On Fri, Jan 25, 2013 at 04:43:34PM -0500, Alan McConnell wrote: > On Fri, Jan 25, 2013 at 12:53:20PM -0700, s. keeling wrote: > > Incoming from Mark H. Wood: > > > On Fri, Jan 25, 2013 at 09:28:05AM -0500, Alan McConnell wrote: > > > > First, generically: I feel it is a source of difficulty that > > > > mutt relies on two config files, .muttrc and .mailcap. Perhaps > > > > > > .mailcap is a general-purpose configuration file for anything that > > > wants to know what you would like done with certain types of content. > > > Lots of other tools also use .mailcap and /etc/mailcap. > > > > > > This is why they are separate. One belongs to Mutt and the other > > > belongs to the world (including Mutt, which can use it). > > > > That was a beautiful exposition. > <LOL> It may seem beautiful to some, but it can't > help anyone with a practical problem.
Well, generically that is what is going on. > Mr Wood wrote further: > > You probably need to add "; needsterminal" to your .mailcap entry for > > "text/html" so that Mutt will ask you to hit a key when the external > > program (Iceweasel) is finished. > <sigh> My iceweasel(aka Firefox) runs, and displays in the > middle of my screen, from the moment my computer is turned > on in the morning till I use it to talk to my DSL modem > to shut down my connection in the evening, preparatory to > "shutdown -h now". Yes, there's an additional wrinkle with Firefox/Iceweasel: if it is already running when you invoke it again, the second invocation just tells the first to do something and then exits. This makes the race even *more*, uh, interesting. The point is to make Mutt wait to remove the file until some time after your browser is actually displaying it. Any time after that, Mutt can be allowed to continue. Come to think of it, it's the second Iceweasel instance which enables the race. That instance just sends a message to the first instance and then exits. Mutt, which was waiting on the second instance, thinks you're done with the temp file and cleans up. The first Iceweasel instance, which is the one you want to read with, may not even have been scheduled yet, and if not then it wouldn't yet have the file open. When the "main" Iceweasel instance tries to obey the message, the file is already gone. > > For more on .mailcap and how Mutt > > interprets it, see: > http://www.mutt.org/doc/manual/manual-5.html > I've pored over the whole document, including this > section. It is likely my stupidity that makes me > unable to find in it why the .muttrc and the .mailcap > are fighting with each other That's because they arent; Mutt and Iceweasel are fighting with each other. > Re "Race Conditions". Unless I am mistaken, mutt is > written as a single, un-threaded process; I believe that > 'me' is (justly) proud of this achievement. So I do > not understand how "two processes" can be involved here. Mutt is one process. Iceweasel is another. -- Mark H. Wood, Lead System Programmer mw...@iupui.edu There's an app for that: your browser
pgpixJTmWMzR_.pgp
Description: PGP signature
