Re: ~/Mailbox oddness?
On Fri, Mar 15, 2002 at 02:32:08PM -0500, David T-G wrote: Well, you could always dump the mush client now that you have mutt ;-) Why would I do that? :) Also, I've been using mutt for quite a few years. It's only just now that I'd grown weary enough of the (I thought) broken new mail detection in mutt to complain about it. ;) Since you'll lose mutt's new-mail-detection feature anyway, you might as well either let all of your apps check for you or look at starting off such an app, like newmail, when you log in and before you connect to screen so that whatever window is active will get the notification. The only problem with this is that if I let other apps do it, then my status line in mutt won't be accurate, and mutt won't offer ~/Mailbox as an option to change to when I hit 'c'. I find that much more annoying than having to pop over to mutt from time to time. OT: I love screen. - Myrddin -- ICQ: 22404528 Why Vegan? http://www.firstmagic.com/vegan --
Re: ~/Mailbox oddness?
On Thu, Mar 14, 2002 at 07:14:49AM -0500, David T-G wrote: % On Wed, Mar 13, 2002 at 11:51:38PM +0100, Maarten den Braber wrote: % % Do you have some 'buffy' kind of program that checks ~/Mailbox? % % To the best of my knowledge, no. Though I'm not sure how that would affect % mutt's ability to keep track of new messages in that box...? Because, as has been discussed on the list before, mutt doesn't actually know that there are new messages in the box; it simply knows that the modification timestamp (last write) is later than the access time stamp (last read) and, according to the definition that that fits, says there is new mail. If biff or buffy were to update the access timestamp, though, then it wouldn't fit the new mail qualification any more. Thanks Maarten and David, this put me on the right track. It wasn't a biff, buffy kind of thing, and my shell wasn't checking, but I had two other client type apps that -did- check the mailbox periodically. So, I disabled their checking and, voila, mutt is happy. This does bring up in my mind a curious conundrum. The whole concept of apps checking to see if the mailspool has new mail in it can/should be done in such a way so that multiple apps can do it and not squash each others data. Not that much can be done about it at this point, it seems so many apps use this current model. :/ - Myrddin -- ICQ: 22404528 Why Vegan? http://www.firstmagic.com/vegan --
~/Mailbox oddness?
Something that's been bugging me a bit. I have multiple mailboxes that procmail filters mail into. mutt dutifully notifies me when I have mail waiting in other mailboxes, and such. As well, the status bar across the top of my index list will tell me how many mailboxes have new mail waiting in them. Everything works just fine, -except- when it comes to the main/default mailbox (~/Mailbox). If I'm sitting in one of the other mailboxes, I will get a notification when mail comes into ~/Mailbox, but (I believe) if mail comes into one of the other mailboxes before I get to ~/Mailbox, then the 'c' command won't offer up ~/Mailbox as a default option (ie. when hitting 'c', you will be offered the 'next' mailbox that has new mail waiting in it as a default to change to -- ~/Mailbox is not offered, even if I've already 'c'hanged to all the other mailboxes, read/marked/etc the new mail and -know- there's new mail in the ~/Mailbox). That bugs me. As well, mutt seems to use the list of mailboxes as offered in your 'mailboxes' option as a sort of precedence when offering you a default box to 'c'hange to -- but even though I have '!' as the first mailbox, 'c' never offers to go there first. Always somewhere else. And finally, the status_format variable shows me how many mailboxes have waiting new messages -- however, again, if I'm sitting in one of my 'other' mailboxes, and mail has come into the ~/Mailbox, that variable doesn't indicate such. mutt obviously knows which mailbox I'm in (as status_format will correctly tell me how many new messages are in my current mailbox), so IMO, the %b variable should count ~/Mailbox as a box with waiting mail. Here's some pertinent bits from my .mutt* files: mailboxes ! =tivo =sca =opera =embperl =modperl =alsa set status_format=%v: %f (%s) [%m msgs] [%n new, *=%t, otherboxes=%b] Oh, and I'm using 1.2.5i (Note that using ~/Mailbox in place of ! in the mailboxes line doesn't seem to change the behaviour at all) So, to sum up: A: 'c' will almost never offer ~/Mailbox as a pre-filled option B: I'd like 'c' to respect the order of precedence in the 'mailboxes' list (obviously related to A) C: %b doesn't accurately reflect new mail in ~/Mailbox if you're in a different mailbox. Am I missing something? Are these issues fixed in a newer release? - Myrddin -- ICQ: 22404528 Why Vegan? http://www.firstmagic.com/vegan --
Re: ~/Mailbox oddness?
On Wed, Mar 13, 2002 at 11:51:38PM +0100, Maarten den Braber wrote: * J. Scott Dorr [EMAIL PROTECTED] [020313 22:36]: Everything works just fine, -except- when it comes to the main/default mailbox (~/Mailbox). If I'm sitting in one of the other mailboxes, I will get a notification when mail comes into ~/Mailbox, but (I believe) if mail comes into one of the other mailboxes before I get to ~/Mailbox, then the 'c' command won't offer up ~/Mailbox as a default option (ie. when hitting 'c', you will be offered the 'next' mailbox that has new mail waiting in it as a default to change to -- ~/Mailbox is not offered, even if I've already 'c'hanged to all the other mailboxes, read/marked/etc the new mail and -know- there's new mail in the ~/Mailbox). That bugs me. Do you have some 'buffy' kind of program that checks ~/Mailbox? To the best of my knowledge, no. Though I'm not sure how that would affect mutt's ability to keep track of new messages in that box...? - Myrddin -- ICQ: 22404528 Why Vegan? http://www.firstmagic.com/vegan --
Re: libiconv
On Wed, Jan 30, 2002 at 10:54:24AM -0500, Bechtold, Katie wrote: I'm trying to install mutt on a Slackware 7.0 system, but I'm stuck on the configure step. I get the following error: checking whether this iconv is good enough... no configure: error: Try using libiconv instead I just installed libiconv-1.7, but I see that's not enough to make configure see it. What do I have to do to use libiconv? Very likely you still have the old config.status sitting around. After having properly installed libiconv, do a 'make distclean'. Then start over with 'configure', etc. Hope this helps. - Myrddin -- ICQ: 22404528 Why Vegan? http://www.firstmagic.com/vegan --
Re: Suggestion for List Etiquette
On Fri, Jan 11, 2002 at 07:46:15AM -0600, Anh Lai wrote: ... On 01/10/02, Knute decided to write ... On Fri, 11 Jan 2002, Nick Croft wrote: This is quoted text: This is quoted text: This is quoted text: * Imre Vida ([EMAIL PROTECTED]) wrote: This is quoted text: somewhat different but related: This is quoted text: [ snip ] (Note, I merely edited the message, I didn't actually change my reply thinggy-ma-jiggy.) 9o) LOL, that is too funny. It probably would have been easier to change your reply thinggy-ma-jiggy just to write that email. Nah. :) He coulda just highlighted the appropriate lines (via shift-v or some such) then ':s/^/This is quoted text: ' Faster that then changed the reply thingy-ma-jiggy, then changing it back. ;) - Myrddin -- ICQ: 22404528 Why Vegan? http://www.firstmagic.com/vegan --
