On Apr 25, David T-G wrote: [snip] > > What does > > ls -dl `which mutt` `which mutt_dotlock` `dirname $MAIL` > > give you? If mutt_dotlock is owned by you instead of root, that's > probably your problem. Fortunately it's easily fixed by getting rid of > the mutt_dotlock you just installed; the 1.2.5 one will still be in your > path and mutt (yours, 1.2.5, or any other one whose user has the original > dotlock program in $PATH) will happily use it.
Sorry for the delay, and thanks everyone for your responsiveness. I just made mutt_dotlock setgid for the right group and things work. I had a sendmail misconfiguration and all of these emails popped out days after I sent them :( So I got some help here for the read only problem. Now I understand why installing the new version messed it up though. [snip] > % > % > % P.S. > % > % I wanted to use the $hide_missing, but even under 1.3.28i it claims it is an > % invalid variable. Is this a future feature or am I still not getting the > % latest version? > > Hmmm... I'm running 1.3.28 and, although I do have quite a cocktail of > patches, I don't need any patch to set $hide_missing. I believe it was > integrated into the build around 1.3.25, though I'm not positive; I have > > patch-1.3.24-de-new_threads.3 > > (though I'm not using it for my build, I promise) which has hide_missing > in it and so it can't have been too far after that. So when you're in > mutt and you type > > :set ?hide_missing > > you get an error? No, this works fine (it says hide_missing is set). What doesn't work is putting the line: set hide_missing no in my .muttrc... ... oh dang it, I'm a total idiot. I didn't put in the equals. Thanks for putting up with newbie errors!
