Comment by ~ferdinandyb on ~rjarry/aerc
I am unable to reproduce this. I'm also not sure what a client can do if this were the case. We need to hand over the email for sending to the smtp server. If the server can't handle bcc then the only workaround I could see is sending several messages instead of one.
~ferdinandyb, ~justinesmithies
With 0.18.2, folder-specific bindings certainly seem to work, if I'm not mistaken.
However, the command
:delete-message
itself acts strange for me: in a Gmail account, it only deletes messages if run in[Gmail]/Trash
folder. In any other folder (or, label in Gmail's vocabulary), it just deletes a message from the current folder (strips the current label from an email).Sadly, I don't recall it already, but it's possible it was the command's behaviour (different at the time of submission), not the folder-specific bindings per se, that was the reason for my original report (I don't remember if I only had this one folder-specific binding back then and if I tested it with other mappings).
Anyway, as the title stands now, it probably can be closed?
Comment by ~ferdinandyb on ~rjarry/aerc
Ideally, any extra you'd type would be passed to it, e.g.:
define gitsendinreplyto = term git send-email --cc='{{.Cc | persons | join "' --cc='"}}' --annotate --cover-letter --in-reply-to={{.MessageId}}
And you should be able to call:
:gitsendinreplyto -v3 -2
To send a v3 of the last two commits.
Ticket created by ~ferdinandyb on ~rjarry/aerc
If the user has a complicated command the only solution right now is to bind it. The problem with this, is that if the command is rarely used, the user will need to open their config all the time. At this point it would probably be easier to handle it somewhere else as a snippet.
On the other hand if the user could define their
:rarelyusedcommand
as a memorably string that can be autocompleted, the situation is much better.
Ticket created by ~ferdinandyb on ~rjarry/aerc
it would be useful, especially for troubleshooting that after executing the command passed to
:term
it would no exit. Another useful feature would be opening a terminal with the command prepopulated but not executed. The use case for this is checking a command that uses complicated templates before executing something that is potentially harmful.
Ticket created by ~ferdinandyb on ~rjarry/aerc
This would be useful for testing templates. The command would just echo back the string with templates resolved.
Comment by ~ferdinandyb on ~rjarry/aerc
welcome!
REPORTED
RESOLVED CLOSED