On 13Aug2009 22:25, dv1...@wayne.edu dv1...@wayne.edu wrote:
| (1) Isn't my muttrc supposed to override /usr/local/etc/muttrc when
| they conflict?
|
| With mutt config files, there's no notion of conflicts, there cannot
| be. It reads them in line by line and remembers the setting
Hello,
Sometime in the last few days, it appears that the hdr_order setting in my
muttrc is being ignored by mutt. I just noticed it today, with the Aug. 13
nightly, but it may have gone haywire in the last few days.
In my muttrc, I have these three lines:
ignore *
unignore from date
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thursday, August 13 at 07:40 PM, quoth dv1...@wayne.edu:
Sometime in the last few days, it appears that the hdr_order setting
in my muttrc is being ignored by mutt. I just noticed it today,
with the Aug. 13 nightly, but it may have gone
On Thursday, August 13 at 07:40 PM, quoth dv1...@wayne.edu:
Sometime in the last few days, it appears that the hdr_order setting
in my muttrc is being ignored by mutt. I just noticed it today,
with the Aug. 13 nightly, but it may have gone haywire in the last
few days.
Sounds like
[ please try to keep a line length limit of something around 72 ]]
Hi,
* dv1...@wayne.edu wrote:
Well, I found /usr/local/etc/Muttrc, and it does have unignore and
hdr_order in there. I commented them out, and now mutt reads my
settings. But:
(1) Isn't my muttrc supposed to override
(1) Isn't my muttrc supposed to override /usr/local/etc/muttrc when
they conflict?
With mutt config files, there's no notion of conflicts, there cannot
be. It reads them in line by line and remembers the setting internally
somehow. This means they're always applied on top of one another.
On 13Aug2009 22:25, dv1...@wayne.edu dv1...@wayne.edu wrote:
| (1) Isn't my muttrc supposed to override /usr/local/etc/muttrc when
| they conflict?
|
| With mutt config files, there's no notion of conflicts, there cannot
| be. It reads them in line by line and remembers the setting
