Re: [Announce] mutt-1.1.9 is out - RELEASE CANDIDATE!
On Sun, Mar 19, 2000 at 18:13:16 -0500, David T-G wrote: Can the authors or maintainers of the patches let me know if any of them are obsoleted or need to be updated, and where to get them? I'm now updating my patches (those with "bj" in their filenames) to the soon-coming Mutt 1.2. More info and descriptions will follow when I'm ready. -- Byrial
Re: two mutt 1.1.9 problems(?) (was: [Announce] mutt-1.1.9 is out - RELEASE CANDIDATE!)
On 2000-03-20 01:27:51 +, Thomas Ribbrock wrote: I have a slight problem with Muttrc in the 1.1.9. In 1.0.1 and before, the Muttrc that got installed was automatically changed during install to contain the correct path to "manual.txt" according to --prefix. This no longer works for 1.1.9. Even after configuring with --prefix, the installed Muttrc still contains "/usr/local/." as path to manual.txt NEWS states that the mechanism to generate Muttrc has been changed, so maybe this was an oversight? Or did I miss something? This was an oversight when changing the Muttrc generation mechanism. I've put Muttrc.head under autoconf control now. -- http://www.guug.de/~roessler/
Charset problem ?
Whenever mutt displays a thread, the arrows look like "AA" with little accents on top. I'm using iso-8859-1 which I think is the default. Oddly enough, mutt can display french characters in messages. Am I trading one for the other? Which charset should I be using to support threads? Thanks, js. -- Jean-Sebastien Morisset, Sr. UNIX Admin [EMAIL PROTECTED] Reseau d'informations scientifiques du Quebec (RISQ) inc. This is Linux Country. On a quiet night you can hear Windows NT reboot! PGP signature
Trouble getting indicator to point to first message
Hi, I want to read my mail FIFO (ie oldest mail first). I don't have any "set sort" commands in my .muttrc, so mutt's defaulting to "date", which is just fine. However, the indicator goes to message 300, instead of message 1 when I start mutt. Is there an option to have the indicator go to message 1 at startup that I've missed in the manual? If not, is there any other way to accomplish this, please? $ mutt -v Mutt 1.0.1i (2000-01-18) 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 10400] Compile options: -DOMAIN -HOMESPOOL -USE_SETGID +USE_DOTLOCK -USE_FCNTL -USE_FLOCK -USE_IMAP -USE_POP -HAVE_REGCOMP +USE_GNU_REGEX +HAVE_COLOR -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL="/usr/lib/sendmail" MAILPATH="/var/mail" SHAREDIR="/usr/local/share/mutt" SYSCONFDIR="/usr/local/etc" ISPELL="/usr/local/bin/ispell" To contact the developers, please mail to [EMAIL PROTECTED]. $ uname -a SunOS tashkent 5.6 Generic_105181-16 sun4u sparc SUNW,Ultra-5_10 $ Sincerely Yours, Aleksey Tsalolikhin
Re: Trouble getting indicator to point to first message
Aleksey Tsalolikhin [EMAIL PROTECTED] wrote on Mon, 20 Mar 2000: However, the indicator goes to message 300, instead of message 1 when I start mutt. Is there an option to have the indicator go to message 1 at startup that I've missed in the manual? If not, is there any other way to accomplish this, please? Not really an option, but a supported method would be to set up a folder hook in your .muttrc, which matches all folders: folder-hook . 'push "1enter"' Seemed to work fine when I quickly tested that just now. 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 / Support bacteria -- it's the only culture some people have.
Re: Trouble getting indicator to point to first message
Hi, folks -- ...and then Mikko Hänninen said... % Aleksey Tsalolikhin [EMAIL PROTECTED] wrote on Mon, 20 Mar 2000: % of message 1 when I start mutt. Is there an option to have % the indicator go to message 1 at startup that I've missed % % Not really an option, but a supported method would be to set up a % folder hook in your .muttrc, which matches all folders: % % folder-hook . 'push "1enter"' This is all I could come up with, too, but it's IMHO a kludge. Do I incorrectly remember a point_new variable that would cause mutt to jump to the first new message, which is what most people want anyway but some don't, which is now obviously not there? Or did I make it up? :-) :-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: Trouble getting indicator to point to first message
David T-G [EMAIL PROTECTED] wrote on Mon, 20 Mar 2000: % folder-hook . 'push "1enter"' This is all I could come up with, too, but it's IMHO a kludge. Why is it a kludge? It works, it's quite simple, and it doesn't seem to add a significant overhead in the folder processing.. Maybe that you need to use "push" is a bit kludgey, since I couldn't figure out a way to invoke the jump function without it (I get "jump: unknown command" and "jump: unknown command"). Do I incorrectly remember a point_new variable that would cause mutt to jump to the first new message, which is what most people want anyway but some don't, which is now obviously not there? Or did I make it up? :-) Well, at least on my 1.1.9 I get "point_new: unknown variable" when I try to do ":set ?point_new"... And a quick grep from all the manuals I had (going back to version 0.85) didn't turn up anything either. 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 / There is nothing in the world stronger than gentleness.
Printing with only some headers
Hi, how can I make mutt print only some (ie important) header lines? Right now I use: set print_command='enscript -2 -r -G -i3' which results in all headers being printed. So I piped the mail through sed/formail before passing it to enscript, and that worked, but I wonder if there is a nicer way to do it? Maybe with a mailcap-print setting? Chris -- christian molls student of laws univ of cologne
Trouble with fcc-save-hook . +%F
Dear mutt-users, i try to migrate from an german mail+news reader "CrossPoint" (runs on pure DOS) to mutt. With CrossPoint i'm used to save mails i got from a user and copys of emails i sent her (the whole correspondence) in one location (aka folder). Now i tried hard configuring mutt to fcc and save emails in folders with users realnames. But if i setfcc-save-hook . +%Femails i send go to a folder 'To Firstname Lastname' whereas emails i got and save go to folder 'Firstname Lastname': The correspondence is splitt in two folders and as a result i can not read it without changing folders all the time. Any suggestions? Ciao, Gregor
Re: Trouble getting indicator to point to first message
Mikko -- ...and then Mikko Hänninen said... % David T-G [EMAIL PROTECTED] wrote on Mon, 20 Mar 2000: % % folder-hook . 'push "1enter"' % % This is all I could come up with, too, but it's IMHO a kludge. % % Why is it a kludge? It works, it's quite simple, and it doesn't seem to % add a significant overhead in the folder processing.. Maybe that you Well, it's noticeable to me; mutt opens up the folder, paints the index, and then has to re-paint it from message 1. Even with "modern" fast dialup lines, which don't always apply even for me here in the states, it's quite noticeable. % need to use "push" is a bit kludgey, since I couldn't figure out a way % to invoke the jump function without it (I get "jump: unknown command" % and "jump: unknown command"). It just seems to me that there should be a way to not point to the first new message if you don't want to. % % Do I incorrectly remember a point_new variable that would cause mutt to % jump to the first new message, which is what most people want anyway but % some don't, which is now obviously not there? Or did I make it up? :-) % % Well, at least on my 1.1.9 I get "point_new: unknown variable" when I % try to do ":set ?point_new"... And a quick grep from all the manuals % I had (going back to version 0.85) didn't turn up anything either. Since I signed on at in the 0.88 days, I must have made it up entirely. Bummer; I was sure it was there :-) % % % Regards, % Mikko :-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: Trouble getting indicator to point to first message
David T-G [EMAIL PROTECTED] wrote on Mon, 20 Mar 2000: Well, it's noticeable to me; mutt opens up the folder, paints the index, and then has to re-paint it from message 1. Even with "modern" fast dialup lines, which don't always apply even for me here in the states, it's quite noticeable. Okay, then I agree you have a point here. I guess I've just been spoiled by not having to use remote access over dialup modem connections at all in about 1.5 years... It just seems to me that there should be a way to not point to the first new message if you don't want to. True, although the desire to do so seems to be quite rare. Since I signed on at in the 0.88 days, I must have made it up entirely. Bummer; I was sure it was there :-) Maybe it was a patch... Or my grep may have missed it. 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 / "If you're not impossible to tolerate, you're not trying hard enough."
Re: Trouble getting indicator to point to first message
Mikko Hänninen [EMAIL PROTECTED] wrote: folder-hook . 'push "1enter"' A bit more efficient: folder-hook . 'push first-entry' -- 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
How could i deal with this in Procmail or Mutt?
How would I work with this and kill the messages taht I send? #You have added to the subscriber list of: # #[EMAIL PROTECTED] # #the following mail address: # #[EMAIL PROTECTED] # #By default, copies of your own submissions will be returned -- /helfman "At any given moment, you may find the ticket to the circus that has always beenin your possession." Fingerprint: 2F76 2856 776A 3E07 9F3E 452A 17D9 9B28 D75E 0A36 GnuPG http://www.gnupg.org Get Private! PGP signature
Re: How could i deal with this in Procmail or Mutt?
On Mon, Mar 20, 2000 at 11:22:41PM -0600, Jason Helfman wrote: How would I work with this and kill the messages taht I send? #You have added to the subscriber list of: # #[EMAIL PROTECTED] # #the following mail address: # #[EMAIL PROTECTED] # #By default, copies of your own submissions will be returned -- Dear Jason, Something like :0 * ^From gnupg-users-owner * ^From: Jason Helfman [EMAIL PROTECTED] /dev/null in your procmailrc ought to do it, if you don't want to see your own posts to gnupg-users. You might have to tweak the 'From ' line in the recipe depending on what it actually looks like when you get email from the list. Yours, Aleksey
Re: Trouble getting indicator to point to first message
On Mon, Mar 20, 2000 at 17:22:01 -0500, David T-G wrote:
Well, it's noticeable to me; mutt opens up the folder, paints the index,
and then has to re-paint it from message 1. Even with "modern" fast
dialup lines, which don't always apply even for me here in the states,
it's quite noticeable.
It just seems to me that there should be a way to not point to the first
new message if you don't want to.
With the source everything is possible. :-)
One way is to edit curs_main.c, find the function ci_first_message(),
delete all code lines but the last so the function looks like this:
static int ci_first_message (void)
{
return 0;
}
Then recompile and be happy.
--
Byrial
Re: Trouble getting indicator to point to first message
On Mon, Mar 20, 2000 at 22:52:31 +0200, Mikko Hänninen wrote: Why is it a kludge? It works, it's quite simple, and it doesn't seem to add a significant overhead in the folder processing.. Maybe that you need to use "push" is a bit kludgey, since I couldn't figure out a way to invoke the jump function without it (I get "jump: unknown command" and "jump: unknown command"). I would prefer to name the jump function directly instead of relying on the key binding of "1": folder-hook . 'push jump1enter' or just as David DeSimone suggested: folder-hook . 'push first-entry' -- Byrial
Re: Trouble getting indicator to point to first message
On Mon, Mar 20, 2000 at 15:39:20 -0500, David T-G wrote: Do I incorrectly remember a point_new variable that would cause mutt to jump to the first new message, which is what most people want anyway but some don't, which is now obviously not there? Or did I make it up? :-) I'm not sure, but I think that there once was such a variable which was considered superfluous and removed. -- Byrial
