Re: problems with 1.2.2i
On Thu, Jun 22, 2000 at 03:53:35AM +0200, clemensF <[EMAIL PROTECTED]> muttered: > > Mike Markowski: > > > Notice that I now must put *two* slashes after "~mm". With only a > > single slash, I get this: > > how in the world did you find out? i would never have had the idea to try > to put two slashes in there! now tell us: what made you do this? not the > marsians again > > clemens I *am* a Martian... :-) Actually, the error message clued me in - it shows the correct path but missing the first slash. Mike ([EMAIL PROTECTED])
Re: problems with 1.2.2i
On Wed, Jun 21, 2000 at 05:19:52PM +0200, Thomas Roessler <[EMAIL PROTECTED]> muttered: > On 2000-06-21 10:49:57 -0400, Mike Markowski wrote: > > > Notice that I now must put *two* slashes after "~mm". With only a > > single slash, I get this: > > [...] > > > It seems to swallow the first slash. > > Please try the attached patch. Yup, that did the trick! Thanks very much, Thomas. Mike
Re: problems with 1.2.2i
On Wed, Jun 21, 2000 at 10:13:03AM -0400, Daniel Monjar <[EMAIL PROTECTED]> muttered: > Just grabbed 1.2.2i and did the install. Everything appeared to work > well but mutt seg faults on invocation. I'm running on Solaris 8 without imap/ssl and it works without any noticable problems, except for a minor oddity. I have a $HOME/.mutt directory with various muttrc type files in it. My main rc file in $HOME/.mutt is Muttrc which contains only: source ~mm//.mutt/vars source ~mm//.mutt/pgp2 source ~mm//.mutt/aliases source ~mm//.mutt/colors source ~mm//.mutt/hooks source ~mm//.mutt/lists source ~mm//.mutt/macros source ~mm//.mutt/autoview Notice that I now must put *two* slashes after "~mm". With only a single slash, I get this: 64 mahler> mutt Error in /home/base/usrb/mm/.mutt/Muttrc, line 1: /home/base/usrb/mm.mutt/vars: No such file or directory Error in /home/base/usrb/mm/.mutt/Muttrc, line 2: /home/base/usrb/mm.mutt/pgp2: No such file or directory Error in /home/base/usrb/mm/.mutt/Muttrc, line 3: /home/base/usrb/mm.mutt/aliases: No such file or directory Error in /home/base/usrb/mm/.mutt/Muttrc, line 4: /home/base/usrb/mm.mutt/colors: No such file or directory Error in /home/base/usrb/mm/.mutt/Muttrc, line 5: /home/base/usrb/mm.mutt/hooks: No such file or directory Error in /home/base/usrb/mm/.mutt/Muttrc, line 6: /home/base/usrb/mm.mutt/lists: No such file or directory Error in /home/base/usrb/mm/.mutt/Muttrc, line 7: /home/base/usrb/mm.mutt/macros: No such file or directory Error in /home/base/usrb/mm/.mutt/Muttrc, line 8: /home/base/usrb/mm.mutt/autoview: No such file or directory source: errors in /home/base/usrb/mm/.mutt/Muttrc Press any key to continue... It seems to swallow the first slash. Mike
Re: New Mail Polling
On Tue, Mar 14, 2000 at 12:33:25PM +0200, Mikko Hänninen wrote: > John P. Verel <[EMAIL PROTECTED]> wrote on Mon, 13 Mar 2000: > > > Over the next couple days, I intend to try some XWindow biff-like > > clients and see how that goes. > > Keep in mind that some of the biff-style utilities will conflict with > Mutt's folder new-ness detection. Can you recommend any that don't conflict? I'm using xbiff, which definitely does. Thanks, Mike
Re: setting limit in .muttrc
On Tue, Feb 15, 2000 at 05:03:05PM +0100, Frank Joerdens wrote: > Hmm, doesn`t work here. Upon launching mutt, I get the error > > /home/frank/.muttrc, line 1: too few arguments Sorry. I could've sworn that worked when I tried it... Well, in the past few minutes multiple tests of the following seem to work in 1.0.1i: folder-hook /var/mail/mm "push 'l ! ~f \"Mail System Internal Data\"'\\n" (Note that I changed the '.' to my mail spool file.) > Wouldn't it be nice to do this directly, e.g. via > > set limit ! ~f "Mail System Internal Data" > > or is there another way to do it? I used a folder-hook so that when returning to my main folder, it would again execute the 'push'. But I'm 2 weeks new to mutt, so I expect there are probably better solutions... Mike > Cheers, > Frank > > > On Mon, Feb 14, 2000 at 01:29:26PM -0500, Mike Markowski wrote: > > I use this: > > > > folder-hook . ;push 'l ! ~f "Mail System Internal Data"'\n > > > > and it seems to do the job. > > > > Maybe someone can explain why it doesn't work without that initial > > semicolon, though! :-) > > > > Thanks, > > Mike > > > > > > On Mon, Feb 14, 2000 at 06:56:41PM +0100, Frank Joerdens wrote: > > > > > > Is it possible to configure mutt to not show the message DON'T DELETE > > > THIS MESSAGE -- FOLDER INTERNAL DATA which is generated by my IMAP/POP3 > > > server? > > -- > frank joerdens > > joerdens new media e: [EMAIL PROTECTED] > heinrich-roller str. 16/17 t: +49 30 44055470 > 10405 berlinf: +49 30 44055475 > germany h: http://www.joerdens.de > > pgp fingerprint: > 73D0 C6C1 931D 9E0E D94B 1CB5 6A31 B70E 9907 3D95
Re: peculiar requirement (maybe)
I use this: folder-hook . ;push 'l ! ~f "Mail System Internal Data"'\n and it seems to do the job. Maybe someone can explain why it doesn't work without that initial semicolon, though! :-) Thanks, Mike On Mon, Feb 14, 2000 at 06:56:41PM +0100, Frank Joerdens wrote: > > Is it possible to configure mutt to not show the message DON'T DELETE > THIS MESSAGE -- FOLDER INTERNAL DATA which is generated by my IMAP/POP3 > server?
