From laalsaas to ~mil/sxmo-devel
--- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index a6b5815..e2a1980 100644 --- a/README.md +++ b/README.md @@ -21,7 +21,7 @@ You will want to use clickclack in combination with another tool, most likely a Clickclack Options: * ``-f`` - A wave file to load and play, note that only the first milliseconds as specified by ``-D`` are actually * ``-f`` - A wave file to load and play, note that only the first milliseconds as specified by ``-d`` are actually [message trimmed]
From laalsaas to ~mil/mepo-devel
A patch release shouldn't have any breaking changes. However, pinning the patch means reducing the tolerance for different zig versions in software repositorys to zero. --- NixOS only has zig 0.10.1, however mepo 1.1.1 still pins zig 0.10.0, while mepo 1.1.2 isn't released yet. src/main.zig | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/main.zig b/src/main.zig index 513038e..33c78f2 100644 --- a/src/main.zig +++ b/src/main.zig [message trimmed]
From laalsaas to ~rjarry/aerc-devel
On Tue Dec 6, 2022 at 6:26 PM CET, Moritz Poldrack wrote: > Regarding the solution of this issue, I don't think we actually have to > do anything. Mails to read with aerc have to follow the established > standards and we can't really cater to everyone not following standards > or bending them to their will :) I do agree that it's not aerc's job to parse invalid mails. However, I would argue that it shouldn't crash when trying to display them.
From laalsaas to ~rjarry/aerc-devel
On Tue Dec 6, 2022 at 9:00 AM CET, Moritz Poldrack wrote: > On Mon Dec 5, 2022 at 11:50 PM CET, laalsaas wrote: > > the bottom line displays the message: "could not get structure: > > message: malformed MIME header line: <!DOCTYPE html>". > Pretty sure the mail does not follow standard and we can't cater to > every non-standard kind of mail. To say for certain we would need the > complete mail (including headers) That is indeed very likely. I have looked at the mail in raw and noticed two things: Firstly, the mail contains this Header: > X-Amavis-Alert: BAD HEADER SECTION, MIME error: error: couldn't parse head; > error near:; <html lang="de">
From laalsaas to ~rjarry/aerc-devel
I just recompiled on master, with the following results: - The mail still displays as "(unable to fetch header)" - I still can't open the mail with "could not get structure: message: malformed MIME header line: <!DOCTYPE html>". - If I am in the email I got after the weird mail and press J, the bottom status line displays the same message, and the main window display the same message prefixed with "could not view message: ". This seems like an improvement, however, aerc crashes as soon as I try to leave the message (by pressing J/K/C-n). Attached you'll once again find the crash report.
From laalsaas to ~rjarry/aerc-devel
Hey, I've revently recieved an email where aerc in the inbox list just displayed "(unable to fetch header)", instead of the timestamp, subject, etc. When I press <Enter> on that mail, the mail doesn't open, the bottom line displays the message: "could not get structure: message: malformed MIME header line: <!DOCTYPE html>". However, I can just fine open that mail in my webmailer, and it displays correctly. I assume this is a bug with the mail backend aerc is using. BTW, the mail is stored in a maildir. If there is some other place upstream where I should report this, don't hesitate to tell me where. Also you can ask me questions about a mail, but I'll not post the mail publicly, as it was from my bank. Here is a thing that i assume is related to how aerc interact with the email backend. When I'm in the mail i got after the weird mail, and then
From laalsaas to ~mil/mepo-devel
I think you forgot to bump the version for the new release, at least `mepo -v` still outputs 1.1 as version.
From laalsaas to ~mil/mepo-devel
The script mepo_ui_menu_user_pin_updater is using geoclue per default. However, the where-am-i binary outputs the coordinates in a number format which is locale-specific. i.e. if you've set LC_NUMERIC="de_DE.UTF-8" , where-am-i will use the comma as the decimal seperator instead of the point. This will lead to the following mepolang statement produced by the script: > pin_add 6 0 51,028178 13,710861 user_location; Mepo can't deal with this and will silently ignore it. The fix is to set the LC_NUMERIC variable to en_US for calling where-am-i. --- scripts/mepo_ui_menu_user_pin_updater.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) [message trimmed]
From laalsaas to ~rjarry/aerc-devel
On Fri Oct 28, 2022 at 1:43 PM CEST, Tim Culverhouse wrote: > I checked through the release notes, and maildir ++ support wasn't added until > 0.11.0, and from your crash log it looks like you are on 0.10.0. True, i didn't check this! I guess I'll have to nag my system administrators to upgrade aerc then. Sorry if i created noise. regards, laalsaas.
From laalsaas to ~rjarry/aerc-devel
Hey, I tried using aerc (which is awesome, btw) on the tilde.club public ssh server. There, every user has a ~/.mail folder managed by dovecot which is in the maildir++ format. When i have this in my accounts.conf, aerc crashes at start: > [tilde] > source = maildirpp://~/.mail > from = laalsaas <laalsaas@tilde.club> > outgoing = /usr/sbin/sendmail I also tried using just maildir:// instead, then it detects only the .sent-mail folder.