~john1doe


#25 After clearing a filter, any action leads to reloading the current folder a month ago

Comment by ~john1doe on ~rjarry/aerc

This seems to be fixed in 0.9.0?

#34 Option to disable or limit statusline? a month ago

Ticket created by ~john1doe on ~rjarry/aerc

Can an option to disable the statusline messages be added? Or to limit them to some bare minimum at least, to print only errors and such?

It just keeps getting noiser and noiser with no opt-out at all.

#25 After clearing a filter, any action leads to reloading the current folder 2 months ago

Ticket created by ~john1doe on ~rjarry/aerc

(I only use IMAP, don't know if this happens with other backends.)

#To reproduce

  1. Enter a new filter, like :filter -u or :filter '[PATCH]';
  2. Clear it with :clear;
  3. Do something with a message of your choice, like open it, or toggle its read status;

#Observed results:

  1. Note the whole folder reloads.

#Expected results:

  1. The folder should not reload (the filter is already cleared, the default all messages view is already restored, why reload?)

Happens with 0.8.1, 0.5.2, as well as with the default binds.conf.

#468 ui folder/account specific sorting doesn't seem to work (maildir) 1 year, 5 months ago

Ticket created by ~john1doe on ~sircmpwn/aerc2

As of commit a1467af, adding something like this to aerc.conf doesn't work (both for ui:account and ui:folder):

[ui:account=ACCOUNTNAME]
sort="from"

While adding something like this does:

[ui:account=ACCOUNTNAME]
index-format=%D

(This is the maildir backend, so issuing the :sort from command manually does work.)

#460 Problems with folders with square brackets (maildir) 1 year, 6 months ago

Comment by ~john1doe on ~sircmpwn/aerc2

REPORTED RESOLVED FIXED

#460 Problems with folders with square brackets (maildir) 1 year, 6 months ago

bug added by ~john1doe on ~sircmpwn/aerc2

#460 Problems with folders with square brackets (maildir) 1 year, 6 months ago

Ticket created by ~john1doe on ~sircmpwn/aerc2

On maildir backend, aerc seems to fail when copying/moving messages to a folder, which has square brackets in its name, like [test].

When I try to copy a message to such a folder, it reports the following error:

could not copy message 969: maildir: key 1604464143.citron.local.949571000212ece86f727c1ec0dd4a matches 0 files.

And if I take a look at the filesystem, then I notice the following:

  1. This is the contents of the source folder, test:

    ~/Maildir/test/cur> ls -la total 68K -rw-r--r-- 1 s 31K Nov 4 00:31 1604462839.M934234P89860Q2.citron.local:2, -rw-r--r-- 1 s 15K Nov 3 21:37 1604462852.M72207P89860Q3.citron.local:2, -rw-r--r-- 1 s 4.1K Nov 3 22:32 1604462855.M585571P89860Q4.citron.local:2, -rw-r--r-- 1 s 3.0K Nov 3 20:53 1604462855.M600502P89860Q5.citron.local:2, -rw-r--r-- 1 s 2.1K Nov 3 20:51 1604462855.M612264P89860Q6.citron.local:2, -rw-r--r-- 1 s 3.6K Nov 3 20:50 1604462855.M624851P89860Q7.citron.local:2,S

  2. This is the contents of the destination folder, [test] after the failed cp command:

    ~/Maildir/[test]/cur> dir total 4.0K -rw------- 1 s 2.1K Nov 4 06:29 1604464143.citron.local.949571000212ece86f727c1ec0dd4a2,

And if I :cf [test], the directory sidebar will say that I have 1 message there but the folder itself will display none. However, if in the shell I will rename this only message in the [test] folder from 1604464143.citron.local.949571000212ece86f727c1ec0dd4a2, to 1604464143.citron.local.949571000212ece86f727c1ec0dd4a:2, then I will be able to see and open the message (or copy it from [test] to any other folder) just fine.

So, the problem seems to arise when copying/moving TO a folder with the square brackets. More precisely, a colon in the name of the message somehow gets "eaten".

#416 aerc's :term doesn't seem to support high/true color, some text decorations 1 year, 9 months ago

Comment by ~john1doe on ~sircmpwn/aerc2

As far as I understand, you can compile aerc with the original tcell:

  • remove replace github.com/gdamore/tcell => git.sr.ht/~sircmpwn/tcell v0.0.0-20190807054800-3fdb6bc01a50 from go.mod file
  • run go get github.com/gdamore/tcell@master

It doesn't seem to solve any of the problems, though: both italic and truecolor (without abusing TERM) still will not function.

#423 Error when sending mail with accents in the filename of an attachment 1 year, 10 months ago

Comment by ~john1doe on ~sircmpwn/aerc2

From my side, it looks like so. Thank you very much :)

#423 Error when sending mail with accents in the filename of an attachment 1 year, 10 months ago

Comment by ~john1doe on ~sircmpwn/aerc2

Not only in the attachment filename but also in the Subject (and other fields may be affected, too).