Re: selecting deleted messages
On Mon, Mar 13, 2000 at 06:09:55PM +, J McKitrick wrote: : :I know mutt has an option (resolve) to not move to the next message :after performing an action. If i delete a message, is there any way :to get back to that message besides entering the message number? The :index skips deleted messages when navigating, of course. Interpreting your message differently, there's not a way to do so. Using an example pager index: 36 Mar 13 J McKitrick (0.4K) selecting deleted messages 37 D Mar 13 Gary Johnson(0.6K) |-> 38 Mar 14 J McKitrick (0.8K) |-> if my current selection is on message #36, pressing 'd' marks that message as deleted, and moves my current select to message #38. As far as I know, there is no mechanism within Mutt to remember your previous selection; thus there's no way to automagically jump from message #38 back to message #36. -- Eugene Lee [EMAIL PROTECTED]
Re: [Announce] mutt-1.1.9 is out - RELEASE CANDIDATE!
On 2000-03-13 20:03:37 +0100, Thomas Roessler wrote:
> Mutt-1.1.9 is out on ftp://ftp.mutt.org/pub/mutt/devel/,
Just a reminder: There is a mutt-announce mailing list.
The last mail there announced 1.0pre3 :-{
Best regards
Martin
--
Martin Schröder, [EMAIL PROTECTED]
ArtCom GmbH, Grazer Straße 8, D-28359 Bremen
Voice +49 421 20419-44 / Fax +49 421 20419-10
PGP signature
Re: [Announce] mutt-1.1.9 is out - RELEASE CANDIDATE!
On Mon, Mar 13, 2000 at 02:16:40PM -0800, Gary Johnson wrote: > > Works like a charm on HP-UX 10.20 > > That's good news! I've had to hack the configure script of previous > releases (0.95.4 and 1.0) to get them to use the proper curses library > on my HP-UX 10.20 system. Is this still necessary? What curses/slang > library did you use? I use slang-1.4.0 -- the latest. Right now I'm trying to build PGP-6.5.1, the guy who made the hpux/aix patch is a moron. I had to give patch the filenames by hand... -- does GNUpg work on your HP-UX box? -- Ralf Hildebrandt <[EMAIL PROTECTED]> www.stahl.bau.tu-bs.de/~hildeb PP: MMDF gone mad with standards fever. Think "Brazil". PGP signature
Re: New Mail Polling
John P. Verel <[EMAIL PROTECTED]> wrote on Mon, 13 Mar 2000: > In poking around the mutt manual, I discovered that a) opening mutt > with the -y switch opens the directory browser with (apparently) > updated N indicator. Alternatively, pressing the tab key while in the > directory browser will do the same. Right, both are known methods. :-) Mutt can be full of these kind of "discoveries" (especially if you never bothered to read the manual thoroughly). > 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. Regards, 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 / "I am a veritable epitome of eloquence and -- umm, other stuff." -Anirion
Re: [Announce] mutt-1.1.9 is out - RELEASE CANDIDATE!
On 2000-03-14 10:15:41 +0100, Martin Schröder wrote:
> Just a reminder: There is a mutt-announce mailing list.
Thanks, I know.
> The last mail there announced 1.0pre3 :-{
The last mail I sent there announced 1.0.1.
Additionally, I have intentionally announced the public
1.1 betas to mutt-users, and not to mutt-announce, in
order to make sure we have a direct back-channel. 1.2
will be announced to mutt-announce.
--
http://www.guug.de/~roessler/
PGP signature
Re: selecting deleted messages
On Tue, Mar 14, 2000 at 12:15:37AM -0800, Eugene Lee wrote: (SNIP) > message as deleted, and moves my current select to message #38. As far > as I know, there is no mechanism within Mutt to remember your previous > selection; thus there's no way to automagically jump from message #38 > back to message #36. That was one of my questions... It would be a good implementation, wouldn't it? :-) -- Godoy. <[EMAIL PROTECTED]> Setor de Publicações Publishing Department Conectiva S.A.
Searching multiple folders
Hi, I am afraid this might be a FAQ, but all I could find was a detailed description of how to do it with pine, so here is my question: How can you search for mails in different folders (eg search through all the mailboxes you have in ~/Mail/)? Regards, Chris -- christian molls student of laws univ of cologne
Re: Searching multiple folders
Christian R Molls <[EMAIL PROTECTED]> wrote on Tue, 14 Mar 2000: > How can you search for mails in different folders (eg search through > all the mailboxes you have in ~/Mail/)? You can't do this with Mutt. You need to use maybe something like grep from the command line, or the grepmail program. Regards, 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 / "I have this nagging fear that everyone is out to make me paranoid."
Re: mutt-1.1.9 is out - RELEASE CANDIDATE!
> Sure. The problem has to do with the expansion of the $< macro. For > the HP-UX make, $< is evaluated only for inference rules. For GNU make, > $< is evaluated for both target and inference rules. At least one of > mutt's Makefiles (I don't remember offhand which one) has a target rule > that uses sed and $<. GNU make expands this $< to the source file name, > as the Makefile's author intended, and the build works fine. When the > HP-UX make gets to this point, however, it replaces $< with an empty > string which then leaves sed waiting for input from stdin and the build > hangs. That was in m4/Makefile.*, and it's has been fixed for a while now.
Re: selecting deleted messages
On Mon, Mar 13, 2000 at 08:35:56PM -0800, Gary Johnson wrote: > On Mon, Mar 13, 2000 at 08:16:18PM -0800, Gary Johnson wrote: > > On Tue, Mar 14, 2000 at 02:33:06AM +, J McKitrick wrote: > > > On Mon, Mar 13, 2000 at 04:50:40PM -0800, Gary Johnson wrote: > > Sorry about that. I didn't see the new messages in the other thread > until after I sent that. I've got to learn to read ALL the new messages > in the list before responding. That's OK gary, i need to read the whole thread before responding to the messages that didn't answer the question when the answer is just a little further down. :-) jm -- - Jonathon McKitrick / [EMAIL PROTECTED] \ "I prefer the term Artificial Person myself."/ -
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: New Mail Polling
On Tue, Mar 14, 2000 at 08:07:39AM -0500, Mike Markowski wrote: > Can you recommend any that don't conflict? I'm using xbiff, which > definitely does. Check out gbuffy by Brandon Long: http://www.fiction.net/blong/programs/gbuffy/ -- Ralf Hildebrandt <[EMAIL PROTECTED]> www.stahl.bau.tu-bs.de/~hildeb One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them.
Pgp signing
I am using pgp5 on a Linux box. I am not a large user of pgp right now, because I basically don't have the time to fiddle with it.. have one question for now. I notice that many signed messages have something of a very short key. I have fiddled with pgp enough in the past to realize that you can't do with pgp5 in unix. Is this the case? I only have a long key.. 1024 bit, or 768 -- /helfman "At any given moment, you may find the ticket to the circus that has always been in your possession."
PGP behavior
I just got PGP (v. 6.5.2) back on my Linux box, and seem to have forgotten how it's supposed to work. If I write a note to [EMAIL PROTECTED] and ask to encrypt and sign it, I get a prompt for the key ID of '[EMAIL PROTECTED]'. Pressing the return gets me a list of the public keys in my public key ring, with a '+' next to my entry, but *no* entries for bob, even though I know his key is on the ring. My one 'successful' attempt at the encrypt and sign operation resulted in me encrypting the message to myself, which carries the concept of eyes-only just a tad too far, wouldn't you agree? :^) What gives? Something simple, I guess, as I have not absorbed any coffee yet today. :^) Cheers... P.S. I'm signing this note with my new key. My old key (ca 1994) has been revoked, the key for which is on the PGP page of my web site. My "new" key seems to behave well with PGP, but key servers have a bad time with it...if anyone can shed light on this latter issue, I'd appreciate it. -- Alex Lane * Seabrook, Texas, USA -*- [EMAIL PROTECTED] * www.galexi.com/alex/ His idea of a balanced meal is a doughnout in each hand. (anon) PGP signature
Re: Pgp signing
On Tue, Mar 14, 2000 at 07:38:16AM -0600, Jason Helfman wrote: > I am using pgp5 on a Linux box. I am not a large user of pgp right now, > because I basically don't have the time to fiddle with it.. have one > question for now. I notice that many signed messages have something of a > very short key. I have fiddled with pgp enough in the past to realize > that you can't do with pgp5 in unix. Is this the case? I only have a > long key.. 1024 bit, or 768 Huh? I use 2.x, 5.x and 6.x and have no problems. -- Ralf Hildebrandt <[EMAIL PROTECTED]> www.stahl.bau.tu-bs.de/~hildeb I wish you'd tell me what kind of systems they're using instead, because HP can't be doing much worse than Sun "would you like the compiler or internet options with that" Microsystems, or Silicon "hey be glad the support-contract number isn't a 1-900" Graphics. Then there's Digital "It sucks in 64 bits, you can't suck in 64 bits anywhere else" Equipment Corp (Did we mention it's 64 bits?).
Re: [Announce] mutt-1.1.9 is out - RELEASE CANDIDATE!
On Tue, Mar 14, 2000 at 10:27:43AM +0100, Ralf Hildebrandt wrote: > I use slang-1.4.0 -- the latest. Right now I'm trying to build PGP-6.5.1, > the guy who made the hpux/aix patch is a moron. I had to give patch the > filenames by hand... -- does GNUpg work on your HP-UX box? I don't know about GNUpg--I've never tried it. -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | RF Communications Product Generation Unit | Spokane, Washington, USA
Re: mutt-1.1.9 is out - RELEASE CANDIDATE!
On Tue, Mar 14, 2000 at 11:35:53AM +, Lars Hecking wrote: > > Sure. The problem has to do with the expansion of the $< macro. For > That was in m4/Makefile.*, and it's has been fixed for a while now. That's good to hear, too. It appears that the fix may be only in the development branch though, as mutt-1.0-us/m4/Makefile still has the "sed ... $< ..." lines. -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | RF Communications Product Generation Unit | Spokane, Washington, USA
Re: mutt-1.1.9 is out - RELEASE CANDIDATE!
On Tuesday, 14 March 2000 at 11:35, Lars Hecking wrote: > > > Sure. The problem has to do with the expansion of the $< macro. For > > the HP-UX make, $< is evaluated only for inference rules. For GNU make, > > $< is evaluated for both target and inference rules. At least one of > > mutt's Makefiles (I don't remember offhand which one) has a target rule > > that uses sed and $<. GNU make expands this $< to the source file name, > > as the Makefile's author intended, and the build works fine. When the > > HP-UX make gets to this point, however, it replaces $< with an empty > > string which then leaves sed waiting for input from stdin and the build > > hangs. > > That was in m4/Makefile.*, and it's has been fixed for a while now. Well, it still doesn't build with NetBSD's make. I think the problem lies in automake. I believe there is a flag you can set in automake to get it to avoid gnuisms, though. PGP signature
Re: mutt-1.1.9 is out - RELEASE CANDIDATE!
> > That was in m4/Makefile.*, and it's has been fixed for a while now. > > That's good to hear, too. It appears that the fix may be only in the > development branch though, as mutt-1.0-us/m4/Makefile still has the > "sed ... $< ..." lines. That's right, I think this wasn't backfixed for 1.0. Easy to fix yourself, though :) > Well, it still doesn't build with NetBSD's make. I think the problem > lies in automake. I believe there is a flag you can set in automake to > get it to avoid gnuisms, though. This is in 1.1.9: $ grep AUTOMAKE_OPTIONS mutt-1.1.9/Makefile.am AUTOMAKE_OPTIONS = foreign IIRC it does work for me under NetBSD. What doesn't work, again IIRC, is 'make install DESTDIR=/foo'. make just drops the DESTDIR for some (but not all) targets. This was actually under OpenBSD, but I think I had the same problem with NetBSD, and I don't think the Makefile or automake is at fault.
Re: Pgp signing
On Tue, 14 Mar 2000, Jason Helfman wrote: > I am using pgp5 on a Linux box. I am not a large user of pgp right now, > because I basically don't have the time to fiddle with it.. have one > question for now. I notice that many signed messages have something of a > very short key. I have fiddled with pgp enough in the past to realize > that you can't do with pgp5 in unix. Is this the case? I only have a > long key.. 1024 bit, or 768 Could you be referring to the PGP fingerprints? Fingerprints aren't signing a message, but more a way of making sure that the key that Bob uses is the same key that you have for Bob. Here's an example of a PGP fingerprint: 9702 984B 27CF 96A4 F4A5 4F9B FA9A BDED A186 B570 Jag
Re: mutt-1.1.9 is out - RELEASE CANDIDATE!
Ralf Hildebrandt <[EMAIL PROTECTED]> wrote: > > does GNUpg work on your HP-UX box? It runs fine here, on HP-UX 10.20. I don't remember having to do more than the usual contortions to build on HP-UX. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: mutt-1.1.9 is out - RELEASE CANDIDATE!
Gary Johnson <[EMAIL PROTECTED]> wrote: > > CPPFLAGS="$CPPFLAGS -I/usr/include/curses_colr" > LIBS="$LIBS -lcur_colr" I have done this myself, and while the resulting Mutt does build, I found that the color support does not work. I haven't tried it lately, though. Do you get correct colors with this? -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Q: new mail
Dear group, Is there any way to tell mutt to inform me if new mail has arrived? At the moment I am using xbiff for that purpose but I would like to get rid of it. Tehanks in advance. Regards, Marc van Dongen -- Marc van Dongen, CS Dept | phone: +353 21 4903578 University College Cork, NUIC | Fax:+353 21 4903113 College Road, Cork, Ireland | Email: [EMAIL PROTECTED]
mutt shouldn't write back unchanged mh messages
When reading an mh folder mutt 1.0.1 apparently loads every message, and, when you quit, writes every message back to disk. (Is that true for maildir too?) That's surely a bug, right? The whole point of one-file-per-message formats is that you only touch the data you need to, and leave the rest alone. Otherwise, with a large folder, mutt is unusably slow, and it also destroys e.g. timestamp information on old files.
Re: New Mail Polling
Telsa Gwynne <[EMAIL PROTECTED]> wrote on Mon, 13 Mar 2000: > And the N for > "new mail" is very intermittent on the listing of folders (for which > I too have forgotten the correct name). > > There are one or two folders which never seem to show up as having > new mail in them. They're listed in mailboxes in my .muttrc just like > the rest. David DeSimone posted a few days ago a very good reply in another thread which explains how Mutt detects new mail (for the usual mbox folders). Basically, it compares the "last accessed" and "last modified" times for a file. If "last modified" is later than "last accessed", the the folder is marked in the Mailboxes or directory listing as containing new mail. If a folder is not marked as containing new mail, it means that Mutt saw that the modified time was earlier or equal to the accessed time. Why this happens is anyone's guess. Possible common causes: - another new mail checking application which disturbs the "last accessed" time when it checks a folder for new mail, for example a shell's new mail listing or a "biff" type application - the mbox is read over NFS, and the timestamps get mangled because of that (at least, that's what I've heard claimed) Also something to try is to set $save_empty, at least for your incoming folders (with a folder-hook), which will keep the mail folder file around even if it's empty. I remember once experiencing similar problems which were solved with this, because the file got created with new mail and had lass access time being equal to last modification time, which is not enough (last modification needs to be *later*, not equal). 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 / *** WANRING -- this signature quote is spellt wrong. ***
Re: Q: new mail
Marc van Dongen <[EMAIL PROTECTED]> wrote on Tue, 14 Mar 2000: > Is there any way to tell mutt to inform me if new > mail has arrived? At the moment I am using xbiff > for that purpose but I would like to get rid of it. Sure. List your incoming mailboxes with the "mailboxes" command in your .muttrc. For more info, look up the command's entry in the manual. Regards, 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 / "I am a veritable epitome of eloquence and -- umm, other stuff." -Anirion
Re: mutt shouldn't write back unchanged mh messages
Scott Schwartz <[EMAIL PROTECTED]> wrote: > When reading an mh folder mutt 1.0.1 apparently loads every message, > and, when you quit, writes every message back to disk. Well, the files have to be at least renamed, because mh requires the filenames be contiguous integers. IIRC, the message flags are also stored inside the files, so mutt would have to rewrite the files to change the read, replied, etc flags. > (Is that true > for maildir too?) No. The files in a Maildir do not have to be rewritten, as flags are stored in the filenames. And since the filenames don't have to be successive integers (in fact, they can't be, there's a defined format), only the changed messages are renamed on closing a folder. > That's surely a bug, right? The whole point of > one-file-per-message formats is that you only touch the data you need > to, and leave the rest alone. Otherwise, with a large folder, mutt is > unusably slow, and it also destroys e.g. timestamp information on old > files. It's not a bug in mutt. mh is broken by design; try Maildirs instead. Charles -- Charles Cazabon <[EMAIL PROTECTED]> Any opinions expressed are just that -- my opinions.
Re: formatting and printing messages with long lines
My previous question was : > > Hello, > > > > I'm searching a solution to properly print messages with paragraphs in long single >lines (in fact, like this one...). On Sun, Mar 12, 2000 at 03:35:40PM -0500, John P. Verel wrote: > > I use enscript with excellent results. Here's the entry from my > .muttrc file: > > set print_command="enscript -f "Times-Roman11" -F "TimesRoman14" -G -i3" > > Give it a try! > > John I add : enscript with the option --word-wrap And since, I've found another solution with mpage (interessant for people who doesn't have installed enscript, since mpage comes with all Redhat-print-filters) : set print_command="fmt -s | mpage -1 -f | lpr -" Gauthier
I liked the old "weed" behavior (was [Announce] mutt-1.1.9 ...)
On Mon, Mar 13, 2000 at 02:03:37PM -0500, Thomas Roessler wrote: > "Thomas" == Thomas Roessler <[EMAIL PROTECTED]> writes: Thomas> Changes against 1.1.8 are a couple of bug-fixes. Unless someone Thomas> has some real show-stoppers, I'd consider this to be a release Thomas> candidate for 1.2, and release that version later that week. Thomas> If someone objects, please speak up now or be silent forever. ;-) Well, this certainly isn't a showstopper but it is annoying. I liked the old behavior where the full headers were included when replying -- I use sc in emacs and it needs all the headers to work properly. I've worked around it by using send-hook . 'unset weed' I am assuming the reason for the change was consistency. If was some other reason, could we go back to the old way. As I said, not a showstopper but my 2 cents. -- Eric M. Boehm [EMAIL PROTECTED]
one mailboxes, no new mail found
Hi, I have several folders, but in two of them no new mail is noticed (when browsing thru folders with new mail or looking for folders marked with N in the folderlist). One of them is /home/rejo/mail/spam-usenet, although i seem to have set up everything correct: $ la mail/spam* -rw--- 1 rejo users 2583240 Mar 13 20:34 mail/spam -rw--- 1 rejo users 1659461 Mar 14 20:34 mail/spam-usenet $ grep folder= .muttrc set folder=$HOME/mail $ grep =spam-usenet .muttrc mailboxes =spam-usenet Any idea? -Rejo. -- = Rejo Zenger [Sister Ray Crisiscentrum] [EMAIL PROTECTED] = http://mediaport.org/~sister (and my_urls.html) PGP: see headers Destroy a spamhaus! http://www.xs4all.nl/~sister/mirror/sengir/spam_sites.html
Re: mutt shouldn't write back unchanged mh messages
| Well, the files have to be at least renamed, because mh requires the filenames | be contiguous integers. No it doesn't. They usually are not. | IIRC, the message flags are also stored inside the | files, so mutt would have to rewrite the files to change the read, replied, | etc flags. It seems to me that mutt changes files that have not been read, replied, or anything else. That doesn't seem useful. Mh doesn't store "read" flags in any messages files. It uses the sequence mechanism for that, which mutt has unfortunately stopped supporting. | It's not a bug in mutt. mh is broken by design; try Maildirs instead. In my experience mh works well enough, but mutt makes some incorrect assumptions that have painful consequences.
Re: mutt-1.1.9 is out - RELEASE CANDIDATE!
On Tue, Mar 14, 2000 at 12:01:12PM -0800, Gary Johnson wrote: > Many of the text applications I've seen that have used color have used > it in a way that I found either not useful, distracting or hideous. I can certainly see how you would say that. But the nice thing about mutt is it is extremely configurable, and that goes for colors as well, of course. You can use as much or as little as you like. It comes in handy for From fields, the threads tree indicators, blocking off quoted materials, the status line, and a host of other things. And again, you can be liberal or sparse with it. When i connect from a mono terminal, it simply defaults to reverse video where necessary, and is extremely readable. jm -- - Jonathon McKitrick / [EMAIL PROTECTED] \ "I prefer the term Artificial Person myself."/ -
Re: Pgp signing
super, do you think you can tell me something about it? what command would I use to sign messages with a short signature i use this all the time... http://clug.chicago.il.us:11371/pks/lookup?op=get&search=0x60618246 /jgh - Original Message - From: Ralf Hildebrandt <[EMAIL PROTECTED]> Date: Tuesday, March 14, 2000 8:33 am Subject: Re: Pgp signing > On Tue, Mar 14, 2000 at 07:38:16AM -0600, Jason Helfman wrote: > > I am using pgp5 on a Linux box. I am not a large user of pgp > right now, > > because I basically don't have the time to fiddle with it.. > have one > > question for now. I notice that many signed messages have > something of a > > very short key. I have fiddled with pgp enough in the past to > realize> that you can't do with pgp5 in unix. Is this the case? I > only have a > > long key.. 1024 bit, or 768 > > Huh? I use 2.x, 5.x and 6.x and have no problems. > > -- > Ralf Hildebrandt <[EMAIL PROTECTED]> www.stahl.bau.tu- > bs.de/~hildebI wish you'd tell me what kind of systems they're > using instead, > because HP can't be doing much worse than Sun "would you like the > compiler or internet options with that" Microsystems, or Silicon "hey > be glad the support-contract number isn't a 1-900" Graphics. Then > there's Digital "It sucks in 64 bits, you can't suck in 64 bits > anywhere else" Equipment Corp (Did we mention it's 64 bits?). > >
Re: mutt-1.1.9 is out - RELEASE CANDIDATE!
On Tue, Mar 14, 2000 at 11:57:25AM -0600, David DeSimone wrote: > Gary Johnson <[EMAIL PROTECTED]> wrote: > > > > CPPFLAGS="$CPPFLAGS -I/usr/include/curses_colr" > > LIBS="$LIBS -lcur_colr" > > I have done this myself, and while the resulting Mutt does build, I > found that the color support does not work. I haven't tried it lately, > though. Do you get correct colors with this? I don't know--I've never tried to get colors to work in mutt. Many of the text applications I've seen that have used color have used it in a way that I found either not useful, distracting or hideous. I've also avoided color as a means to convey information because it's usually lost when printed or photocopied and because several of my co-workers are color blind. So my motivation to get color working is generally low. That being said, I do like using gvim's syntax coloring when I'm editing HTML files. I tried using syntax coloring with vim running in both hpterm and xterm windows on this system, but all I got was combinations of bold, inverse video and underlining. I think the problem may be with hpterm or xterm, but I haven't done any serious investigation. -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | RF Communications Product Generation Unit | Spokane, Washington, USA
Re: mutt-1.1.9 is out - RELEASE CANDIDATE!
Gary Johnson <[EMAIL PROTECTED]> wrote:
>
> > > CPPFLAGS="$CPPFLAGS -I/usr/include/curses_colr"
> > > LIBS="$LIBS -lcur_colr"
> >
> > I have done this myself, and while the resulting Mutt does build, I
> > found that the color support does not work. I haven't tried it lately,
> > though. Do you get correct colors with this?
>
> I don't know--I've never tried to get colors to work in mutt.
Well, being the curious type, I just tried it, and the colors indeed
have problems. I don't know if this is HP's curses' fault, or my
terminfo's fault, or my xterm's fault, but I do know that Mutt+{ncurses/
slang}+{this-xterm} = working colors, so I suspect the curses library.
But you are correct that Mutt will successfully compile when built this
way, because symbols such as COLOR_BLACK will become defined. I guess
nobody has noticed that Mutt won't build with a curses library that
doesn't even comprehend colors? Oh well.
> Many of the text applications I've seen that have used color have used
> it in a way that I found either not useful, distracting or hideous.
I shared your opinion of colors, until I tried it with Mutt.
> I've also avoided color as a means to convey information because it's
> usually lost when printed or photocopied and because several of my
> co-workers are color blind.
I agree that color ability should never be assumed in one's colleagues,
but I find that, for me, the color helps me to visually separate parts
of messages more easily than I otherwise would. I can more easily scan
past quoted sections of text (because they are in a different color)
without accidentally missing new text that might have been added. I am
certainly still able to, say, distinguish a message's headers from its
body, or quoted text from non-quoted, but the color simply makes the
process easier and less error-prone.
--
David DeSimone | "The doctrine of human equality reposes on this:
[EMAIL PROTECTED] | that there is no man really clever who has not
Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson
UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Mutt 1.1.9 about 3-4x slower than mutt 1.0 (was Re: [Announce] mutt-1.1.9 is out - RELEASE CANDIDATE!)
On Mon, Mar 13, 2000 at 02:03:37PM -0500, Thomas Roessler wrote: > "Thomas" == Thomas Roessler <[EMAIL PROTECTED]> writes: Thomas> Changes against 1.1.8 are a couple of bug-fixes. Unless someone Thomas> has some real show-stoppers, I'd consider this to be a release Thomas> candidate for 1.2, and release that version later that week. I have found that mutt 1.1.9 is about 4x slower reading a 7.4 MB mail file with 1451 messages in it than mutt 1.0. I tried this several times to eliminate the effects of caching. It took mutt 1.0 about 7.8 seconds to bring up the file, it took mutt 1.1.9 about 28.8 seconds to bring up the same file. I don't know if you would consider this a show stopper but it was enough for me to back out 1.1.9 and go back to 1.0. -- Eric M. Boehm [EMAIL PROTECTED]
Re: PGP behavior
* On Tue, Mar 14, 2000 at 08:20:16AM -0600, Alex Lane wrote: > I just got PGP (v. 6.5.2) back on my Linux box, and seem to have > forgotten how it's supposed to work. > > If I write a note to [EMAIL PROTECTED] and ask to encrypt and sign it, I get a > prompt for the key ID of '[EMAIL PROTECTED]'. Pressing the return gets me a > list of the public keys in my public key ring, with a '+' next to my > entry, but *no* entries for bob, even though I know his key is on the > ring. My one 'successful' attempt at the encrypt and sign operation > resulted in me encrypting the message to myself, which carries the > concept of eyes-only just a tad too far, wouldn't you agree? :^) > > What gives? Something simple, I guess, as I have not absorbed any > coffee yet today. :^) > I will check out the newest version of mutt, my 1.0i has a lot of trouble distinguishing my key from my revoked key (keeps trying to check my passphrase against my revoked key), and just who, exactly, mutt extracts from my public key ring is a mystery...all I can tell right now is...it isn't everyone. Cheers... -- Alex Lane * Seabrook, Texas, USA -*- [EMAIL PROTECTED] * www.galexi.com/alex/ Do. Or do not. There is no 'try'.(Yoda) PGP signature
Re: Mutt 1.1.9 about 3-4x slower than mutt 1.0 (was Re: [Announce] mutt-1.1.9 is out - RELEASE CANDIDATE!)
Eric Boehm <[EMAIL PROTECTED]> wrote: > > I have found that mutt 1.1.9 is about 4x slower reading a 7.4 MB mail > file with 1451 messages in it than mutt 1.0. NFS? What type(s) of file locking? Differences in "mutt -v" output? > I don't know if you would consider this a show stopper but it was > enough for me to back out 1.1.9 and go back to 1.0. It would be incredible if such a slow-down escaped the notice of any of the developers. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: New Mail Polling
On 03/14/00, 09:36:28PM +0200, Mikko Hänninen wrote: > > David DeSimone posted a few days ago a very good reply in another thread > which explains how Mutt detects new mail (for the usual mbox folders). > Basically, it compares the "last accessed" and "last modified" times for > a file. If "last modified" is later than "last accessed", the the > folder is marked in the Mailboxes or directory listing as containing new > mail. > How and when does mutt update the folder browser? Is it necessary to press tab twice to re-write the screen? Thanks, Mikko :)
Re: New Mail Polling
John P. Verel <[EMAIL PROTECTED]> wrote on Tue, 14 Mar 2000: > How and when does mutt update the folder browser? Is it necessary to > press tab twice to re-write the screen? There's a function called check-new in the directory listing (and Mailboxes) screen, but it's unbound by default. Bind it to a key of your choice. > Thanks, Mikko :) You're welcome. :-) Regards, 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 / Sapere Aude - Dare to Know -- Immanuel Kant
Threading
What causes a "thread" of messages to break on occasion ?? Is the fault of the sender or their e-mailer ?? What happens every once in a while is I can have a thread of messages grouped together like they should be and then, for instance, the next time my mail is checked, a new message that *should* be grouped with the others in the thread stay at the bottom of my list. Pressing "$" syncs my mailbox, right ?? Could it or should it also fix any stray messages ?? Or, as I mentioned above, does the guilty e-mail program somehow change a header or something similar that messes things up ?? Regards, Hall Stevenson
Re: Mutt 1.1.9 about 3-4x slower than mutt 1.0 (was Re: [Announce] mutt-1.1.9 is out - RELEASE CANDIDATE!)
On Tue, Mar 14, 2000 at 06:59:48PM -0600, David DeSimone wrote: > "David" == David DeSimone <[EMAIL PROTECTED]> writes: Eric> I have found that mutt 1.1.9 is about 4x slower reading a 7.4 MB Eric> mail file with 1451 messages in it than mutt 1.0. David> NFS? What type(s) of file locking? Differences in "mutt -v" David> output? Yes, across NFS. I copied the file to a local drive and ran both mutts. The time was about the same (1.8 sec). Both mutts were also run from a local drive. My system is an Ultra 60 with two 450MHz processors. Network is 10BT (dedicated through an ethernet switch to ATM backbone). OS is Solaris 2.6 with relatively up-to-date patches. Eric> I don't know if you would consider this a show stopper but it was Eric> enough for me to back out 1.1.9 and go back to 1.0. The file normally resides in my home directory which is NFS mounted from an Auspex. Relevant output from nfsstat -m /home/ax10 from brtpyc9d:/home/ax10 Flags: vers=3,proto=udp,sec=sys,hard,intr,link,symlink,rsize=32768,wsize=32768,retrans=5 Lookups: srtt=8 (20ms), dev=4 (20ms), cur=3 (60ms) Reads: srtt=46 (115ms), dev=5 (25ms), cur=8 (160ms) Writes: srtt=45 (112ms), dev=18 (90ms), cur=14 (280ms) All: srtt=8 (20ms), dev=4 (20ms), cur=3 (60ms) brtpyc9d is an interface on the same subnet as my workstation. I've attached mutt -v output. They are essentially the same except for options added or removed between the two releases. David> It would be incredible if such a slow-down escaped the notice of David> any of the developers. Interestingly enough, I rebuilt both under HP-UX 10.20 and I got similar times to bring up the same file (across NFS) with both versions (about 20 sec). I've attached the mutt -v output for both versions under HP-UX 10.20. I went back and rebuilt both versions under Solaris 2.6. I still get the same reults -- 7.9 secs for mutt 1.0, 29-30 secs for mutt 1.1.9. I'm open to other suggestions/explanations. -- Eric M. Boehm [EMAIL PROTECTED] Mutt 1.0i (1999-10-22) Copyright (C) 1996-9 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: SunOS 5.6 [using slang 10201] Compile options: DOMAIN="nortelnetworks.com" -HOMESPOOL -USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK +USE_IMAP +USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_PGP2 +BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL="/usr/lib/sendmail" MAILPATH="/var/mail" SHAREDIR="/opt/corp/mnt/spm/admin/share/mutt" SYSCONFDIR="/opt/corp/mnt/spm/admin/etc" ISPELL="/bnr/contrib/bin/ispell" _PGPPATH="/home/ax10/boehm/bin/sun/pgp" _PGPV2PATH="/home/ax10/boehm/bin/sun/pgp" To contact the developers, please mail to <[EMAIL PROTECTED]>. Mutt 1.1.9i (2000-03-13) Copyright (C) 1996-2000 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: SunOS 5.6 [using slang 10201] Compile options: DOMAIN="nortelnetworks.com" -HOMESPOOL -USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK +USE_IMAP -USE_GSS -USE_SSL +USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_PGP +BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL="/usr/lib/sendmail" MAILPATH="/var/mail" SHAREDIR="/opt/corp/mnt/spm/admin/share/mutt" SYSCONFDIR="/opt/corp/mnt/spm/admin/etc" ISPELL="/bnr/contrib/bin/ispell" To contact the developers, please mail to <[EMAIL PROTECTED]>. To report a bug, please use the muttbug utility. Mutt 0.95.5i (1999-04-23) Copyright (C) 1996-8 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: HP-UX B.10.20 [using slang 10201] Compile options: -DOMAIN -HOMESPOOL +USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK +USE_IMAP +USE_POP -HAVE_REGCOMP +USE_GNU_REGEX +HAVE_COLOR +HAVE_PGP2 +-BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/mail" SHAREDIR="/opt/corp/mnt/spm/admin/share/mutt" SYSCONFDIR="/opt/corp/mnt/spm/admin/etc" ISPELL="/bnr/contrib/bin/ispell" _PGPPATH="/home/ax10/boehm/bin/hppa/pgp" _PGPV2PATH="/home/ax10/boehm/bin/hppa/pgp" To contact the developers, please mail to <[EMAIL PROTECTED]>. Mutt 0.95.5i (1999-04-23) Copyright (C) 1996-8 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: HP-UX B.10.20 [using slang 10201] Compile options: -DOMAIN -HOMESPOOL +USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK +USE_IMAP +USE_POP
Eudora to Mbox
I remember someone mentioning of wanting to convert their large addressbook in Eudora to Mutt...I found this on freshmeat and some other cool utils, by just searching for "mutt" http://provo.doit.wisc.edu/~miner/eud2mbox/ -- /helfman "At any given moment, you may find the ticket to the circus that has always been in your possession."
Re: Threading
At 21:11 -0500 14 Mar 2000, Hall Stevenson <[EMAIL PROTECTED]> wrote: > What causes a "thread" of messages to break on occasion ?? Is the fault > of the sender or their e-mailer ?? > > What happens every once in a while is I can have a thread of messages > grouped together like they should be and then, for instance, the next > time my mail is checked, a new message that *should* be grouped with the > others in the thread stay at the bottom of my list. Mutt has two methods of threading, the preferred way is by message IDs. Here it matches up the Message-ID header with IDs found in the References or In-Reply-To header of any replies to that message. When this type of threading breaks, it's usually the fault of the persons mail client. In most cases a mail client will always send broken (with regards to threading) messages or it will never do so. But there's a long standing bug in Eudora that causes it to occasionally send broken headers. If mutt can't do reference based threading and $strict_threads isn't set, it will try threading based on the subject. This will only be able to group the messages together, it won't be able to display a thread tree. This can sometimes break because of subtle changes to the subject. > Pressing "$" syncs my mailbox, right ?? Could it or should it also fix > any stray messages ?? Or, as I mentioned above, does the guilty e-mail Yes, with the default bindings, the '$' key will cause mutt to sync your mailbox. If this does cause a message to be threaded correctly, it's a bug that this wasn't done in the first place. Aaron Schrab <[EMAIL PROTECTED]> :) -- Aaron Schrab [EMAIL PROTECTED] http://www.execpc.com/~aarons/ Real programmers can write assembly code in any language. :-) --Larry Wall
Re: Mutt 1.1.9 about 3-4x slower than mutt 1.0 (was Re: [Announce] mutt-1.1.9 is out - RELEASE CANDIDATE!)
On Tuesday, 14 March 2000 at 21:23, Eric Boehm wrote: > On Tue, Mar 14, 2000 at 06:59:48PM -0600, David DeSimone wrote: > > "David" == David DeSimone <[EMAIL PROTECTED]> writes: > > Eric> I have found that mutt 1.1.9 is about 4x slower reading a 7.4 MB > Eric> mail file with 1451 messages in it than mutt 1.0. > > David> NFS? What type(s) of file locking? Differences in "mutt -v" > David> output? > > Yes, across NFS. I copied the file to a local drive and ran both mutts. The > time was about the same (1.8 sec). Both mutts were also run from a local > drive. > > Interestingly enough, I rebuilt both under HP-UX 10.20 and I got similar times > to bring up the same file (across NFS) with both versions (about 20 sec). I've > attached the mutt -v output for both versions under HP-UX 10.20. > > I went back and rebuilt both versions under Solaris 2.6. I still get the same > reults -- 7.9 secs for mutt 1.0, 29-30 secs for mutt 1.1.9. > > I'm open to other suggestions/explanations. I don't have any answer, but I do seem to recall that file locking was made more paranoid during 1.1, due to NFS snafus which could cause lost mail. I would guess the culprit might be there... maybe you could try forcing flock instead of fcntl to test (not that I'd recommend running that way) - don't write to the folder, just open it... really I'm just guessing. -Brendan PGP signature
Certificates update?
Hi, Over the past few months I've seen the odd message on the list concerning the use of certifcates with Mutt. I also remember someone posting about the use of OpenSSL and potentially calling this from within Mutt. I was wondering whether anything further has come of this and what the future holds? Thanks, N. Neil van der Merwe National Operations Manager Dimension Data Security www.didata.co.za Tel (Reception): +27-11-709-1000 Tel (Direct):+27-11-709-1052 Fax: +27-11-283-5401 Mail: [EMAIL PROTECTED] PGP fingerprint=EF C6 98 DD E5 3A EF 56 10 B9 28 39 2B 63 52 5F PGP signature
Re: PGP behavior
Keeping in mind this is not a PGP mail list, I nonetheless would be appreciative if anyone could explain why I get a signal 11 error when running pgp 6.5.2. The mutt docs I've looked at distinguish pgp2 and pgp5; is 6.5.2 a completely different animal? I may be taking a oversimplified view of things, but mutt 1.0i-2 (rpm distro for RHL 6.0) expects to see '/usr/bin/pgps' when I specify pgp5 in the .muttrc file, apparently. So, I've tried renaming the pgp that came from Network Associates, and I've tried creating a symbolic link to the executable so that I can invoke 'pgps' and execute the file. What might I be doing wrong? Cheers... -- Alex Lane * Seabrook, Texas, USA -*- [EMAIL PROTECTED] * www.galexi.com/alex/ Fall seven times and stand up eight.(Japanese proverb)
