Re: push and the limit command
On Tue, Aug 15, 2000 at 08:29:38PM +0530, Suresh Ramasubramanian wrote: Using a large mallet, [EMAIL PROTECTED] whacked out: However, there is one problem, if the dreaded IMAP message is the *only* one in the folder then mutt gives an error "No messages matched criteria." and doesn't remove the message from the index display. If mutt is the only thing you use - and you dont read mails off the server, what's wrong in having your procmail dev/nulling them? ? Procmail doesn't come into it at all! I have a system with an IMAP server running on it where I store 'interesting' mail from all the accounts where I run mutt (home, work and two shell login accounts). The mail stays on the IMAP server as the whole point is that I can see it and refer to it from anyhwhere. The "DON'T DELETE THIS MESSAGE " message doesn't show up when using mutt to look at mail on a remote IMAP server like this. Sometimes however I use mutt on the system where the IMAP server is running, using mutt this way *does* show the unwanted message. This is when I want to use the 'limit' command to hide the message. In this case mutt is viewing the mailboxes directly, not using the IMAP server. -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
Re: push and the limit command
On Tue, Aug 15, 2000 at 01:08:32PM -0400, David T-G wrote: Suresh, et al -- ...and then Suresh Ramasubramanian said... % Using a large mallet, [EMAIL PROTECTED] whacked out: % % However, there is one problem, if the dreaded IMAP message is the % *only* one in the folder then mutt gives an error "No messages matched % criteria." and doesn't remove the message from the index display. I still wonder about this one. I thought that mutt would happily display an empty mailbox, and one would think that the message would certainly match the criteria... But I'm not playing around to test it, so I'll just go away again. No, what's happening is that the limit command with a '!' is saying "display all messages that *don't* match this", there are no messages that *don't* match so mutt displays the error. -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
Re: push and the limit command
On Mon, Aug 14, 2000 at 06:41:59PM +0300, Mikko Hänninen wrote: [EMAIL PROTECTED] [EMAIL PROTECTED] wrote on Mon, 14 Aug 2000: push l ! 'DELETE THIS MESSAGE' but, at startup, mutt just says:- Error in /usr/home/chris/.mutt/muttrc, line 96: push: too many arguments What am I doing wrong? I guess it's something to do with the '!' and the RE but I can't work out the right syntax. Push is a command that takes exactly one argument. If you want to push a space, you need to quote the entire string: push "l! 'DELETE THIS MESSAGE'" You should also be careful with the limit, and make sure it matches *only* that one message, and for example, not messages to mutt-users discussing how to avoid seeing that message... And you may in fact wanted to use "l!~s 'DELETE THIS MESSAGE'", to match the subject, or something. Thanks for the response, I now have the above push working OK. Yes, I appreciate there's always a risk of missing other messages as well, however the message number in the index gives one a clue by indicating how many messages have been ignored by the limit. I have 'improved' the limit RE now so that it's:- push "l!~s '^DON'\\''T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA$'^M" This (I hope) anchors the string at both ends so that only messages with this exact subject will be matched so messages with 'Re:' on the front etc. will not be ignored. -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
Re: push and the limit command
On 2000.08.15, in [EMAIL PROTECTED], "[EMAIL PROTECTED]" [EMAIL PROTECTED] wrote: push "l!~s '^DON'\\''T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA$'^M" This (I hope) anchors the string at both ends so that only messages with this exact subject will be matched so messages with 'Re:' on the front etc. will not be ignored. Turns out you also can use: push "limit! ~h X-IMAP:return" or, I guess, push "l! ~h X-IMAP:\n" I can't guess how much slower that might be, if any, but it's surely simpler. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: push and the limit command
Using a large mallet, David Champion whacked out: Turns out you also can use: push "limit! ~h X-IMAP:return" or, I guess, push "l! ~h X-IMAP:\n" I can't guess how much slower that might be, if any, but it's surely simpler. That works out in the wu-imapd ... and in any case, isn't that the only imap in which the 'folder internal data' is generated? -- Suresh Ramasubramanian + Lumber Cartel India - tinlcI mallet @ cluestick.org + Wallopus Malletus Indigenensis The human animal differs from the lesser primates in his passion for lists of "Ten Best". -- H. Allen Smith
Re: push and the limit command
On Tue, Aug 15, 2000 at 03:27:46AM -0500, David Champion wrote: On 2000.08.15, in [EMAIL PROTECTED], "[EMAIL PROTECTED]" [EMAIL PROTECTED] wrote: push "l!~s '^DON'\\''T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA$'^M" This (I hope) anchors the string at both ends so that only messages with this exact subject will be matched so messages with 'Re:' on the front etc. will not be ignored. Turns out you also can use: push "limit! ~h X-IMAP:return" or, I guess, push "l! ~h X-IMAP:\n" I can't guess how much slower that might be, if any, but it's surely simpler. Definitely! :-) I think this is a very neat approach. I doubt if it's significantly slower and I'm not really fussed on that front, I don't have folders with large numbers of mail messages in them. -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
Re: push and the limit command
On Tue, Aug 15, 2000 at 02:38:14PM +0530, Suresh Ramasubramanian wrote: Using a large mallet, David Champion whacked out: Turns out you also can use: push "limit! ~h X-IMAP:return" or, I guess, push "l! ~h X-IMAP:\n" I can't guess how much slower that might be, if any, but it's surely simpler. That works out in the wu-imapd ... and in any case, isn't that the only imap in which the 'folder internal data' is generated? Yes, as far as I know it's only UW does it. As none of the others uses mbox format it's the only one where it matters anyway as it's the only one where the MUA can use the same folders directly. (Well you can do this with Courier-IMAP's maildirs but they're not really suitable for using this way) -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
Re: push and the limit command
On Tue, Aug 15, 2000 at 10:24:21AM -0400, Brendan Cully wrote: On Tuesday, 15 August 2000 at 06:01, [EMAIL PROTECTED] wrote: On Tue, Aug 15, 2000 at 03:27:46AM -0500, David Champion wrote: Turns out you also can use: push "limit! ~h X-IMAP:return" or, I guess, push "l! ~h X-IMAP:\n" I can't guess how much slower that might be, if any, but it's surely simpler. Definitely! :-) I think this is a very neat approach. I doubt if it's significantly slower and I'm not really fussed on that front, I don't have folders with large numbers of mail messages in them. Watch out for this one. It may end up rendering all your new messages as read (or not recent, anyway). I believe ~h searches require mutt to download every message in the mailbox. ~s is much faster because the subject is already fetched for the index view... ... but it's not needed if you're reading via the server, it's only needed if you're reading mail direct. Anyway, even if I'm wrong, I'm reading the mail direct from the mboxes. However, there is one problem, if the dreaded IMAP message is the *only* one in the folder then mutt gives an error "No messages matched criteria." and doesn't remove the message from the index display. -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
Re: push and the limit command
Using a large mallet, [EMAIL PROTECTED] whacked out: However, there is one problem, if the dreaded IMAP message is the *only* one in the folder then mutt gives an error "No messages matched criteria." and doesn't remove the message from the index display. If mutt is the only thing you use - and you dont read mails off the server, what's wrong in having your procmail dev/nulling them? -- Suresh Ramasubramanian + Lumber Cartel India - tinlcI mallet @ cluestick.org + Wallopus Malletus Indigenensis An apple every eight hours will keep three doctors away.
Re: push and the limit command
Suresh, et al -- ...and then Suresh Ramasubramanian said... % Using a large mallet, [EMAIL PROTECTED] whacked out: % % However, there is one problem, if the dreaded IMAP message is the % *only* one in the folder then mutt gives an error "No messages matched % criteria." and doesn't remove the message from the index display. I still wonder about this one. I thought that mutt would happily display an empty mailbox, and one would think that the message would certainly match the criteria... But I'm not playing around to test it, so I'll just go away again. % % If mutt is the only thing you use - and you dont read mails off the server, % what's wrong in having your procmail dev/nulling them? No, you have it backwards; he not only reads the mailboxes locally but also with IMAP, and they never go thru procmail because it's the IMAP server that puts the fake message in place. % % -- % Suresh Ramasubramanian + Lumber Cartel India - tinlcI % mallet @ cluestick.org + Wallopus Malletus Indigenensis % An apple every eight hours will keep three doctors away. :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! The "new millennium" starts at the beginning of 2001. There was no year 0. Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh* PGP signature
Re: push and the limit command
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote on Mon, 14 Aug 2000: push l ! 'DELETE THIS MESSAGE' but, at startup, mutt just says:- Error in /usr/home/chris/.mutt/muttrc, line 96: push: too many arguments What am I doing wrong? I guess it's something to do with the '!' and the RE but I can't work out the right syntax. Push is a command that takes exactly one argument. If you want to push a space, you need to quote the entire string: push "l! 'DELETE THIS MESSAGE'" You should also be careful with the limit, and make sure it matches *only* that one message, and for example, not messages to mutt-users discussing how to avoid seeing that message... And you may in fact wanted to use "l!~s 'DELETE THIS MESSAGE'", to match the subject, or something. Hope this helps, Mikko -- // Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy scifi, the Corrs / Press any key to continue, or any other key to cancel.
