Ian Zimmerman wrote:
What I ended up doing (after spending several days patching the source
with debug prints just to understand WTH was happening) was:
folder-hook .*^/home/itz/foo/.* my_hdr X-itz-real-home-foo: yes
Another workaround which might be less distasteful would be to use
On 2015-07-21 10:15 +0200, Michael Tatge wrote:
folder-hooks use substring matches.
Unanchored regexp matches, to be more precise.
^ is a shortcut for the current mailbox. It's not BOL here.
Do you see how these 2 facts together make it hard to construct a
meaningful pattern, if you're
I should read more carefully.
* On Tue, Jul 21, 2015 10:15AM +0200 I (tatg...@gmail.com) muttered:
* On Wed, Jul 15, 2015 01:00PM -0700 Ian Zimmerman (i...@buug.org) muttered:
Which of the following will fire when entering /home/itz/foobar/inbox ?
Ian,
* On Wed, Jul 15, 2015 01:00PM -0700 Ian Zimmerman (i...@buug.org) muttered:
It is not clear from the manual against what the folder-hook command
matches the given pattern.
folder-hooks use substring matches.
Let's say my folders are under /home/itz/foobar/ , and /home/itz/Mail is
a
On 15.07.15 13:00, Ian Zimmerman wrote:
Let us further assume the following is set globally:
set folder=~/Mail
(I can neither confirm nor deny that this is in fact the case :)
Try:
:set ? folder
Here, that gives:
folder=~/mail
due to:
$ grep folder .muttrc
set folder=~/mail
Erik
It is not clear from the manual against what the folder-hook command
matches the given pattern.
Let's say my folders are under /home/itz/foobar/ , and /home/itz/Mail is
a symbolic link to foobar. Let us further assume the following is set
globally:
set folder=~/Mail
(I can neither confirm nor
