Re: Creating Aliases from sent messages?
On 10/07/02 08:40 -0400, darren chamberlain wrote: Change the last line (the print line) to read: print map alias $_\n, sort keys %addrs; Which will give you a list like: alias [EMAIL PROTECTED] alias [EMAIL PROTECTED] Many thanks! John
Re: Creating Aliases from sent messages?
On 10/01/02 14:39 -0400, darren chamberlain wrote:
* Michael Tatge [EMAIL PROTECTED] [2002-10-01 14:17]:
Why don't you run a little shell or perl script against that folder?
Hmm...
#!/usr/bin/perl
use strict;
use File::Slurp;
use Email::Find;
my (%addrs, $data, $mbox, $finder);
$data = read_file(mutt-users); # read_file comes from File::Slurp
$mbox = $ENV{HOME}/Mail/lists/mutt-users;
$finder = Email::Find-new(sub { $addrs{ $_[0]-format }++ });
$finder-find(\$data);
print join \n, sort keys %addrs;
This works, assuming you have File::Slurp and Email::Find installed.
The problem with this, though, is that it picks up Message-ID's.
This worked just as promised! Cleaning out the Message-IDs was no big
deal. Thanks a million Darren! Forgive my delay in responding, but I
just found time to do this today. Also, File::Slurp and Email::Find had
to be installed.
I piped the output to a file. The only thing I had to then do was to
prepend the word 'alias' and a dummy alias (I used numbers) before each
address, so as to make the list work with mutt. (I did this via a
spreadsheet) I am a COMPLETE Perl novice, so please forgive this
question, but how could the script be modified to automate this
prepending?
John
Creating Aliases from sent messages?
I've searched the manual high and low on this and come up blank. I want to create a file of aliases based upon messages I've sent, rather than receive. They are all in one folder for ease of access. While creating an alias from a received message is a snap, it appears that, short of typing in long hand, there's no quick way to do this. Perhaps there's a macro around that will do this? TIA. John
Re: A question on forwarding
On 09/05/02 18:41 -0700, Gary Johnson wrote:
To forward messages that way, you need to go to the attachment menu
('v'), tag all the attachments ('t'), then forward them all using ';f'.
Doesn't esc e simply do what is wanted? I tried it with an excel
spreadsheet and it seems to work just fine.
John
Re: a number of newbie questions
On 08/29/02 12:16 -0400, darren chamberlain wrote: 3) [this is a vim question; don't shoot me :)] I've seen mutts start up vim as their editor like vim -c ':0;/^$' which I understand puts the cursor on the first empty line. Any way to place it at the end of the file (eg, last line)? set editor=vim +$ works for me, although that feels not right. I start vim thusly: set editor =vim +/^$ +'set nobackup' -c 'normal o' -c startinsert This puts me at a new line below the first non blank line, in insert mode. If you like, simply change 'normal o' to 'normal i' to omit the additional blank line. I use the blank line to make it easier when I need to reformat the first paragraph. That way, the headers don't get mangled when I execute gqip. The use of 'set nobackup' above is obvious. Also, while we're talking editors, I use: set tmpdir=~/tmp to ensure privacy of my temp files. Otherwise, they get written to /tmp, which is world readable. And,welcome to Mutt, krjw :) John
Re: Pipe:ing messages - behavior changed?
On 07/30/02 20:52 +0200, Peter Schuller wrote: Since upgrading mutt to the latest version the | command seems to only pipe what's on screen, not the entire raw message. As your headers indicate you're using 1.4, as I am, I tried what you described and my install works fine. I piped to lpr and to less using: |lpr, etc. How did you build it? If you used an rpm, what source?
Re: Numeric Keypad Malfunction -- Mutt, Vim, Gnome-Terminal
On 07/26/02 16:41 -0400, John P Verel wrote: Upon further investigation, I find that the keypad works fine under vim, run in an xterm and in rxvt. So, the culprit, I suppose, is gnome-terminal. I'll head on over the the RedHat Limbo beta list and see if I can learn anything there. I've learned that this numpad/vim issue is a well know bug with the current gnome-terminal. I've also learned that the Redhat Limbo Beta version of gnome-terminal is 100% re-written and that it is working correctly. FWIW. John
Re: Numeric Keypad Malfunction -- Mutt, Vim, Gnome-Terminal
Upon further investigation, I find that the keypad works fine under vim, run in an xterm and in rxvt. So, the culprit, I suppose, is gnome-terminal. I'll head on over the the RedHat Limbo beta list and see if I can learn anything there. John
Numeric Keypad Malfunction -- Mutt, Vim, Gnome-Terminal
I cannot get my numeric keypad to work with Mutt. Here's my environment: I run Mutt 1.4-2 in gnome terminal, provided by gnome-core-1.4.0.4-54. My editor is vim 6.1-2. I start vim with this command: set editor =vim +/^$ +'set nobackup' The numeric keypad works correctly within gnome-terminal (e.g. writing code), works fine within mutt, if run from xterm or rxvt. However, if I edit with vim, within mutt, run in a gnome-terminal, the numeric keypad does not work correctly. For example, I press the number 1 on the keypad, I get the letter q inserted above the current line. I tried tracking a thread in the archives on this topic, but it was beyond my ability to follow. However, I can report the my $TERM is set to xterm. mutt -v produces the following: Mutt 1.4i (2002-05-29) Copyright (C) 1996-2001 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: Linux 2.4.18-5 (i686) [using slang 10405] Compile options: -DOMAIN -DEBUG -HOMESPOOL -USE_SETGID -USE_DOTLOCK -DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP +USE_GSS +USE_SSL +USE_SASL +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR -HAVE_START_COLOR -HAVE_TYPEAHEAD -HAVE_BKGDSET -HAVE_CURS_SET -HAVE_META -HAVE_RESIZETERM +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET ++HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=/usr/bin/ispell SENDMAIL=/usr/sbin/sendmail MAILPATH=/var/mail PKGDATADIR=/usr/share/mutt SYSCONFDIR=/etc EXECSHELL=/bin/sh -MIXMASTER To contact the developers, please mail to [EMAIL PROTECTED]. To report a bug, please use the flea(1) utility. It is the stock compilation provided by Red Hat with release 7.3. Any help much appreciated. I want to stay with gnome-terminal because of the way it handles urls. TIA John
X-Mailer Header Not Being Picked Up With Resend Command
When I resend a message, using esc e, I find that my X-Mailer header is not picked up from the original message. The manual indicates that weeding is used when resending. My .muttrc contains: ignore unignorefrom: subject to cc mail-followup-to \ date x-mailer x-url weed in not set, so should default to yes, per the manual. What obvious thing am I missing? TIA John
Re: how does simple commenting work
Under :help comments there is this:
'comments' 'com'string (default s1:/*,mb:*,ex:*/,://,b:#,:%,:XCOMM,n:,fb:-)
local to buffer
{not in Vi}
{not available when compiled without the
|+comments|
feature}
A comma separated list of strings that can start a comment line.
See |format-comments|. See |option-backslash| about using
backslashes to insert a space.
If you have access to Steve Oualline's Book in Vim, he goes through
examples of using the comments option to define what is a comment. He
gives an example:
s1:/*,mb:*,ex:*/
and says of it:
The s1 command indicates that this is the start of a three-part comment
(s) and the other lines in the command need to be indented an extra
space (1). The comment starts with the string /*.
The middle of the comment is defined by the mb:* part. The m indicates
a middle piece, and the b says that a blank must follow anything that is
inserted. The text that begins the comment is *.
The ending is specified by ex:*/. The e indicates the end, and the x
indicates that you have only to type the last character of the ending to
finish the comment. The end delimiter is */. (Oualline, page 271).
I have not worked with this feature, but hope this reference is helpful.
John
On 07/24/02 16:23 +0200, Erika Pacholleck wrote:
Now I spent a whole day in searching all my .vim files,
reading all through the :help stuff and used my mailarchive
to get a clue - either I am missing simply a part of the
whole puzzle or I am just too insert whatever to understand.
Supposed I have a text which may begin with [ \t]+
blahblah
blahblah
and I need to define a special comment marker like note1
blahblah
note1 no blahblah
note1 use blub instead
blahblah
and further I want this comment marker to be auto-inserted
whenever I do enter, what parts would I need for this?
The whole stuff works with mail just on its own, but I cannot
find out what it is that makes it work. I have not auto-
insert and gq also does not work like it should.
Any help appreciated.
--
Erika Pacholleck [EMAIL PROTECTED]
mutters: insert vowels of last name
Re: X-Mailer Header Not Being Picked Up With Resend Command
On 07/24/02 21:12 +0200, Sven Guckes wrote: resending takes the message as is. no hooks or whatever get applied. feature. period. Not to be difficult, but to quote the on-line manual: 'With resend-message, mutt takes the current message as a template for a new message. This function is best described as recall from arbitrary folders. It can conveniently be used to forward MIME messages while preserving the original mail structure. Note that the amount of headers included here depends on the value of the ``$weed'' variable.' What does the last sentence mean? As the original message had an X-Mailer header included, I took the manual to mean that it would be picked up in the new message. John
Re: X-Mailer Header Not Being Picked Up With Resend Command
On 07/24/02 22:11 +0200, Michael Tatge wrote: To summarize: Mutt will delete any X-Mailer header. Confirmed. Thanks.
Re: Viewing both text and image
This also works, using ee as the client to view graphic images: Mailcap entries image/gif; ~/bin/spawn ee %s image/jpg; ~/bin/spawn ee %s image/jpeg; ~/bin/spawn ee %s ~/bin/spawn is the following script: #!/bin/sh cp $2 $2.tmp ($1 $2.tmp;rm -f $2.tmp) John On 07/15/02 14:25 -0700, Gary Johnson wrote: On Mon, Jul 15, 2002 at 01:41:57PM -0700, Jim Osborn wrote: I'm on a list where most of the traffic consists of a paragraph or two of text and an accompanying chart as an image attachment. I really need to be able to see the image as I read the text, and it'd be nice to be able to do that within Mutt. I haven't figured out how to get the image to xv without going into the ``v'' attachment menu, which hides the text part of the mail.
Re: Display in 'To:' in 'sent' folder only...
On 07/15/02 14:55 -0600, Dhruva B. Reddy wrote: I use mutt 1.3.28 (the Debian package). When viewing the list of messages in my 'sent' mailbox (where I copy my sent messages), it displays the 'From:' line. This is not very useful, since I already know that all messages in this mailbox are from me. This has been happening ever since I switch from mutt 1.3.20. Is there a way that I can get it to revert to the previous behavior? I couldn't find anything in the manual about this, specifically. I do what you're seeking with a folder hook. My ~/.muttrc includes: folder-hook outbox 'set index_format=%4C %Z %d %-20.20t (%3l) %s' which produces: 575 07/07/02 14:54 -0400 To Joe Foo( 11) New Red Hat Beta Announcement See the manual for index_format to suit your needs. John
Re: odd behavior -- collapse-all, sorting by thread
On 07/12/02 22:53 -0500, Derrick 'dman' Hudson wrote: I notice some really odd behavior in mutt. I have it set up with some folder-hooks to sort by threads in all my mailing list folders. This works fine, _except_ for one particular list *iff* I don't have the line folder-hook lists.* collapse-all # collapse all threads in my .muttrc. (remove that line, and the spamassassin list is not threaded, put it in and it is). What can I look for to determine why all but the one list are properly threaded without that line? I've found that folder hooks are sensitive to the order they are executed. I'm not quite certain if this addresses your question, but here's what I've got in my ~/.muttrc: folder-hook =mbox 'push odendl~Nenter' folder-hook =outbox 'push odend' folder-hook =Search 'push odend' folder-hook outbox 'set index_format=%4C %Z %d %-20.20t (%3l) %s' folder-hook Search 'set index_format=%4C %Z %D %-20.20t %-20.20f (%3l) %s' folder-hook Search 'push odend' folder-hook =CGO_Chorus 'push odend' folder-hook =My_Posts 'push odend' folder-hook =My_Replies 'push odend' set sort=threads set sort_aux=subject folder-hook . 'push otescVhome' # NOTE: Need to set specific mailbox hook BEFORE setting default. See my note to myself above. I found that I needed to set all the folders where I wanted the non default behavior, e.g. folder-hook . BEFORE the default is set. Otherwise, it didn't work. HTH. John
Problem piping *.doc attachment to AbiWord.
I have antiword set up as my mailcap entry for viewing MSWord docs and it works great (thanks Sven :). What I'd also like to do, from time to time, is pipe a *.doc to AbiWord. From the attachment menu, I've tried: | AbiWord and | AbiWord %s and | AbiWord %s Version one opens AbiWord without the file. Versions two and three open AbiWord with an error message saying, unable to open file %s. I've used AbiWord successfully in my mailcap file, using the %s temporary file descriptor, FWIW. I've looked at pipe_split, pipe_decode and pipe_sep, but none of them seem on point for what I'm trying to do. AbiWord documentation sheds no light on this, that I could find. Surely this is a brain cramp on my part, but any help appreciated. Thanks. John
Re: Problem piping *.doc attachment to AbiWord.
On 07/10/02 10:51 -0400, Mark J. Reed wrote: Like you, I have antiword set up for everyday .doc reading, and fire up AbiWord when antiword isn't enough. But I just save the attachment and then run abiword on it: s filename !abiword filename Yep, that works fine. Just looking for a shortcut. I suppose one could construct a macro to do the above, right? John
Re: Problem piping *.doc attachment to AbiWord.
On 07/10/02 11:37 -0400, Mark J. Reed wrote: macro attach a s/tmp/foo.doc\r!abiwordSpace/tmp/foo.doc\r Almost. I got this to work: macro attach a save-entry\cubol~/tmp/foo.doc\n!AbiWord ~/tmp/foo.doc\n Without ^U, the original name of the attachment was being appended to foo.doc. The bol is just insurance. Also, AbiWord is case sensitive. Your macro has \r in two places. What the intent there? Time for lunch. After lunch, I'll amend the macro to delete the temp file. Regards, John
Re: Problem piping *.doc attachment to AbiWord: Deleting the temp file
On 07/10/02 12:23 -0400, John P Verel wrote: Time for lunch. After lunch, I'll amend the macro to delete the temp file. This seems trivial, but I can't get the macro to do this. If I do rm -f foo.doc, I get dumped into my editor. I also can't figure out how to a) have AbiWord execute and then b) execute the rm after AbiWord exits. John
Re: Problem piping *.doc attachment to AbiWord: Deleting the temp file
On 07/10/02 14:52 -0400, Mark J. Reed wrote: Mutt should hang around and do nothing until AbiWord exits, so you should be able to just append a !rm -f ~/tmp/foo.doc\n to your macro. . . Arrrggh! Forgot the ! Finished product looks like this and works just fine. macro attach a save-entry\cubol~/tmp/foo.doc\n;!AbiWord ~/tmp/foo.doc\n;!rm -f ~/tmp/foo.doc\n John
Re: wrapping lines ?
On 07/10/02 11:56 -0800, W. D. McKinney wrote: Hello, Being a new mutt user, I need some help. I am trying to get mutt-1.3.27i-66 to wrap lines auto-magically. Be sure you've got your editor set up correctly. I use vim as my editor. In my .vimrc, I've got textwidth=72, which makes all come out right for my sent mail. Inbound may or may not be satisfactory, depending on the mailer used to create the mail. Outlook Express, for example, does a particularly awful job of not wrapping text. John
Re: how to filter in procmail
On 06/23/02 12:16 -0700, Will Yardley wrote: John Smith wrote: Well, i just subscribed to this list, and I'm wondering how do I filter this into a separate mailbox with procmail? All the other mailing lists I'm subscribed to are using X-Mailing-List in the headers. I examined the headers coming in here, and I can't find something that would help me :-) how about: * ^Return-Path: mutt-users-owner or: * ^Sender: owner-mutt-users I use: * ^TO_mutt Mutt n.b. man procmail for the syntax of ^TO_ John
Re: viewing urls (was: Re: mutt is awesome)
On 06/22/02, 12:53:13PM +0200, Raoul Bönisch wrote: On Fri, Jun 21, 2002 at 10:51:28PM -0600, Dave Price wrote: What I have not figured out is how to be able to click on a url in mutt and launch a browser window; can this be done? Righ now i paster the url into my browser 'by hand' You can use urlview for this. Press Ctrl-B in the pager to make urlview list all the urls in the mail shown. Then select a url and press return. Also, if you're running mutt from a gnome terminal emulator (gnome-terminal), taking the cursor over a url will highlight the url and change the cursor. Right click for a context sensitive menu, which includes launching in browser. Alternatively, press and hold control then left click for the same thing. John
Re: viewing urls (was: Re: mutt is awesome)
On 06/22/02, 11:55:18AM -0400, Ollie Acheson wrote: One question: where do I set which browser is picked? My installation seems to like mozilla, but I would prefer opera. Programs|Settings|Document Handlers|Url Handlers I'm using Galeon. It is MUCH lighter and faster than Netscape or Opera on my P733/256Meg machine. John
Re: Outlook warning bar
Probably the X-Sven header. ;-) ROFLMAO! :))
How to show custom macro bindings in help screen?
I've added a macro to my compose menu. It does not show up when I type '?' Should it? Am I missing something quite obvious? TIA. John
AbiWord in Mailcap works well :)
Just to pass this on -- I find that abiword-0.99.5-1 works wonderfully well in ~/.mailcap to open msword documents. The entry, trivially simple, is: application/msword; /usr/bin/AbiWord %s John
Re: How to show custom macro bindings in help screen?
On 06/18/02, 07:22:12PM +0200, Sven Guckes wrote: * John P Verel [EMAIL PROTECTED] [2002-06-18 16:31]: I've added a macro to my compose menu. It does not show up when I type '?' Should it? Am I missing something quite obvious? how did you add these macros? To my embarrassment, the macro in question IS present on the help screen. I have it bound to \cr The help screen shows it as bound to upper case r, e.g. ^R. I guess I'd forgotten that macros are case insensitive (correct?) and was looking for ^r. Sorry. Brain cramp :( John
Re: AbiWord in Mailcap works well :)
On 06/18/02, 07:28:41PM +0200, Sven Guckes wrote: application/msword; antiword %s ; copiousoutput Works pretty swift :). Have you figured out a way to print from antiword? I've tried lpr, enscript, a2ps, etc. Nothing works so far. Suggestions? John
Re: AbiWord in Mailcap works well :)
On 06/18/02, 02:10:06PM -0400, Mark J. Reed wrote: Also, you might want to upgrade; AbiWord 1.0.2 is out, and I find it successfully opens many Word documents that 0.99.x could not. Just gave 1.0.2 a go, via the rpms from the AbiWord home page. RPM reported that they were older than 0.99 (???), so I erased 0.99 and installed the base package, clipart and fonts. Got big time segfault, complaints about fonts, etc. So, erased and went back to 0.99. John
1.4: Better at setting 'N' flag than was 1.2.5 :)
Another observation. 1.4 seems to do a MUCH better job of check mail folders and setting new (N) flags than was 1.2.5. As I've got both installed on this machine, I'd doing some side by side comparisons. Seems to be a lot of nice fine tuning in 1.4.
Re: resent messages not saved?
Turns out this is a feature/bug that has been fixed in 1.4 John On 06/11/02, 11:49:46AM -0400, Adam Shostack wrote: It seems that messages re-sent (esc-e) are not being saved to my sent folder. In particular, I have a long message that I want to respond to in chunks; I used esc-e to re-send it, edit it up, and send it. When I go into ~/sent (where all my other saved mail is), there's no copy. Is this a (mis-)feature of resending messages? Is there a configuration option to control it? I've been quite paniced by this this morning. Adam
Re: How can I save the help screens?
On 06/10/02, 08:37:18AM -0400, Russell Hoover wrote: Is there an easy way to save mutt's help screens to a file, without doing a cut paste? Have a look at the manual, section 6.4, Functions. John
Making 1.4: Error messages
Made Mutt 1.4 today. I'm getting the following errors:
Error in /home/john/.muttrc, line 359: thread: unknown sorting method
This refers to a line which reads:
set sort=thread (Works fine in 1.2)
Second problem:
When I press F1, I get key not bound error.
Third thing:
In make intall log I get:
if test -f /home/john/mutt1.4/bin/mutt_dotlock test xmail != x ; then
\
chgrp mail /home/john/mutt1.4/bin/mutt_dotlock \
chmod 2755 /home/john/mutt1.4/bin/mutt_dotlock || \
{ echo Can't fix mutt_dotlock's permissions! 2 ; exit 1 ; }
\
fi
chgrp: changing group of `/home/john/mutt1.4/bin/mutt_dotlock':
Operation not permitted
Can't fix mutt_dotlock's permissions!
make[2]: *** [install-exec-local] Error 1
Is this important?
John
Re: Making 1.4: Error messages
On 06/10/02, 12:44:57PM -0500, David T-G wrote:
Don't know why it did, but it should be pluralized.
Pluralized it and it's fixed :)
% % Second problem: % % When I press F1, I get key not bound error.
Do you have the F1 binding in the system muttrc, or perhaps in yours?
It's in the system muttrc by default. What do you see when you hit ?
to look at your current bindings? Is it there at all?
The 1.2.5 version is in /etc, the 1.4 version is in the source for 1.4.
Where should the new one live?
% % Third thing: % % In make intall log I get: % % if test -f
/home/john/mutt1.4/bin/mutt_dotlock test xmail != x ; then % \ %
chgrp mail /home/john/mutt1.4/bin/mutt_dotlock \ % chmod
2755 /home/john/mutt1.4/bin/mutt_dotlock || \ % { echo Can't
fix mutt_dotlock's permissions! 2 ; exit 1 ; } % \ % fi % chgrp:
changing group of `/home/john/mutt1.4/bin/mutt_dotlock': % Operation
not permitted % Can't fix mutt_dotlock's permissions! % make[2]: ***
[install-exec-local] Error 1 % % Is this important?
It just means you're installing as you instead of root but that you
built mutt to expect to find a mutt_dotlock to do locking for it. If
you have an old mutt_dotlock on the system then I would say it's no
biggie EXCEPT that recently someone else posted that mutt compiles in
the location of mutt_dotlock instead of searching your path, so in the
worst case you might have to symlink your mutt_dotlock to the system
one with the proper perms. Only testing will tell if you really need
it. If your mail is not in /var/*/mail where only mail can create
files then you don't even need special perms (well, assuming that you
can always write in your own dirs, anyway).
My mail comes via fetchmail from my ISP's POP server.
If I look at the configuration options for 1.2.5, I see -USE_DOTLOCK.
These settings came via the rpm from Red Hat. 1.4 shows +USE_SETGID and
+USE_DOTLOCK, plus +DL_STANDALONE. Could these setting be sources of
the problem?
Re: Making 1.4: Error messages
On 06/10/02, 02:25:28PM -0400, John P Verel wrote: The 1.2.5 version is in /etc, the 1.4 version is in the source for 1.4. Where should the new one live? Fixed it. Mutt set up SYSCONFDIR as /home/john/mutt1.4/etc However, it did not copy my Muttrc to it, nor change the path to the manual in the macro. I did and it's fixed.
Re: Making 1.4: Error messages
On 06/10/02, 01:46:21PM -0500, David T-G wrote: % My mail comes via fetchmail from my ISP's POP server. I imagine it goes into your home dir somewhere, then, but it could go into the system mail spool. What does :set ?spoolfile in mutt tell you? Says unknow option -- which seems consistent with configuration option -HOMESPOOL. FWIW, this is a stand alone machine, hooked to a cable mode, poping mail using fetchmail. % % If I look at the configuration options for 1.2.5, I see -USE_DOTLOCK. % These settings came via the rpm from Red Hat. 1.4 shows +USE_SETGID and % +USE_DOTLOCK, plus +DL_STANDALONE. Could these setting be sources of % the problem? Well, it's just a difference rather than a problem. If you turned off USE_DOTLOCK you wouldn't have to worry about installing the dotlock program but you'd then have to be sure that other locking worked. Doesn't procmail (used here) take care of locking? % Fixed it. Mutt set up SYSCONFDIR as /home/john/mutt1.4/etc However, it Right. % did not copy my Muttrc to it, nor change the path to the manual in % the F1 macro. Now *that* is interesting; I am almost certain it should have done the copy. You did finish up with a make install, right? Yep. John
Re: Making 1.4: Error messages
On 06/10/02, 03:27:18PM -0500, David T-G wrote: Then you must set spoolfile somewhere in your muttrc in order for mutt to be able to find ! when you start up, because -HOMESPOOL says that your mail is found under /var. That makes the unknown variable all that more peculiar. My ~/.muttrc says: set spoolfile='~/Mail/mbox' Well, we've figured out the answers to your original questions; we should probably let this thread die :-) Morte ! ;)
1.4 Snappier than 1.2.5?
This may just be me, but it seems to me that 1.4 is considerably snappier than 1.2.5 was. It's about 50K larger, and this is compiled on this particular machine, versus rpm installed. Does this make sense? Have others noticed this? John
Re: 1.4 Snappier than 1.2.5?
On 06/10/02, 05:39:00PM -0500, David T-G wrote: John -- ...and then John P Verel said... % % This may just be me, but it seems to me that 1.4 is considerably % snappier than 1.2.5 was. It's about 50K larger, and this is compiled % on this particular machine, versus rpm installed. Who knows; it might still stand some stripping and get even smaller :-) This puppy's already been stripped, per Sven. % % Does this make sense? Have others noticed this? I haven't noticed it specifically, but that's because I stuck with the 1.3 tree for quite a while; I haven't used 1.2.5 in a long time. I know that a lot of improvements have been made, so I'm not at all surprised. % % John Enjoy HAND :-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.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg!
OT: Making Mutt: log files
I'm getting set to do my first non-rpm install of mutt and therefore my first usage of make. Looking at Sven's Installation Examples, I see outputted logs showing the results of configure, make and make install. Am I correct to assuming that these are generated automatically? TIA John
Re: OT: Making Mutt: log files
On 06/09/02, 06:01:56PM +0200, Rocco Rutte wrote: Looking at Sven's Installation Examples, I see outputted logs showing the results of configure, make and make install. Am I correct to assuming that these are generated automatically? Yes and no. What do you mean with automatically? Those tools involved produce that output automatically, yes. But to use them within a homepage, you have to catch them by hand: ./configure ... ./logfile 21 will display nothing but store everything in a logfile (you should consult your shell's manpage and search for I/O redirection). So, would ./configure 21 | tee ./logfile_config (etc) capture the output and show it to me on standard output as well (using bash)? John
Re: OT: Making Mutt: log files
Again, as I'm new to make, with the mutt source, if I make and install and find I need or want to uninstall what I just made and installed, how do I do that? Thank you for your patience with these questions. John
How to save copy of resent message?
I note that if I resend a message from, say, my outbox by doing ESC e to open it, edit and send the new message, no copy of the newly edited and sent message is placed in my outbox. Is there a way to change this behavior? BTW, the resend-message function does not appear the manual for 1.2.5, but seems only to be documented in the help screen for the index. Should be in the manual, no? TIA. John
Re: Default folder for save attachements
A variation on the below, given to this list by Mikko Hanninen, 4/2/00: macro attach s save-entrybol/mnt/vfat/john/muttattachments/ John On 06/05/02, 11:13:56PM +0200, Nicolas Rachinsky wrote: * Oliver Fuchs [EMAIL PROTECTED] [2002-06-05 22:39 +0200]: can I define a default folder for saving attachments (something like /home/me/download) in the .muttrc? macro attach s 'save-entrybol~/I/eol' 'save attachment' Nicolas
Re: to save tagged messages
On 05/29/02, 09:59:18AM -0500, Patrick wrote: * Bruno Caprile [EMAIL PROTECTED] [05-29-02 09:42]: The keystrokes would be: ;s[ ; = action to all tagged ] and [ s = save ] then enter the folder you wish to accept the tagged messages. NOTE: prepend = as a shortcut key for ~/home/Mail or ~/home/mail as you have set in .muttrc. Also, AFAIK, you'll need to create the folder outside of Mutt before saving to it. Just do: $ touch ~/Mail/foo then as Patrick wrote above. -- John P. Verel Living Proof That Low Tech Beats High Tech!
Re: to save tagged messages
Yet another cool mutt feature (is there no end ;). I'd missed this one. Thanks, David :) On 05/29/02, 03:28:02PM -0500, David T-G wrote: ...and then John P Verel said... % Also, AFAIK, you'll need to create the folder outside of Mutt before % saving to it. Just do: $ touch ~/Mail/foo then as Patrick wrote above. Nope. From TFM: 6.3.27. confirmcreate Type: boolean Default: yes When set, Mutt will prompt for confirmation when saving messages to a mailbox which does not yet exist before creating it. This, in conjunction with $mbox_type, let you create new folders just as you like without any extra work. -- John P. Verel Living Proof That Low Tech Beats High Tech!
Re: to save tagged messages
On 05/29/02, 04:51:12PM -0500, David T-G wrote: John -- So when are you going to bump to 1.4? :-) Well, I'm a Venerable RPM sissy ;). I'm supposing it won't be long 'till that day for 1.4 ... unless there's a site with one already built? -- John P. Verel Living Proof That Low Tech Beats High Tech!
Re: to save tagged messages
On 05/29/02, 05:11:53PM -0500, David T-G wrote: Fergit RPMs (though our RPM team is starting to build them now) and just build your own from source like a real man. Heck, surf over to http://mutt.justpickone.org/mutt-build-cocktail/ and see how a *real* mess of a mutt is made :-) Seriously, though, building the source from scratch is pretty simple if you keep it stock. Well, I'll have a look ... notwithstanding that this may compromise my signature, of course ;) -- John P. Verel Living Proof That Low Tech Beats High Tech!
Re: alphabetically listing
On 05/22/02, 09:22:47AM -0500, [EMAIL PROTECTED] wrote: Hello, I would like the directory/mailbox listings to be in alphabetical order. Is this possible? For example when I open a mailbox and choose (? for list). I'm not sure how it is sorted now. Kurt It looks to me that you've got your mail folders nested within subdirectories of your ~/Mail directory. There may be a reason for this, but it seems unnecessarily complicated. If, instead, your mail is kept in files directly under your ~/Mail directory, mutt will, by default, list them in alpha order. You could set up these files using procmail or, if you're doing all this manually (my guess), simply execute: touch ~/Mail/foo to create the folder. Then, save mail to the new folder(s) as usual. John -- Mutt: Directory [~/.Maildir], File mask: .* drwx-- 5 kvh users 120 Oct 20 06:33 lfs/ drwx-- 5 kvh users 120 Oct 20 06:33 jobs/ drwx-- 5 kvh users 120 Oct 20 06:33 save/ drwx-- 5 kvh users 120 Oct 20 06:33 urls/ drwx-- 5 kvh users 120 Oct 20 06:33 accounts/ drwx-- 5 kvh users 120 Oct 20 06:33 tvguide/ drwx-- 5 kvh users 120 Oct 20 06:33 postponed/ drwx-- 5 kvh users 120 Oct 20 06:33 receipts/ -- John P. Verel Living Proof That Low Tech Beats High Tech!
Re: Still fighting to get clickable URLs via w3m
On 05/13/02, 01:33:16PM +0200, Marco Fioretti wrote: Hello, I haven't been able yet to use w3m (or any other text browser for that matter) work cleanly as a Mutt pager. I want to read HTML email as text Marco, This works for me: I do my terminal work in a gnome terminal. This has the advantage of recognizing urls triggered by mouse over. To launch a browser, either right click for the context sensitive menu or hold alt and left click. My ~/.mailcap entry for w3m looks like this: text/html; w3m -T text/html -dump %s; copiousoutput; print= w3m -T text/html -dump %s | a2ps -c --borders=no --margin=36 --center-title= Note that this also allows me to print via a2ps, if desired. HTH. John -- John P. Verel Living Proof That Low Tech Beats High Tech!
Re: Re: Outlook pst import: What about awk?
Michael,
BRAVO! Worked like a charm! Thank you very much!
This is clearly one for the mutt archives. Congratulations to you.
John
On 04/17/02, 04:59:46PM +0200, Michal 'hramrach' Suchanek wrote:
Yes, the files are identical, you do not need to attach the same thing
twice ;-)
The difference is that while the email contained spaces after the From:
the mailbox contains a tab. There are two lines in the script containing
regexp which identify the From and Sent headers. The From: did not
match From:\t and the from header was not identified. Try changing the
lines like this in the script(only regexps inside quotes changed):
{ if ($0 ~ ^From:\t) {
# ^ here \t stands for tab
# space in original script does not match the tabs found in mailbox
...
if ($0 ~ ^Sent:\t) {
# you may append \t here as well ^
well I finally decided to attach the whole hack again
--
Michal Suchanek
[EMAIL PROTECTED]
{ if ($0 ~ ^From:\t) {
# a From: line is eaten
from=$0
start=1
}else{
#not From:
if (start) {
#but after From:
start=0
if ($0 ~ ^Sent:\t) {
# Sent: after From:
mail=from;
sub(^.*\\[,,mail);
sub(\\].*$,,mail);
wday=substr($2,1,3);
mon=substr($3,1,3);
mday=substr($4,1,2);
year=$5
hour=substr($6,1,2);
min=substr($6,4,4);
if ($7==PM) hour+=12;
date= wday mon mday hour : min year
print From mail date
print Date: date
}
#doesnt look like a header
# just print the eaten line
print from
}
# not even after From:
# nothing special
print $0
}
}
--
John P. Verel
Living Proof That Low Tech Beats High Tech!
Re: Re: Outlook pst import: What file format should I use?: Formail problem
On 04/15/02, 06:33:32PM +1200, Volker Kuhlmann wrote: Snip out any two consecutive messages from the file and attach them to a reply to the list. I'm sure someone can come up with a quick hack that will [re?]build ^From_ lines for you. Yes, that hack is very simple: man formail man procmail Splitting up a single file which contains concatenated emails with no From_ line at all could be more of a problem. Try some formail options, if none help, use a short script (or your editor) and replace each From: with a From\nFrom: , then run formail. Volker When doing the above, formail generates but one ^From_ entry, From_ foo@bar. I have done the following: Using sed, changed the address format from [[EMAIL PROTECTED]] (which is the way Outlook left it) to [EMAIL PROTECTED]. I run the output of this though formail and, no matter what options I try, it will only generate a From_ entry for the first mail message. The rest of the messages are unaffected. man formail recommends formail -ds old_mailbox new_mailbox. This does not work. Any suggestions -- John P. Verel Living Proof That Low Tech Beats High Tech!
Re: Re: Outlook pst import: What about awk?
Michael,
Thank you very much for your response and awk script. Much obliged.
I am a complete newbie to awk (although I do have the Dougherty and
Robbins text on sed and awk on hand).
When I execute awk with the script as you instruct, it creates an output
file that is unchanged from the input file. I used the fully qualified
path for the awk command, awkscript.awk, input and output files.
However, I'm unable to get it to work.
I'm running gnu awk 3.1.0, Red Hat 7.2. awk on my machine is a symbolic
link to gawk.
John
On 04/16/02, 05:26:44PM +0200, Michal 'hramrach' Suchanek wrote:
On Sun, Apr 14, 2002 at 11:53:57AM -0400, John P Verel wrote:
David,
As suggested, here's the first two messages from the file. The messages
bodies, which were just plain text, are omitted for confidentiality:
From: Robert F. Hugi [[EMAIL PROTECTED]]
Sent: Tuesday, November 02, 1999 11:20 AM
To: Verel,John(NXI); [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject:[Deleted]
Message here, deleted
From: Davis, Christopher [[EMAIL PROTECTED]]
Sent: Wednesday, November 03, 1999 9:21 PM
To: Heyen,Keith A.(NXI); Verel,John(NXI)
Cc: Goldstein,Irving V.; Chazaud, Diana; Taylor, Gabriella
Subject: [Deleted]
Message here, deleted
I made mutt read this mail as three-mail folder with awk:
$ awk -f awkscript.awk pst2 output
where pst2 is folder where I saved only the original (unquoted) mail and
output is the rusulting folder. awkscript.awk is attached
--
Michal Suchanek
[EMAIL PROTECTED]
{ if ($0 ~ ^From: ) {
# a From: line is eaten
from=$0
start=1
}else{
#not From:
if (start) {
#but after From:
start=0
if ($0 ~ ^Sent:) {
# Sent: after From:
mail=from;
sub(^.*\\[,,mail);
sub(\\].*$,,mail);
wday=substr($2,1,3);
mon=substr($3,1,3);
mday=substr($4,1,2);
year=$5
hour=substr($6,1,2);
min=substr($6,4,4);
if ($7==PM) hour+=12;
date= wday mon mday hour : min year
print From mail date
print Date: date
}
#doesnt look like a header
# just print the eaten line
print from
}
# not even after From:
# nothing special
print $0
}
}
--
John P. Verel
Living Proof That Low Tech Beats High Tech!
Re: Re: Outlook pst import: What file format should I use?: Formail problem
David, On 04/13/02, 10:41:27PM -0500, David T-G wrote: Snip out any two consecutive messages from the file and attach them to a reply to the list. I'm sure someone can come up with a quick hack that will [re?]build ^From_ lines for you. Don't try mucking with it in vim unless you only have two or three messages, in which case this should have been simple anyway. As suggested, here's the first two messages from the file. The messages bodies, which were just plain text, are omitted for confidentiality: From: Robert F. Hugi [[EMAIL PROTECTED]] Sent: Tuesday, November 02, 1999 11:20 AM To: Verel,John(NXI); [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject:[Deleted] Message here, deleted From: Davis, Christopher [[EMAIL PROTECTED]] Sent: Wednesday, November 03, 1999 9:21 PM To: Heyen,Keith A.(NXI); Verel,John(NXI) Cc: Goldstein,Irving V.; Chazaud, Diana; Taylor, Gabriella Subject: [Deleted] Message here, deleted Thank you, David, and all. John -- John P. Verel Living Proof That Low Tech Beats High Tech!
Re: Re: Outlook pst import: What file format should I use?: Formail problem
On 04/11/02, 12:36:45PM -0400, darren chamberlain wrote: * [EMAIL PROTECTED] [EMAIL PROTECTED] [2002-04-11 12:24]: These big text files open fine with vim. When I get home, I may have to fiddle with the From header to get things right. But, this may work. I'll report back. Try formail; I think it can add missing From lines. Using vim, I've gotten the From header to look like this: From Robert F. Jones [[EMAIL PROTECTED]] This, however, is not the standard mbox header, which, on my machine, looks like this: From [EMAIL PROTECTED] Fri Apr 7 18:38:07 2000 When then run the edited file through formail, it does not add the correct missing From line. Rather, it leaves the first instance of From as shown above unchanged and then escapes the remaining From lines with a I use the -b switch to stop this. However, in no case does Mutt recognize the box as a valid mbox. Any ideas? Thanks. John -- John P. Verel Living Proof That Low Tech Beats High Tech!
Re: Re: Outlook pst import: What file format should I use?
Try formail; I think it can add missing From lines. (darren) The Outlook file is formatted with the first line as, for example: From: John Q. Hacker If I execute formail -ds old_mailbox new_mailbox, as per man formail, the new_mailbox has a first line of: From John but stops there, not processing any other messages. As this is my first this is my first go with formail, I'm surely missing something. Any guidance will be appreciated. Thanks. -- John P. Verel Living Proof That Low Tech Beats High Tech!
How to convert Outlook *.pst files to mbox format?
This may be an FAQ, but I couldn't come up with it. I have substantial *.pst files from Microsoft Outlook from work which I want to convert to mbox format. Any pointers on this will be gratefully appreciated. -- John P. Verel Living Proof That Low Tech Beats High Tech!
Re: How to convert Outlook *.pst files to mbox format?
On 04/10/02, 04:02:02AM +0200, Gerhard Häring wrote: I've done that recently. I used Mozilla on Windows to import the PST files. Then hunted down where Mozilla actually has his files. c:/Documents and Settings//AppData/Mozilla or similar it was in my case. Mozilla saves its mails in a mbox format. However, in a peculiar one with Windows line endings, so you have to get rid of the CR for example using tr. Voila the converted mbox files. This may do the trick. I have no particular need to filter the messages. Rather, if I can simply make them available to browse in mutt, this will be fine. A good weekend project ahead of me. Thanks! -- John P. Verel Living Proof That Low Tech Beats High Tech!
Re: thread view
...and then Eduardo Gargiulo said... % How can i configure muttrc to collapse thread messages ? I use: folder-hook . 'push otescVhome Sets sort order to thread, collapses all, puts you at top of the list. John - John P. Verel Living Proof That Low Tech Beats High Tech!
Re: Index format
My experience with hooks is that if you have to set specific mailbox
hooks BEFORE setting a default. Try changing the order of the hooks
so that the default comes after all the others. My o/s and version are
as above.
John
On 02/06/02, 05:36:23PM +, Patrick Colbeck wrote:
Hi
Unfortunately I cannot get mutt to recognise the folder hook, no errors
are generated but there is no change in the index format. If I change
the global format even with a folder hook . then I do see a change.
I am using Mutt 1.3.22.1i on SuSE 7.2
Here is some of my muttrc (stolen from all over the net)
set folder=~/Mail
#folder-hook . 'set index_format=%4C %Z %{%b %d} %-15.15t (%4l) %s'
folder-hook . 'set index_format=%4C %Z %{%b %d} %-15.15t (%4l) %t'
either of the two above work and change the index in all mailboxes
folder-hook +Spool/mutt-users my_hdr From: [EMAIL PROTECTED]
folder-hook +Spool/mutt-users set signature=~/Signatures/bashq.sig
folder-hook +Spool/mutt-users 'fcc-hook .* +Outgoing/mutt-user
folder-hook +Outgoing/mutt-users 'set index_format=%4C %Z %{%b %d}
%-15.15t (%4l) %s'
The above doesnt work in that ~/Mail/Outgoing/mutt-users gets the same
index as whatever is set as the default for all folders.
Thanks
Pat
--
John P. Verel
Living Proof That Low Tech Beats High Tech!
Sorceforge bouncing mail: Create Postmaster Account ??
I have the impression that this is unsolvable. In any case, if I attempt to post to [EMAIL PROTECTED], I get this message: - The following addresses had permanent fatal errors - [EMAIL PROTECTED] (reason: 550-Envelope sender verification failed) - Transcript of session follows - ... while talking to mail.sourceforge.net.: DATA 550-Envelope sender verification failed 550 rejected: there is no valid sender in any header line (envelope sender is [EMAIL PROTECTED]). Your mail server returned: +Response from mx1.optonline.net [167.206.5.6] was 550 5.1.1 unknown or illegal alias: [EMAIL PROTECTED] when checking for existence+of a postmaster mailbox. RFC 822 section 6.3 (which you have to abide by if you send and receive Email) states that you are required to have+a postmaster mailbox that is routed to the person responsible for mail (http://www.rfc822.com/). We need to be able to contact you at the +postmaster address to resolve potential problems if need be before we can accept your mail. Please create a postmaster account at your site.554 5.0.0 Service unavailable My .muttrc includes: set envelope_from=yes set use_from=yes my_hdr From: John P Verel [EMAIL PROTECTED] The From above is my true address at optonline. I'm completely baffled on this one. -- John P. Verel Living Proof That Low Tech Beats High Tech!
Re: Pity that mutt doesn't read news - what's the best match?
On 02/01/02, 01:30:33AM +0800, Charles Jie wrote: I have been a netscape user. Now I'm satisfied with mutt and will not go back to netscape except one thing - reading news groups. Could any Mutter suggest a good news reader of mutt style? (Highly customizable) Slrn, as others have said. My model is Mutt/Slrn/Vim. Fabulous all around. The threading can not be beat, IMHO :) -- John P. Verel Living Proof That Low Tech Beats High Tech!
Re: how to keep threads collapsed, in a mailbox index, when mail arrives?
Have you tried setting uncollapse_jump to yes? Perhaps this will help? John On 01/19/02, 04:04:47PM -0500, parv wrote: in message 20020119061359.GA1695@knute, wrote Knute thusly... On Sat, 19 Jan 2002, parv wrote: ... say, i am looking at the mailbox index. all the threads are collapsed. as soon as new mail arrives, the thread receiving the new mail gets un-collapsed ... which is highly annoying. i am using mutt 1.3.25i on freebsd 4.5-prerelease. below is some of the muttrc, hopefully w/ least of the irrelevant portion... ... set collapse_unread=yes ... Change the above to : set collapse_unread=no According to the manual, that's the option that prevents mutt from collapsing threads with new mail in them. thanks, but i want the threads to remain collapsed whether they have new mail or just received new mail and thus get un-collapsed. w/ collapse_unread=no, i can't collapse threads at all. w/ collapse_unread=yes, i can at least collapse the threads after they had been un collapsed on receiving new mail. - parv -- -- John P. Verel Living Proof That Low Tech Beats High Tech!
Re: envelope ?
There is a From: field in the email message and there is a from field on the envelope wrapping the message. They are two different things. When mutt passes off the message to your Mail Transport Agent, e.g. Sendmail, Sendmail prepends certain information to it: specifically the from field, date and time, all on the first line. Sendmail may try to create this from field using, say, your login name and your machine name, based on /etc/hosts. Unfortunately, this may not be your address with your ISP. In some cases, this will cause you message to bounce. Sendmail has a -f switch, documented in the Mutt manual, which forces Sendmail to use your email From: address to be your envelope from. A side benefit is that you may get an additional header inserted by sendmail that looks like this: X-Authentication-warning: John.optonline.net: john set sender to [EMAIL PROTECTED] using -f This can be fixed by changing Sendmail configurations, but, hey life is too short already, no? So, mutt lets you fix this problem with the envelope_from setting. OT, this issue is encountered elsewhere, like, for instance, slrn, where I have to force the sendmail command to be able to forward mail from it. HTH John On 01/10/02, 09:07:55AM -0800, Todd Kokoszka wrote: What is the envelope_from setting and how is it different from the From: field? Does anyone know where I can learn how these function? -- John P. Verel Living Proof That Low Tech Beats High Tech!
Re: Please help verify my procmail settings to go with mutt
While I'm on RedHat, not Mandrake, my suspicion is that Mandrake may be set up so that you do not need a .forward file for postfix. Have you tried running without the .forward? John On 12/31/01, 07:05:28PM +0800, Charles Jie wrote: Hi, I'm trying to substitute Mutt with Mozilla. One important porting work is dealing with the multiple accounts I keep, especially the mailing list. * But I found the flow of incoming mail dropping down. vim mailing list sent me a message telling me my mail is bouncing. On 12/28 and 29, I received about 20 mails from mutt-users. But 12/30 I had no more than 5. It also happened to [EMAIL PROTECTED], dropping from 20-30 down to 4. (But my testing mail all survived.) (My MTA is postfix (on Mandrake 8.1). Mutt is 1.3.24i. procmail 3.21.) I wonder whether the following files (copied from 'man procmail') have anything wrong. Help, please. * My ~/.forward: |IFS=' 'p=/usr/bin/procmailtest -f $pexec $p -Yf-||exit 75 #jie (Could anybody help explain: 1. Why IFS=' ' checking? 2. Why the options -Yf- in exec $p -Yf-? 3. Why exit 75? ) * My ~/.procmailrc: MAILDIR=$HOME/Mail#you'd better make sure it exists #DEFAULT=$MAILDIR/mbox#completely optional LOGFILE=$MAILDIR/proc.log #recommended :0: * ^(To|CC|From): .*mutt-users mbox.mutt :0: * ^(To|CC|From): .*[EMAIL PROTECTED] mbox.vim :0: * ^Subject: .*Fwd?: mbox.fw :0 * ^Reply-To: [EMAIL PROTECTED] mbox.spam If I can not handle multiple accounts well with mutt, I may need to go back to Mozilla or Netscape, which are so heavy. Thank you in advance, charlie -- Charles Jie (¬ö¬K¿³) Keya Technologies (¶}¶®¬ì§Þ) (O) +886 2 2936 0813 (Mobile) 0920 397 746 -- John P. Verel Living Proof That Low Tech Beats High Tech!
Re: abort_nosubject=ask-no not working as expected
Thanks. That works. Nowif I could just figure out how to keep Mutt from putting double quotes around my name in the from line? John On 12/16/01, 11:23:41PM -0500, Ken Weingold wrote: On Sun, Dec 16, 2001, John P . Verel wrote: Does the abort_nosubject option work in 1.2.5? My .muttrc entry is: set abort_nosubject=ask-no Based on the manual, I'd have thought that when I press y to send a message with no subject, I would not be prompted to abort or send. Yet, I'm still asked. What am I missing? If you don't want to be asked, use: set abort_nosubject=no -Ken -- John P. Verel Living Proof That Low Tech Beats High Tech!
Getting rid of quotes in name (new thread;)
Yep, losing the period did it. Thanks, David John On 12/17/01, 09:13:56AM -0500, David T-G wrote: John -- ...and then John P . Verel said... % % Nowif I could just figure out how to keep Mutt from putting double % quotes around my name in the from line? You should have started a new thread ;-) I'm afraid you're stuck with 'em until you remove the period from your fullname. IIRC it's part of the RFC spec, but I at least know that it's come up on the list before. I expect someone can provide you a pointer to the authoritative reference, though :-) % % John HTH HAND :-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.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! -- John P. Verel Living Proof That Low Tech Beats High Tech!
Re: Mutt file browser question
I have the following in my .muttrc: folder-hook =mbox 'push odendl~Nenter What it does when I open my mbox, sorts the entries by date, goes to the last (bottom) one and then just shows new (unread) entries. Perhaps this will help you? John On 12/17/01, 07:13:08PM +0300, [EMAIL PROTECTED] wrote: I have all my mail sorted in a number of mailboxes and when I change from one to another (i.e. go to file browser and select needed mailbox) cursor is always at the top. Is it possible to make it stay on the last open file, not jump to the top? -- Oleg Kourapov | Linux user #245698 http://counter.li.org Moscow, RU| LFS user #1212 http://www.linuxfromscratch.org -- Yesterday is a memory. Tomorrow is the unknown. Now is the knowing. -- -BEGIN GEEK CODE BLOCK- Version: 3.12 GTW d- s+: a-- C UL++ P+ L+++ E--- W+++ N++ o-- K++ w-- O M- V- PS+ PE+++ Y+ PGP++ t 5++ X++ R tv- b+++ DI+ D G e* h! r y? --END GEEK CODE BLOCK-- -- John P. Verel Living Proof That Low Tech Beats High Tech!
How to eliminate vim temporary files?
While I'm sure this is an FAQ, I can't find it on Google, etc., but my apologies in advance if it is out there: I'm running Mutt 1.2.5i, using vim5.8 as editor. I want to have it so vim does not leave temporary files when exiting. My .muttrc editor line looks like this: set editor =vim +/^$ My .vimrc looks like this: set nocompatible set textwidth=72 set incsearch set nu set showmatch set nohlsearch set bs=2 set shm=atI set joinspaces set magic set title set backup set shiftwidth=3 :filetype on :autocmd FileType c,cpp,java :set cindent syntax on TIA John -- John P. Verel Living Proof That Low Tech Beats High Tech!
Re: How to eliminate vim temporary files?
Thanks. It works. I used a modification of what you suggested. Since I want vim to make backup files when, say, writing code, I've set my .muttrc editor line to: set editor =vim +/^$ +'set nobackup' The +/^$ opens the file at the first blank line. The tricky bit for me is that the set command needed the quotes around it to work. Otherwise it thought nobackup was a file name. man vim said double quotes, but the above seems to work fine. John On 12/16/01, 02:14:10PM -0800, Will Yardley wrote: John P. Verel wrote: I'm running Mutt 1.2.5i, using vim5.8 as editor. I want to have it so vim does not leave temporary files when exiting. remove 'set backup' from your .vimrc, and replace it with: set nobackup you want it to keep swap files (presumbably) - i forget what the option is for that, although it should be listed in your global vimrc and in the vimrc man page keeping swap files in the event of a crash is a different option than keeping a backup file for everything you edit. -- Experience -- a great teacher, but the tutition fees... -- John P. Verel Living Proof That Low Tech Beats High Tech!
abort_nosubject=ask-no not working as expected
Does the abort_nosubject option work in 1.2.5? My .muttrc entry is: set abort_nosubject=ask-no Based on the manual, I'd have thought that when I press y to send a message with no subject, I would not be prompted to abort or send. Yet, I'm still asked. What am I missing? TIA -- John P. Verel Living Proof That Low Tech Beats High Tech!
Re: Vim colors?
A good site for this is http://www.math.fu-berlin.de/~guckes/vim/ maintained by Sven Guckes. Lots of great stuff there! John On 11/16/01, 08:59:14PM -0700, Sean LeBlanc wrote: Thanks for all the help everyone has given so far. I finally downloaded and installed vim, and set it up as the editor. I've been looking around for color config info...anyone have a favorite site, or a configuration file to share? Thanks, -- - Sean LeBlanc, [EMAIL PROTECTED] End corporate welfare. Repeal the H1-B program now: http://www.zazona.com/ShameH1B/ Auctioning many Linux, Java, NT, SilverStream books: http://cgi6.ebay.com/aw-cgi/eBayISAPI.dll?MfcISAPICommand=ViewListedItemsuserid=tparkin IM me: Yahoo: seanleblancathome ICQ: 138565743 MSN: seanleblancathome AIM: sleblancathome -- John P. Verel Norwalk, Connecticut
Re: Wrapping Text
Sorry, I missed the printing part as well. Here's my printing configuration: set print_command=enscript --word-wrap --margins=::: -f 'Times-Roman11'-F 'TimesRoman14' --fancy-header='enscript' -i3 This solves all the word wrap problems and makes all printouts real purdy ;) John On 10/25/01, 08:45:37AM -0700, Michael Montagne wrote: Thanks, I tried that and it only controls the display. Printing is unaffected. On Wed, Oct 24, 2001 at 10:43:44PM -0400, John P. Verel wrote: You may want to have a look at smart_wrap, item 6.3.182 in the manual (F1). John On 10/24/01, 05:51:13PM -0700, Michael Montagne wrote: When viewing a mail message, how do I reset the width of my margins so it will print properly. I use vim to write mail and that is ok but the mutt viewer for mail i receive does not control the width. I know I'm missing something. thanks -mjm -- Michael Montagne [EMAIL PROTECTED] http://www.boora.com -- John P. Verel Norwalk, Connecticut -- Michael Montagne [EMAIL PROTECTED] http://www.boora.com -- John P. Verel Norwalk, Connecticut
Re: OT Procmail rule not working.
Here's my procmail recipe to filter mutt mailing list mail: :0 * ^TO_mutt Mutt That's all it takes. It ends up in a mailbox called Mutt. Questions: Does your $HOME/Mail directory exist? What's the PMDIR and INCLUDERC environmental variables for? I'm running procmail-3.21-0.71, and have either of them. John On 10/24/01, 12:26:38PM -0700, Carl B . Constantine wrote: I have a procmail rule to move list mail to a folder. But it's not working correctly according to my procmail logs. Here's the procmail script: PATH=/public/bin:/local/bin:/usr/bin:/bin SHELL=/public/bin/tcsh VERBOSE=on LOGABSTRACT=all MAILDIR=$HOME/Mail PMDIR=$HOME/Procmail LOGFILE=$PMDIR/log #INCLUDERC=$PMDIR/testing.rc INCLUDERC=$PMDIR/lists.rc ### # Mailing lists # ### #:0: #* X-Mailing-List: \/[^@]+ #lists/`echo $MATCH | sed -e 's/[\/]/_/g'` :0: * ^Sender: owner-\/[^@]+ lists/`echo $MATCH | sed -e 's/[\/]/_/g'` It's this last rule that doesn't work. Here's what it produced for a mail msg to this list: procmail: Assigning INCLUDERC=/home/cconstan/Procmail/lists.rc procmail: Assigning MATCH= procmail: Matched mutt-users procmail: Match on ^Sender: owner-\/[^@]+ procmail: Executing echo $MATCH | sed -e 's/[\/]/_/g' procmail: Locking lists/.lock procmail: Assigning LASTFOLDER=lists//msg.LoPC procmail: Opening lists//msg.LoPC procmail: Acquiring kernel-lock procmail: [15789] Wed Oct 24 11:49:59 2001 procmail: Unlocking lists/.lock From [EMAIL PROTECTED] Wed Oct 24 11:49:57 2001 Subject: Re: limit header size Folder: lists//msg.LoPC 2991 procmail: Notified comsat: cconstan@0:/home/cconstan/Mail/lists//msg.LoPC Notice it created a different message file instead of putting it in the proper file. A listing of ~/Mail/lists: (cconstan@viper): ~/Procmail% ls -l ~/Mail/lists total 9422 -rw--- 1 cconstan 5560 Oct 24 12:14 mutt-users -rw--- 1 cconstan 9387453 Oct 24 11:03 mutt-users.01Oct24 -rw--- 1 cconstan 232405 Oct 18 08:26 uvsubnet Anyone have ideas as to why this isn't working correctly? Thanks. -- Carl B. Constantine University of Victoria Programmer Analysthttp://www.uvic.ca UNIX System Administrator Victoria, BC, Canada [EMAIL PROTECTED] -- John P. Verel Norwalk, Connecticut
Re: Wrapping Text
You may want to have a look at smart_wrap, item 6.3.182 in the manual (F1). John On 10/24/01, 05:51:13PM -0700, Michael Montagne wrote: When viewing a mail message, how do I reset the width of my margins so it will print properly. I use vim to write mail and that is ok but the mutt viewer for mail i receive does not control the width. I know I'm missing something. thanks -mjm -- Michael Montagne [EMAIL PROTECTED] http://www.boora.com -- John P. Verel Norwalk, Connecticut
Re: Tag Multiple Attachments?
Sigh. Well, here's the answer, sports fans. Upon close inspection of my .muttrc, I noted that I'd changed my folder_format (manual reference 6.3.43) from the default setting to %N %8s %d %f: i.e, I'd eliminated the display of the tag flag, the *. So, tagging was working, but the * to show it was not. In my effort to streamline the file folder display, I outdid myself. Moral here? RTF.muttrc, John ;( Cheers John On 10/19/01, 12:10:13AM -0400, John P. Verel wrote: Well, I just tried something, with interesting result. I went to the attach menu and pressed t twice. No * showed up next to the files when I typed t. BUTwhen I went back to the compose menu, the tagged files showed up in the attachments section. So... the problem is that the * is not showing up in the attachment menu. I'll have a look at the menu in the morning to see about this. But if anyone has a suggestion on changing the way the attachment screen is laid out, I'd love to hear it! Thanks. John On 10/18/01, 08:31:43PM -0700, Shawn D. McPeek wrote: Perhaps your t is bound to something other than tag-entry. Perhaps you're hitting q instead of Enter after tagging. When you tag files, it should place a * next to the listed permissions. Does it at least do that? If not, your t is probably wrong. If so, then just hit enter after tagging everything and you should be good to go. Shawn Previously, John P. Verel wrote: % That's what I do. All that happens is the cursor moves to the next file % name. % % The manual notes that typing upper case A allows for tagging and % attaching multiple messages (not files) and that works for me. The % manual makes no mention of tagging files...only messages. % % So, no luck here so far. % On 10/17/01, 05:43:40PM -0700, Igor Pruchanskiy wrote: % On Wed 17 Oct 2001, John P. Verel wrote: % Hi. I sometimes want to attach multiple files from the same directory. % I've tried to tag while in the attachment menu, but no luck. Couldn't % find anything in the on-line help. The ? indicated t for tag in the % attachment menu. What am I missing. % % just hit t to tag an attachment, just like you tag messages -- John P. Verel Norwalk, Connecticut -- John P. Verel Norwalk, Connecticut
Re: Tag Multiple Attachments?
That's what I do. All that happens is the cursor moves to the next file name. The manual notes that typing upper case A allows for tagging and attaching multiple messages (not files) and that works for me. The manual makes no mention of tagging files...only messages. So, no luck here so far. On 10/17/01, 05:43:40PM -0700, Igor Pruchanskiy wrote: On Wed 17 Oct 2001, John P. Verel wrote: Hi. I sometimes want to attach multiple files from the same directory. I've tried to tag while in the attachment menu, but no luck. Couldn't find anything in the on-line help. The ? indicated t for tag in the attachment menu. What am I missing. just hit t to tag an attachment, just like you tag messages igor -- Uptime: 45 days, 17:57 -- John P. Verel Norwalk, Connecticut
Re: Tag Multiple Attachments?
Well, I just tried something, with interesting result. I went to the attach menu and pressed t twice. No * showed up next to the files when I typed t. BUTwhen I went back to the compose menu, the tagged files showed up in the attachments section. So... the problem is that the * is not showing up in the attachment menu. I'll have a look at the menu in the morning to see about this. But if anyone has a suggestion on changing the way the attachment screen is laid out, I'd love to hear it! Thanks. John On 10/18/01, 08:31:43PM -0700, Shawn D. McPeek wrote: Perhaps your t is bound to something other than tag-entry. Perhaps you're hitting q instead of Enter after tagging. When you tag files, it should place a * next to the listed permissions. Does it at least do that? If not, your t is probably wrong. If so, then just hit enter after tagging everything and you should be good to go. Shawn Previously, John P. Verel wrote: % That's what I do. All that happens is the cursor moves to the next file % name. % % The manual notes that typing upper case A allows for tagging and % attaching multiple messages (not files) and that works for me. The % manual makes no mention of tagging files...only messages. % % So, no luck here so far. % On 10/17/01, 05:43:40PM -0700, Igor Pruchanskiy wrote: % On Wed 17 Oct 2001, John P. Verel wrote: % Hi. I sometimes want to attach multiple files from the same directory. % I've tried to tag while in the attachment menu, but no luck. Couldn't % find anything in the on-line help. The ? indicated t for tag in the % attachment menu. What am I missing. % % just hit t to tag an attachment, just like you tag messages -- John P. Verel Norwalk, Connecticut
Re: How to un-attach?
Arrrgh. I hate it when that happens ;) To make matters worse, I actually did look at the ? at the send menue. Yep. Looked right at it and never saw it. Sigh. Thanks for the reply, and sorry for the wasted bandwidth, folks. John On 10/04/01, 10:05:58AM +0100, Lars Hecking wrote: Justin R. Miller writes: Thus spake John P. Verel ([EMAIL PROTECTED]): I sometimes accidentally attach the wrong file to a message. I can't figure out how to to un-attach it. Can anyone help on this? Try highlighting the attachment in the compose menu and hitting 'D' (however, not 'd', which changes the description of the attachment.) And it's even documented ;) Press ? in the send menu. D detach-filedelete the current entry -- John P. Verel Norwalk, Connecticut
How to un-attach?
Hi. I sometimes accidentally attach the wrong file to a message. I can't figure out how to to un-attach it. Can anyone help on this? Thanks. -- John P. Verel Norwalk, Connecticut
Re: Procmail/sed/New Mail flag problem solved, FYI (somewhat long) -- new recipe sucess
Aaron, and list: Aaron's suggested recipe works beautifully. In particular, it fixed the odd Assigning... log entry. Thanks! On 09/22/01, 10:56:45PM -0400, John P. Verel wrote: Aaron, Interesting. Your use of the only if the above succeeded is something I'd not thought of. If would fix a glitch I saw in the procmail log, which is this goofy looking entry: procmail: Assigning LASTFOLDER= sed -e '/Subject:/s/\[kde-linux\] //g' KDE-linux Presumably, the added recipe will cause LASTFOLDER to be set simply to KDE-linux, the desired outcome, otherwise to mbox, an okay fallback. I'll give this a go in the morning. Bit too late for tinkering with dot files, especially after some free beers :) Thanks for your note. On 09/22/01, 08:02:20PM -0500, Aaron Schrab wrote: At 14:09 -0400 22 Sep 2001, John P. Verel [EMAIL PROTECTED] wrote: :0 fw: * ^TO_kde-linux | sed -e '/Subject:/s/\[kde-linux\] //g' KDE-linux While this stripped off the string just fine, I was getting funny results. Specifically, my mbox N flag was getting falsely set. Examination of the procmail log showed why: What this log suggested to me was that using the f (consider the pipe a filter) and w (wait for the filter to finish and check its exit code) were not doing what I intended. Rather than simply allowing time for the sed edit to operate, procmail was sending the mail to the correct box, but was continuing to process succeeding recipes, ultimately setting the flag on mbox. I fixed this by removing the flags and the lock (:). New recipe looks like this :0 * ^TO_kde-linux | sed -e '/Subject:/s/\[kde-linux\] //g' KDE-linux Just removing the f flag would have fixed it. You should definitely keep the lock. I'd advise keeping the w flag as well, since it will allow procmail to attempt to deliver the message in some other way if the sed command fails for some reason. Personally, I prefer to let procmail do the writing to my mailboxes. It's likely to do a better job of recovering from errors than some random program acting as a filter. You could do this like: :0fw * ^TO_kde-linux | sed -e '/Subject:/s/\[kde-linux\] //g' # Only if the above succeeded :0a: KDE-linux In this case you want the f flag on the first recipe, but a lock is unnecessary (it's not dealing with any files). -- Aaron Schrab [EMAIL PROTECTED] http://www.execpc.com/~aarons/ At the source of every error which is blamed on the computer you will find at least two human errors, including the error of blaming it on the computer. -- John P. Verel Norwalk, Connecticut -- John P. Verel Norwalk, Connecticut
Procmail/sed/New Mail flag problem solved, FYI (somewhat long)
Here's a procmail problem I solved. Perhaps it may be of help to others. My objective is to strip the string [kde-linux] (no quotes) from the subject line of the mailing list of the same name. My first procmail recipe attempt looked like this: :0 fw: * ^TO_kde-linux | sed -e '/Subject:/s/\[kde-linux\] //g' KDE-linux While this stripped off the string just fine, I was getting funny results. Specifically, my mbox N flag was getting falsely set. Examination of the procmail log showed why: procmail: [1048] Sat Sep 22 10:27:13 2001 procmail: Assigning LOGABSTRACT=all procmail: No match on (^((Original-)?(Resent-)?(To|Cc|Bcc)|(X-Envelope|Apparently(-Resent)?)-To):(.*[^-a-zA-Z0-9_.])?)redhat-list procmail: No match on (^((Original-)?(Resent-)?(To|Cc|Bcc)|(X-Envelope|Apparently(-Resent)?)-To):(.*[^-a-zA-Z0-9_.])?)sparc-list procmail: No match on (^((Original-)?(Resent-)?(To|Cc|Bcc)|(X-Envelope|Apparently(-Resent)?)-To):(.*[^-a-zA-Z0-9_.])?)wine-users procmail: No match on (^((Original-)?(Resent-)?(To|Cc|Bcc)|(X-Envelope|Apparently(-Resent)?)-To):(.*[^-a-zA-Z0-9_.])?)mutt procmail: Match on (^((Original-)?(Resent-)?(To|Cc|Bcc)|(X-Envelope|Apparently(-Resent)?)-To):(.*[^-a-zA-Z0-9_.])?)kde-linux procmail: Locking KDE-linux.lock procmail: Executing sed -e '/Subject:/s/\[kde-linux\] //g' KDE-linux procmail: Unlocking KDE-linux.lock procmail: No match on (^((Original-)?(Resent-)?(To|Cc|Bcc)|(X-Envelope|Apparently(-Resent)?)-To):(.*[^-a-zA-Z0-9_.])?)kde-user procmail: No match on (^((Original-)?(Resent-)?(To|Cc|Bcc)|(X-Envelope|Apparently(-Resent)?)-To):(.*[^-a-zA-Z0-9_.])?)gnome-list procmail: No match on (^((Original-)?(Resent-)?(To|Cc|Bcc)|(X-Envelope|Apparently(-Resent)?)-To):(.*[^-a-zA-Z0-9_.])?)redhat-announce-list procmail: No match on (^((Original-)?(Resent-)?(To|Cc|Bcc)|(X-Envelope|Apparently(-Resent)?)-To):(.*[^-a-zA-Z0-9_.])?)redhat-watch-list procmail: No match on (^((Original-)?(Resent-)?(To|Cc|Bcc)|(X-Envelope|Apparently(-Resent)?)-To):(.*[^-a-zA-Z0-9_.])?)[EMAIL PROTECTED] procmail: No match on (^((Original-)?(Resent-)?(To|Cc|Bcc)|(X-Envelope|Apparently(-Resent)?)-To):(.*[^-a-zA-Z0-9_.])?)linux-security procmail: No match on (^((Original-)?(Resent-)?(To|Cc|Bcc)|(X-Envelope|Apparently(-Resent)?)-To):(.*[^-a-zA-Z0-9_.])?)cgochorus procmail: Locking /home/john/Mail/mbox.lock procmail: Assigning LASTFOLDER=/home/john/Mail/mbox procmail: Opening /home/john/Mail/mbox procmail: Acquiring kernel-lock procmail: Unlocking /home/john/Mail/mbox.lock procmail: Notified comsat: john@15295543:/home/john/Mail/mbox Folder: /home/john/Mail/mbox 1 procmail: Unlocking /home/john/.lockmail What this log suggested to me was that using the f (consider the pipe a filter) and w (wait for the filter to finish and check its exit code) were not doing what I intended. Rather than simply allowing time for the sed edit to operate, procmail was sending the mail to the correct box, but was continuing to process succeeding recipes, ultimately setting the flag on mbox. I fixed this by removing the flags and the lock (:). New recipe looks like this :0 * ^TO_kde-linux | sed -e '/Subject:/s/\[kde-linux\] //g' KDE-linux This solved the problem. -- John P. Verel Norwalk, Connecticut
Re: WTC and Pentagon disaster
Thank you. As I work on Wall Street, this was an awful day. I'm well, as are family and friends...so far. John On 09/11/01, 05:36:03PM +0100, Ailbhe Leamy wrote: My thoughts are firmly with anyone bereaved by this disaster. Ailbhe -- Homepage: http://ailbhe.ossifrage.net/ -- John P. Verel Connecticut? You bettor believe!
Segfault in Mutt 1.2.5i, while executing $ update
I produced a segfault in Mutt 1.2.5i as follows. I have a folder hook set for mbox to show only new messages. I started Mutt, went to mbox. Deleted the one message which was marked as new. I then pressed $ to update mbox, thinking this would show the remaining contents (which is over 300 messages). Instead, I got a segfault. Also, it turned the text on my gnome-terminal blue (sadness, I suppose) John -- John P. Verel Norwalk, CT
Re: mail sorting
My experience is that procmail is well worth the modest effort to learn it. You can easily pick up sample recipes that you'll see are really pretty straight forward. John On 07/16/01, 07:31:49PM +0200, Lukasz Zamel wrote: On Mon, Jul 16, 2001 at 06:16:08PM +0530, Suresh Ramasubramanian wrote: Pradeep mutt-users [16/07/01 05:35 -0700]: You can use something like procmail to do this visit www.procmail.org for FAQs on how to go about it or visit http://symonds.net/~pradeep/linux.htm this is how i did learn how to filter my messages. If all you want to do is to sort mail within a folder, the $sort variable helps ... set sort=threads for example. On Mon, 16 Jul 2001, Lukasz Zamel wrote: is it possible to configure Mutt to automatically sort incoming mail? Something like Sorting Office. Maybe it's explained some ware already. I ment sorting to different folders without procmail. Something like fcc-hook but for incoming messages. -- Lukasz Zamel [EMAIL PROTECTED] Reg. Linux User: #202048 Wszystko jest mozliwe pod warunkiem, ze nie wiesz o czym mowisz. -- John P. Verel Norwalk, CT
Printing in Vim: Solved via Oualline's book
One thing that Oualline's new Vim book solved for me (dummy me) is how to print to a system printer from within vim: :w ! lpr Works like a charm, especially in visual mode. Am I the only one who'd been stymied at how to print from within vim? -- John P. Verel Norwalk, CT
Re: Returning to mutt session while viewing attachment?
Merci! On 06/19/01, 11:45:05PM -0400, Brendan Cully wrote: On Tuesday, 19 June 2001 at 23:40, John P. Verel wrote: Hi, Brendan. Thanks for a cool script! Its beauty is what is accomplished in just 5 lines! Two questions, though, if I may? What is the purpose of the sleep command? that was so the cp in the background process was sure to finish before the script returned and mutt unlinked the master file. But looking at it, this is a better way of doing it (and shorter too): #!/bin/sh cp $2 $2.tmp ($1 $2.tmp; rm -f $2.tmp) Any special reason for calling this as a Bourne shell and not Bash? no. -- John P. Verel Norwalk, CT
Dependency problem: OpenSSL and Mutt 1.3.18i-2
I'm attempting to upgrade to Mutt mutt-1.3.18i-2, using an rpm. I get these failed dependencies messages: libcrypto.so.0.9.6.1 is needed by mutt-1.3.18i-2 libssl.so.0.9.6.1 is needed by mutt-1.3.18i-2 libtinfo.so.5 is needed by mutt-1.3.18i-2 Search at rpmfind says that openssl-0.9.6a-4 provides these objects. When I attempt an rpm -Uvh on mutt and openssl, I get a slew of dependency errors relating to libssl.so.1 and libcrypto.so.1 being needed by a few dozen packages. I am, of course, reluctant to do a --nodeps force on such an important package as openssl. I have openssl-0.9.6-3 installed, running a stock Red Hat 7.1 installation. Can anyone suggest a solution? Thanks. John -- John P. Verel Norwalk, CT
Re: Word Wrap
My .vimrc has just this line for this problem: set textwidth=72 On 05/21/01, 08:04:36AM -0400, darren chamberlain wrote: Larry Hignight ([EMAIL PROTECTED]) said something to this effect on 05/18/2001: I'm not sure how I missed this in the Mutt manual and some online tutorials, but I have some people on another mail list complaining that my email isn't wrapping properly. I am using vim as my editor. Which needs to be configured to setup wrapping at 72? Is it in one of the vim files or the .muttrc? set fo=trcq fo == formatoptions set ft=mail ft == filetype set tw=72 tw == textwidth use :help to describe these. Setting ft=mail will also (I believe) set fo to the right options. (darren) -- Any technology indistinguishable from magic is insufficiently advanced. -- John P. Verel Norwalk, CT
Re: Word Wrap
As a variation on the vim invocation, I use this:
set editor =vim +/^$
This puts me at the first blank line of the composition screen.
John
On 05/22/01, 07:23:43AM +0530, Suresh Ramasubramanian wrote:
I use
set editor=/usr/bin/vim +':set textwidth=77' +':set wrap' +\`awk'/^$/ {print i+2;
exit} {i++}' %s\` %s
--
Suresh Ramasubramanian + Wallopus Malletus Indigenensis
mallet @ cluestick.org + Lumber Cartel of India, tinlcI
EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin
--
John P. Verel
Norwalk, CT
Re: scrolling in a message
I have my Konsole setting to xterm (XFree 3.x.x). I also have the following bindings in my .muttrc: bind generic home first-entry bind generic end last-entry bind generic backspace previous-line Seems to me these binding should be extraneous, but everything is working fine...so I leave it alone...for now ;) HTH John On 04/14/01, 02:01:53PM -0500, David Rock wrote: On Sat, Apr 14, 2001 at 07:13:01AM -0700, CB wrote: Could you share some of your settings? You just described my system and the backspace key does not work for previous line and I've not figured out what I need to change within KDE to make it work. I have found that using the Del key instead of the Backspace key works when the Backspace key doesn't. The Enter key has always worked for me to scroll down one line. -- David Rock [EMAIL PROTECTED] -- John P. Verel Norwalk, CT
Re: scrolling in a message
On 04/14/01, 08:44:29AM -0400, Wade A. Mosely wrote: Jeroen Valcke wrote: But how can I scroll line by line, I just can't find this simple thing. Found something about '' and '' but this only works in the message lister. In the pager, you can use the previous-line function to scroll up one line. I believe the default binding for this is the backspace key. For scrolling down one line in the pager, use the next-line function, which is bound by default to the enter key. -- Mr. Wade Also, behavior is somewhat a function of how you run mutt. For instance, I run inside a KDE2.1 Konsole. Konsole allows choice of keyboard mappings. I've had to fiddle with this setting and provide for some explicit mappings in my .muttrc to get what I want. John -- Linux: The Choice of the GNU Generation -- John P. Verel Norwalk, CT
Re: How to display a mail in raw format
On 04/13/01, 08:39:03AM -0400, darren chamberlain wrote:
Dave Pearson ([EMAIL PROTECTED]) said something to this effect on 04/13/2001:
Toggling header mode ("h") will let you see all the headers in the mutt
pager, but it won't show you the entire e-mail as "raw" since it still
parser MIME. Editing the messages ("e") doesn't show you all the headers
(at least, not in v1.2.4i that I'm running).
Depends on the editor, perhaps. With vim 5.7 all headers are visible.
How does choice of editor affect which headers are passed to it for editing
by mutt?
I did hit 'h' to show all the headers, and then 'e' to edit the
message in $editor, and all headers were displayed and editable.
If you hit 'e', without turning off header weeding, then $editor
will only open up what you see. Does that work for anyone else?
If I press 'e' with $editor set to vim, I see all headers. Having
pressed 'h' before makes no difference. I have not experimented with
other editors (emacs, joe, pico, etc) to see if there is any difference
in behavior.
John
(darren)
--
What you do instead of your real work *is* your real work.
-- Roger Ebert
--
John P. Verel
Norwalk, CT
Re: How to display a mail in raw format
On 04/13/01, 04:10:46PM +0200, Thomas Roessler wrote: On 2001-04-13 09:33:17 -0400, John P. Verel wrote: If I press 'e' with $editor set to vim, I see all headers. Having pressed 'h' before makes no difference. I have not experimented with other editors (emacs, joe, pico, etc) to see if there is any difference in behavior. You may wish to make sure that you both have bound edit-message to 'e', and not resend-mesasge. Confirmed. My bindings are default as respects these. Escape e yields resend, e opens vim. Resend-message produces just the standard headers. e produces the whole landslide of 'em :) John -- Thomas Roessler [EMAIL PROTECTED] -- John P. Verel Norwalk, CT
Re: How to display a mail in raw format
On 04/12/01, 05:22:21PM -0400, Mike Broome wrote:
I've found that piping the message out to cat (eg. "|cat") or more
(eg. "|more") does the trick for me. This will dump the entire
message, including header, MIME separators, unrecognized (to mutt)
attachments.
Toggling header mode ("h") will let you see all the headers in the
mutt pager, but it won't show you the entire e-mail as "raw" since it
still parser MIME. Editing the messages ("e") doesn't show you all the
headers (at least, not in v1.2.4i that I'm running).
Depends on the editor, perhaps. With vim 5.7 all headers are visible.
John
Mike
On Thu, Apr 12, 2001 at 11:32:00AM +0200, Tobias Schenk wrote:
Hello,
I was wondering how one can display any mail in it's pure, raw format within Mutt.
So as to get the same result than if I would load the mbox file into an editor and
look at a particular message.
Did I miss how to do it in the docs? Thank you.
Toby
--
Mike Broome
mbroome(at)employees.org
--
John P. Verel
Norwalk, CT
Re: vim and mutt question
You might not always want to move down 6 lines. Perhaps in the future you will add a new header (using my_hdr) to certain messages. You might want to consider the following instead: set editor="vim -c ':0;/^$'" which will search for and move to the first blank line. In an email message that should be the first line after all the headers, no matter how many header lines there are. Hey Tim! A great one. Thanks! I'd just been doing vim + on my editor line, taking to the bottom of a new mail. This is much better. Thanks! John -- John P. Verel Norwalk, CT
Mutt keymapping problem in KDE2.1 Konsole 1.0.1
I just upgraded to KDE2.1. I run Mutt within a Konsole version 1.0.1. It's default keyboard mapping has apparently changed with the upgrade, now defaulting to "xterm (XFree 4.x.x)" This mapping does not work correctly in Mutt. Specifically, the backspace, home and end key do not work. (They should provide scroll up, top and bottom of message respectively). The mapping within Konsole which does work is labeled "xterm (XFree 3.x.x). It does map these keys correctly. Is this an issue? This problem does not occur within a plain xterm, nor an rxvt. -- John P. Verel Norwalk, CT
Re: Mutt keymapping problem in KDE2.1 Konsole 1.0.1
On 03/18/01, 06:11:30PM -0600, [EMAIL PROTECTED] wrote: Whouldn't the problem lie with how your editor handles the various terminals? tw I wouldn't' think so. Konsole under KDE 2.0 worked just fine with default settings. As noted, mutt works fine with other terminals and with what would appear to be an older keyboard mapping. The question strikes me as whether there is any issue with the newer (4.x.x) mapping provided in Konsole ... as this is the piece that just changed on my machine I'd first suspect the problem to be there. John Le jour Sun Mar 18, 2001 at 05:49:30PM +, John P. Verel ([EMAIL PROTECTED]) a ecrit... I just upgraded to KDE2.1. I run Mutt within a Konsole version 1.0.1. It's default keyboard mapping has apparently changed with the upgrade, now defaulting to "xterm (XFree 4.x.x)" This mapping does not work correctly in Mutt. Specifically, the backspace, home and end key do not work. (They should provide scroll up, top and bottom of message respectively). The mapping within Konsole which does work is labeled "xterm (XFree 3.x.x). It does map these keys correctly. Is this an issue? This problem does not occur within a plain xterm, nor an rxvt. -- John P. Verel Norwalk, CT -- John P. Verel Norwalk, CT
