On Thu Nov 21, 2024 at 21:19, ~inwit outgoing@sr.ht wrote:
This would indeed solve viewing inline images in text/html parts with a sixel/kitty capable tui browser like chawan. Maybe it's better to define a [pagers] config section allowing different pagers for different filetypes? Could be an overshoot, but the | syntax as defined here is obscure to me.
That would be overkill and hard to reason about imho. The idea here is that you just mark that specific filter line you have that you will be providing the pager, aerc does not have to pipe it into the configured default pager.
Comment by ~inwit on ~rjarry/aerc
This would indeed solve viewing inline images in text/html parts with a sixel/kitty capable tui browser like chawan. Maybe it's better to define a [pagers] config section allowing different pagers for different filetypes? Could be an overshoot, but the | syntax as defined here is obscure to me.
Comment by ~inwit on ~bptato/chawan
+1
Having images in dump mode would be brilliant! We could read those cursed html emails with inline images in the terminal, which would be just perfect for aerc and other tui email clients.
EDIT: Ah, we'd need to solve links too, since they seem to be stripped in dump mode... :( Ideally,
cha --dumpshould produce OSC-8 links, right?
Comment by ~inwit on ~rjarry/aerc
Currently, we need to perform the following steps to accept (or decline) an invitation:
- Call the :accept/:decline/:accept-tentative command
- Exit the editor that pops up with a standard event reply email
- Call :send from the review screen
Imho, it'd be also a nice improvement if we had an option to do all these steps at once, or at least skip the second if the user knows that no modifications are required to the standard invitation response.
feature added by ~inwit on ~rjarry/aerc
Comment by ~inwit on ~rjarry/aerc
Solved with the {{.Filenames}} template.
REPORTED RESOLVED IMPLEMENTED
~inwit but this is actually notmuch+maildir so we should be able to delete
On Sat Jun 29, 2024 at 11:52, ~neff outgoing@sr.ht wrote:
Oh, my email provider seems to have issues with
~in email addresses or something. I'll investigate. I sent the email twice. (For sourcehut I use the tuta webmail backend, not aerc. Good reason to change this.)Sourcehut provides an alternative address for this case:
u.rjarry.aerc-devel@lists.sr.ht~inwit reviewed the patch. Is this sufficient?
Sorry for the inconvenience and thanks again.
Yes, it is, thanks! :)
-- +36305425054 bence.ferdinandy.com
Oh, my email provider seems to have issues with
~in email addresses or something. I'll investigate. I sent the email twice. (For sourcehut I use the tuta webmail backend, not aerc. Good reason to change this.)~inwit reviewed the patch. Is this sufficient?
Sorry for the inconvenience and thanks again.
Hi ~neff,
~inwit also reported the same issue recently.
Could you try building from source after reverting commit https://git.sr.ht/~rjarry/aerc/commit/f204c736759f4d6647a50aa94a415545c0d3a8f7 ?
I would be surprised if this was the source of the problem but it is worth checking.
Thanks!