Re: mutt/vim cursor positions

2001-08-01 Thread Kyle Knack
Thanks Thomas! That appears to have done the trick ;) Kyle * Thomas Huemmler <[EMAIL PROTECTED]> [010801 20:16]: >Date: Wed, 1 Aug 2001 11:02:05 +0200 >From: [EMAIL PROTECTED] (Thomas Huemmler) >To: [EMAIL PROTECTED] >Subject: Re: mutt/vim cursor positions >Reply-To: [E

Re: mutt/vim cursor positions

2001-08-01 Thread Christian Kurz
On 01-07-31 Chris Gushue wrote: > Kyle Knack ([EMAIL PROTECTED]) wrote: > > On a side note, and this is definately vim related, I have defined a > > color in my vimrc for message signatures, however with my sig, it colors > > up to the "Kyle Knack" but not the quote. Funny how it's similar to my

Re: mutt/vim cursor positions

2001-08-01 Thread Thomas Huemmler
Hi Kyle, * Kyle Knack <[EMAIL PROTECTED]> [010801 05:46]: > line to just 'vim' and it started working as I expected ;) If any vim > junkies can clarify Chris' question, could you also clue me in as how to > count X lines from the top ? This way I can turn on edit_headers but > still have the cu

Re: mutt/vim cursor positions

2001-07-31 Thread Kyle Knack
t;[EMAIL PROTECTED]> [010731 23:33]: >Date: Tue, 31 Jul 2001 22:26:51 -0500 >From: Chris Gushue <[EMAIL PROTECTED]> >To: Mutt Users <[EMAIL PROTECTED]> >Subject: Re: mutt/vim cursor positions >User-Agent: Mutt/1.3.19i > >Kyle Knack ([EMAIL PROTECTED]) wrote: >>

Re: mutt/vim cursor positions (oops)

2001-07-31 Thread Chris Gushue
My last message quoted the wrong part of Kyle's email, oops :) I meant to refer to the first paragraph about his problem with cursor position when mutt calls vim to edit the message. -- Chris Gushue <[EMAIL PROTECTED]> mutt config files - http://mutt.blackplasma.net bplog news system - http://b

Re: mutt/vim cursor positions

2001-07-31 Thread Chris Gushue
Kyle Knack ([EMAIL PROTECTED]) wrote: > On a side note, and this is definately vim related, I have defined a > color in my vimrc for message signatures, however with my sig, it colors > up to the "Kyle Knack" but not the quote. Funny how it's similar to my > cursor problem. Maybe I should just k