~inwit

Trackers

~inwit/org-notmuch-hello

Last active 1 year, 1 month ago

#174 Send may not be able to set "replied" flag on message is archived too quickly. 22 days ago

Comment by ~inwit on ~rjarry/aerc

Imho, it would be even cleaner to have a proper way to chain commands, although that would probably be harder to develop. See https://todo.sr.ht/~rjarry/aerc/92

#159 Remember folder upon reconnection in IMAP 2 months ago

Ticket created by ~inwit on ~rjarry/aerc

When working over an unstable connection with the IMAP interface, aerc loses trace of the currently selected folder if the network goes down, going back to the default folder when the network comes back. It would be good to remember the folder/message that were selected and go back to them upon reconnection.

#148 Allow for thread folding 2 months ago

Ticket created by ~inwit on ~rjarry/aerc

It would be great if we could fold/unfold message threads. As @rockorager pointed out, the logic could be similar to the dirtree collapsing/expanding.

#18 style: allow styling individual message list fields 2 months ago

Comment by ~inwit on ~rjarry/aerc

This is mostly solved, yay! However, it might be nice to have a way to template the full line conditionally, instead of having to configure each part. For example, say I want to apply a conditional format to mails from "builds.sr.ht". I would need to write the conditional for every column field:

index-columns = date>12,name<17,flags>4,subject<*
column-date = {{if (and (match (index .From 0).Name `builds.sr.ht`) (eq .Folder "INBOX"))}}{{else}}{{.DateAutoFormat .Date.Local}}{{end}}
column-name = {{if (and (match (index .From 0).Name `builds.sr.ht`) (eq .Folder "INBOX"))}}{{else}}{{index (.From | names) 0}}{{end}}
column-flags = {{if (and (match (index .From 0).Name `builds.sr.ht`) (eq .Folder "INBOX"))}}{{else}}{{.Flags | join ""}}{{end}}
column-subject = {{if (and (match (index .From 0).Name `builds.sr.ht`) (eq .Folder "INBOX")) -}}{{- .Style (print .ThreadPrefix .Subject) "msglist_dim" -}}{{- else -}}{{- .ThreadPrefix}}{{.Subject -}}{{- end}}

It'd be nice if I could do this in a single place.

#132 move signature into template 2 months ago

Comment by ~inwit on ~rjarry/aerc

I use the following:

{{exec `cat ~/Mail/signature.txt` ""}}

But I agree that it'd be cleaner to have a signature template.

#76 show an "unread" bar 2 months ago

Comment by ~inwit on ~taiite/senpai

This would be great indeed.

Thanks for senpai! :)

#137 how to handle notmuch + maildir integration 2 months ago

on ~rjarry/aerc

On Tue Feb 28, 2023 at 5:03 AM CST, ~inwit wrote:

  • In the case of folders, templating might be the easiest solution, but we could also split the dirlist and have a second area just for virtual folders. This solution would also be useful for operating on searches (saving them as permanent in the dirlist by adding them to the query-map file, for example, or even exporting a search to a folder or mbox).

I have a pretty good way to handle this one in the works. I am adding IANA special-use roles to the Directory model, and also adding a custom internal aerc one called "Query" (or "Search", still to be figured out). But that flag will allow us to determine the use of a folder - and for the case of "Query"/"Search"

  • limit some functionality that may be hard to determine the users intent (IE moving a message).

This functionality would extend beyond notmuch:

  1. global maildir search
  2. IMAP Esearch (multi-mailbox search, supported by gmail, office 365, fastmail,)
  3. gmail custom IMAP search (gmail exposes gmail-search syntax over imap in a custom extension, we could implement this)

-- Tim

#137 how to handle notmuch + maildir integration 2 months ago

Comment by ~inwit on ~rjarry/aerc

In summary, I see mainly three alternatives:

  1. Give the notmuch interface access to maildir folders. This is what we have now, sort of. As discussed in the aforementioned mailing list thread, maildir folders are currently recreated using notmuch queries. This implies that, on those 'fake' maildir folders, what we see are messages, not files, which is ok-ish if a message is supported by a single file in the maildir store, but it's bound to cause trouble if there are multiple files storing copies of a single message (inducing ambiguity in move/delete operations and search/filter commands).

  2. Give the maildir interface access to notmuch searches. This has been suggested several times and could be nice to have. However, accessing a notmuch database from the maildir worker would result in the same ambiguites.

  3. Full merge (single interface). We get rid of the notmuch worker (giving up mh support along the way, gasp) and we consider notmuch as merely an optional addition for the maildir worker, integrating all the functionality of notmuch into the maildir interface. The alternative (giving up the maildir worker in favour of the current notmuch interface) does not seem so appealing, since notmuch builds upon maildir.

In any of these three options, however, we still need to deal with the ambiguity of the pairs messages/files and folders/virtual folders, so we will need to address this anyway. A solution that has been discussed might be to impose a visual indication with sane defaults for both of them:

  • In the case of message/files listed in the message list, we could either add a new flag to the flag column, add a new column able to display the number of files present for each message (notmuch-emacs added a related functionality recently), or display files and messages with a different template. Possibly a combination of these solutions would be best.

  • In the case of folders, templating might be the easiest solution, but we could also split the dirlist and have a second area just for virtual folders. This solution would also be useful for operating on searches (saving them as permanent in the dirlist by adding them to the query-map file, for example, or even exporting a search to a folder or mbox).

#141 Problem with MS email 3 months ago

Ticket created by ~inwit on ~rjarry/aerc

For whatever reason, aerc fails to show a message in the list, and instead of showing the contents for the columns that I have defined (pretty much standard: index-columns = date>12,name<17,flags>4,subject<50,labels<*), I get the following in the name column: " template: column-name:1:2: executing "column-name" at <index (.From | names) 0>: error calling index: reflect: slice index out of range".

The (redacted) message is here: https://paste.sr.ht/~inwit/d470bedd4ea6417bb82dc29d17c161be86c65a45

#5 notmuch: reto's fork and segmentation faults 3 months ago

Comment by ~inwit on ~rjarry/aerc

I'd say zenhack it's not the official binding: https://notmuchmail.org/bindings/