Re: vim and mutt question
On Sat, Mar 24, 2001 at 09:59:45AM +0200, Peter Pentchev wrote: On Sat, Mar 24, 2001 at 07:35:12AM +, Viktor Lakics wrote: Hi All, I have an autocommand for temporary mutt files. I want to move the cursor down 6 positions automatically when I start a new mail (this would move the cursor right under the headers (i use edit headers). But i can't seem to figure out how to do this from a vimrc file... You could try setting the mutt 'editor' variable to something like /usr/local/bin/vim +6j This shall affect editing old messages, too, but it will probably do what you want. 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. Tim
Re: vim and mutt question
On Sat, Mar 24, 2001 at 02:31:29AM -0600, Timothy Legant wrote: On Sat, Mar 24, 2001 at 09:59:45AM +0200, Peter Pentchev wrote: On Sat, Mar 24, 2001 at 07:35:12AM +, Viktor Lakics wrote: Hi All, I have an autocommand for temporary mutt files. I want to move the cursor down 6 positions automatically when I start a new mail (this would move the cursor right under the headers (i use edit headers). But i can't seem to figure out how to do this from a vimrc file... You could try setting the mutt 'editor' variable to something like /usr/local/bin/vim +6j This shall affect editing old messages, too, but it will probably do what you want. 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. Yeah, that would work better :) G'luck, Peter -- No language can express every thought unambiguously, least of all this one.
Re: vim and mutt question
On Sat, Mar 24, 2001 at 07:35:12AM +, Viktor Lakics wrote: I have an autocommand for temporary mutt files. I want to move the cursor down 6 positions automatically when I start a new mail (this would move the cursor right under the headers (i use edit headers). But i can't seem to figure out how to do this from a vimrc file... Any help? Something like this should work: au BufRead /tmp/mutt-* normal 6j but I would suggest something more like this: au BufRead /tmp/mutt-* normal } so that you cursor is always under the headers even if the number of header lines changes. Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | RF Communications PGU http://www.spocom.com/users/gjohnson/mutt/ | Spokane, Washington, USA
Re: vim and mutt question
I'd like to use this setting, too, but right now I have: set editor="vim -c 'set tw=72 et'" Can I incorporate this into it?? set editor="vim -c ':0;/^$'" On Sat, Mar 24, 2001 at 02:31:29AM -0600, Timothy Legant muttered: | On Sat, Mar 24, 2001 at 09:59:45AM +0200, Peter Pentchev wrote: | On Sat, Mar 24, 2001 at 07:35:12AM +, Viktor Lakics wrote: | Hi All, | | I have an autocommand for temporary mutt files. I want to move the | cursor down 6 positions automatically when I start a new mail (this | would move the cursor right under the headers (i use edit headers). But i |can't seem to figure out how to do this from a vimrc file... | | You could try setting the mutt 'editor' variable to something like | | /usr/local/bin/vim +6j | | This shall affect editing old messages, too, but it will probably | do what you want. | | 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. | | Tim -- /Jason G Helfman "At any given moment, you may find the ticket to the circus that has always been in your possession." Fingerprint: 6A32 3774 E390 33B5 8C96 2AA1 2BF4 BD71 35A1 C149 GnuPG http://www.gnupg.org Get Private! 1024D/35A1C149
Re: vim and mutt question
On Sat, Mar 24, 2001 at 01:06:22AM -0800, Jason Helfman wrote:
I'd like to use this setting, too, but right now I have:
set editor="vim -c 'set tw=72 et'"
Can I incorporate this into it??
set editor="vim -c ':0;/^$'"
From the vim manpage:
-c {command}
{command} will be executed after the first
file has been read. {command} is interpreted
as an Ex command. If the {command} contains
spaces it must be enclosed in double quotes
(this depends on the shell that is used).
Example: Vim "+set si" main.c
Note: You can use up to 10 "+" or "-c" com-
mands.
According to the note, it would be OK to do something like:
set editor="vim -c 'set tw=72 et' -c ':0;/^$'
G'luck,
Peter
--
I had to translate this sentence into English because I could not read the original
Sanskrit.
On Sat, Mar 24, 2001 at 02:31:29AM -0600, Timothy Legant muttered:
| On Sat, Mar 24, 2001 at 09:59:45AM +0200, Peter Pentchev wrote:
| On Sat, Mar 24, 2001 at 07:35:12AM +, Viktor Lakics wrote:
| Hi All,
|
| I have an autocommand for temporary mutt files. I want to move the
| cursor down 6 positions automatically when I start a new mail (this
| would move the cursor right under the headers (i use edit headers). But i
can't seem to figure out how to do this from a vimrc file...
|
| You could try setting the mutt 'editor' variable to something like
|
|/usr/local/bin/vim +6j
|
| This shall affect editing old messages, too, but it will probably
| do what you want.
|
| 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.
Re: vim and mutt question
And btw, mail to the [EMAIL PROTECTED] address bounces.
G'luck,
Peter
--
I am the thought you are now thinking.
On Sat, Mar 24, 2001 at 01:47:25PM +0200, Peter Pentchev wrote:
On Sat, Mar 24, 2001 at 01:06:22AM -0800, Jason Helfman wrote:
I'd like to use this setting, too, but right now I have:
set editor="vim -c 'set tw=72 et'"
Can I incorporate this into it??
set editor="vim -c ':0;/^$'"
From the vim manpage:
-c {command}
{command} will be executed after the first
file has been read. {command} is interpreted
as an Ex command. If the {command} contains
spaces it must be enclosed in double quotes
(this depends on the shell that is used).
Example: Vim "+set si" main.c
Note: You can use up to 10 "+" or "-c" com-
mands.
According to the note, it would be OK to do something like:
set editor="vim -c 'set tw=72 et' -c ':0;/^$'
G'luck,
Peter
--
I had to translate this sentence into English because I could not read the original
Sanskrit.
On Sat, Mar 24, 2001 at 02:31:29AM -0600, Timothy Legant muttered:
| On Sat, Mar 24, 2001 at 09:59:45AM +0200, Peter Pentchev wrote:
| On Sat, Mar 24, 2001 at 07:35:12AM +, Viktor Lakics wrote:
| Hi All,
|
| I have an autocommand for temporary mutt files. I want to move the
| cursor down 6 positions automatically when I start a new mail (this
| would move the cursor right under the headers (i use edit headers). But i
can't seem to figure out how to do this from a vimrc file...
|
| You could try setting the mutt 'editor' variable to something like
|
| /usr/local/bin/vim +6j
|
| This shall affect editing old messages, too, but it will probably
| do what you want.
|
| 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.
Re: compressed folders option
These hooks don't work in my muttrc. open-hook \\.gz$ "gzip -cd %f %t" close-hook \\.gz$ "gzip -c %t %f" append-hook \\.gz$ "gzip -c %t %f" I get the following errors: Error in /home/1/j/jlambert/.muttrc, line 42: open-hook: unknown command Error in /home/1/j/jlambert/.muttrc, line 43: close-hook: unknown command Error in /home/1/j/jlambert/.muttrc, line 44: append-hook: unknown command I tried these hooks in 1.2.5i and 1.3.15i without success. What am I missing here? Thanks, -Jim -- [EMAIL PROTECTED] (Replace Z's with E's to reply) cat /dev/coffee | /dev/cup | /dev/mouth | /dev/nose /dev/keyboard -Anonymous
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
Re: next Mutt release?
On Sat, Mar 24, 2001 at 12:09:08AM +0100, Sven Guckes wrote: * Eugene Lee [EMAIL PROTECTED] [010322 23:39]: I'm just curious to ask is there a timetable for Mutt 1.3 to go stable and be released (Mutt 1.4 I assume?). It would be neat if Mutt had a modular structure that lets people add functionality without having to significantly modify the core. mutt should become a linux kernel module soon. As a reply to my previous post: let this be a lesson for everybody to not read the vim and mutt-users mailing lists at the same time and mixing subjects up completely :-) You will make a fool of yourself in front of everybody :-) Sorry for the noise. And no offence to emacs users on this list ofcourse :-) cheers, roel
Re: next Mutt release?
On Sat, Mar 24, 2001 at 12:09:08AM +0100, Sven Guckes wrote: * Eugene Lee [EMAIL PROTECTED] [010322 23:39]: I'm just curious to ask is there a timetable for Mutt 1.3 to go stable and be released (Mutt 1.4 I assume?). It would be neat if Mutt had a modular structure that lets people add functionality without having to significantly modify the core. mutt should become a linux kernel module soon. Now *that* would be cool. That'll show them emacs users which is the best editor. Heh. cheers, roel
send problems
I have trouble with sending messages, intermittently with another list. I use sendmail and my ISP's SMTP. Mutt shows me sending, a copy ends up in record, that's the end of my knowledge. I know that this is the mutt list but perhaps someone here could help. Does sendmail keep a log file? It would help me see if it thinks that it passed it on. Thanks, Dave
Re: send problems
On Sat, Mar 24, 2001 at 10:52:54AM -0700, Dave Murray wrote: I have trouble with sending messages, intermittently with another list. I use sendmail and my ISP's SMTP. Mutt shows me sending, a copy ends up in record, that's the end of my knowledge. I know that this is the mutt list but perhaps someone here could help. Does sendmail keep a log file? It would help me see if it thinks that it passed it on. Sendmail logs most transactions via syslog, using the facility 'mail'. Usually those end up in /var/log/messages, unless you've redirected them somewhere else in /etc/syslog.conf. G'luck, Peter -- This sentence is false.
Re: send problems
On Sat, Mar 24, 2001 at 07:57:54PM +0200, Peter Pentchev wrote: On Sat, Mar 24, 2001 at 10:52:54AM -0700, Dave Murray wrote: I have trouble with sending messages, intermittently with another list. I use sendmail and my ISP's SMTP. Mutt shows me sending, a copy ends up in record, that's the end of my knowledge. I know that this is the mutt list but perhaps someone here could help. Does sendmail keep a log file? It would help me see if it thinks that it passed it on. Sendmail logs most transactions via syslog, using the facility 'mail'. Usually those end up in /var/log/messages, unless you've redirected them somewhere else in /etc/syslog.conf. G'luck, Peter The default under many linux distributions is /var/log/maillog. Try 'tail -f maillog' for a continuous display of the log file. A. -- Adam Sherman President Technology Architect Tritus Consultant Group Inc. http://www.tritus.ca/
Re: compressed folders option
Jim Lambert muttered: These hooks don't work in my muttrc. open-hook \\.gz$ "gzip -cd %f %t" close-hook \\.gz$ "gzip -c %t %f" append-hook \\.gz$ "gzip -c %t %f" I get the following errors: Error in /home/1/j/jlambert/.muttrc, line 42: open-hook: unknown command Error in /home/1/j/jlambert/.muttrc, line 43: close-hook: unknown command Error in /home/1/j/jlambert/.muttrc, line 44: append-hook: unknown command Well, if you didn't apply the Roland Rosenfeld's compressed-folders- patch... see http://www.spinnaker.de HTH, Michael -- "Oh, I've seen copies [of Linux Journal] around the terminal room at The Labs." (By Dennis Ritchie) PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key
Procmail recipe for PGP 7 encrypted mails
Greetings, I'm looking for a procmail recipe that will modify incoming mails from Outlook/Express that have used PGPi 7.0.3 to encrypt them, so that I can use Mutt to decrypt these broken mails. I've tried using the recipe in PGPnotes.txt but it doesn't seem to work for PGP 7. It used to work fine for PGP 6 so I'm not sure what the difference is. Cheers, Rod -- Rod Pike rodneyp @ utanet.at
Re: send problems
Thank you all, I found the log at: /var/log/mail.log I think that it is decipherable enough for me to believe that the ones that don't make it have been sent to my ISP SMPT host. I suppose that I could ask my ISP to check their log for the disposition of one of the message IDs in question, I don't know if they'll go to the bother. Still not enough information to know for sure, but I'm starting to think that it's that list and not me. Peace, Dave
Re: Save-hook inside a folder-hook
On Sat, Mar 24, 2001 at 12:14:55AM -0800, Gary Johnson wrote: On Fri, Mar 23, 2001 at 05:56:41PM -0700, Duke Normandin wrote: I have the following that doesn't work: folder-hook "IN.mutt" 'save-hook * =mutt' When I'm reading "IN.mutt" and go to save a message, "IN.mutt" keeps coming up as the default for that folder. Any ideas? Tia.. I see a couple of problems here. The first is that '*' in a pattern means to match the preceding item zero or more times. If you want to match everything, use '.' or '~A'. Another is that since hooks accumulate, you are adding a save-hook to the list every time you enter a folder; and since mutt uses the first save-hook in its list whose pattern matches, a save-hook whose pattern matches everything will stop mutt from finding any subsequent save-hooks. So I think this might work, but I haven't tried it: folder-hook "IN.mutt" 'unhook save-hook; save-hook ~A =mutt' Seems so obvious that it ticks me off that I wasn't able to clue-in while reading the Mutt Manual ;,) After my post (above), I did find the stuff about '*' vs '.' while searching the Mutt list archives -- but never stumbled on 'unhook'. Thanks! BTW -- I appreciate the way you respond to e-mail, i.e. your text "follows" the quoted portions. So many people don't know, or don't care! -- -duke Calgary, Alberta, Canada
Re: compressed folders option
Thanks for the help. It works great! -Jim On Sat, Mar 24, 2001 at 06:59:30PM +0100, Michael Tatge wrote: Jim Lambert muttered: These hooks don't work in my muttrc. open-hook \\.gz$ "gzip -cd %f %t" close-hook \\.gz$ "gzip -c %t %f" append-hook \\.gz$ "gzip -c %t %f" I get the following errors: Error in /home/1/j/jlambert/.muttrc, line 42: open-hook: unknown command Error in /home/1/j/jlambert/.muttrc, line 43: close-hook: unknown command Error in /home/1/j/jlambert/.muttrc, line 44: append-hook: unknown command Well, if you didn't apply the Roland Rosenfeld's compressed-folders- patch... see http://www.spinnaker.de HTH, Michael -- "Oh, I've seen copies [of Linux Journal] around the terminal room at The Labs." (By Dennis Ritchie) PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key -- [EMAIL PROTECTED] (Replace Z's with E's to reply) "A witty saying proves nothing." -Voltaire
hook?
I wonder if it's possible to execute the following command automatically on all but "!" and my IO mailbox: "^T~A\nT!(~p|~P|~Q|~F)~d2w\nd" Andre Berger[[EMAIL PROTECTED]]
thread collapsing
How can I achieve this behavior: I want threads to always be collapsed (and %M for index_format available) except for the thread I currently have highlighted, either in the index or pager modes. In other words, I want threads to be automatically collapsed when I move to another thread. I was thinking of trying to set my "j" and "k" keys (up and down in the index menu) to be macros that would automatically collapse the thread when I move to another thread, but how would it know if I'm moving to another thread or simply another message in the same thread? Joshua -- Joshua Haberman[EMAIL PROTECTED] University of Puget Sound[EMAIL PROTECTED] http://www.reverberate.org [EMAIL PROTECTED]
