Paul, that's just brilliant, thank you :)
folder-hooks were always somehow overlooked by me but now I see the potential :)
Thanks once again!
--
Alex
On 12/6/18, Paul Hoffman wrote:
> On Thu, Dec 06, 2018 at 05:16:09PM +0200, Alex Sa wrote:
>> Is it possible to set up a ma
Thanks, Francesco!
It's a bit of re-write for all the "changing folders" macroses that I
have previously set up but it seems like this trick indeed can help me
:)
Thanks once again!
--
Alex
On 12/6/18, Francesco Ariis wrote:
> Hello Alex,
>
> On Thu, Dec 06, 2018 a
Hi!
Is it possible to set up a macro that would behave differently
dependent on the current folder?
Let's say I want to to limit messages in the "[Gmail]/All Mail" folder
to display only the new ones. So, if I'm not in "All Mail", that would
be something like this:
=[Gmail]/All Mail~U
However,
On 10/5/18, John Hawkinson wrote:
> I suggest you
>
> set edit_headers
Now, that's something! Thanks, John!
For those, who are interested: because of email addresses present in
the editor while editing the message, in Vim, I can create something
like that (in $VIMHOME/ftdetect/mail.vim):
On 10/5/18, Timothy Rice wrote:
> I think what you are asking is, if the To: field matches a particular
> pattern, then can the CC: field by populated automatically?
No, Timothy :)
As I've said in my initial question, "I can't add them blindly or
always". I just want to be reminded (in some way)
On Thu, Oct 04, 2018 at 10:56:15PM -0400, Patrick Shanahan wrote:
> you can add recipients (to "t", copy
> "c" and bcc "b") after leaving the
> editor but before sending the msg.
*When* you arrive at this point, when
you leave the editor but before sending
the msg (like shown on this pic:
https:/
Hi!
When replying to some certain emails, I
usually have to add other recipients to
the list. But unfortunately, I often
forget to do so.
Thus, my question: is it possible that
after leaving the editor and arriving at
Mutt's Compose section (where you can
actually add someone with t or c
hotkeys
>> Is there any way to protect these folders? Or give up using 'em? Or
>> any other workaround?
> encryption via your secure shell?
Thanks, PAtrick, but what kind of encryption do you mean? And if these
folders will be decrypted after the mutt starts, then they will be
available to almost anyone,
Hello,
I'm thinking on the possibility to start using mutt installed on a
remote machine, who's admin is not me. What frightens me is that
~/.mutt/cache directory, which contains cached bodies and headers
accessible and viewable almost to anyone :).
Is there any way to protect these folders? Or
