Re: VIM problem when used within mutt
:D You guys are gonna make me have to go reread the diff manpages, aren't you? I can't promise I'll remember to do it all the time but if you quit picking on me, I'll try :) L On 07/11/01 04:25 AM, Thomas Dickey sat at the `puter and typed: > On Tue, Jul 10, 2001 at 09:37:21PM -0400, Louis LeBlanc wrote: > > On 07/10/01 05:37 PM, Ryan Cook sat at the `puter and typed: > > > read. The '-c' flag on a diff provides much more readable content. > > Yes, more readable, but also three times longer - which on smaller > > displays or shorter xterms, has the reverse effect. All a matter of > > actually, I've gotten to regard "diff -u" as more readable than "diff -c" > (ymmv). > > -- > Thomas E. Dickey <[EMAIL PROTECTED]> > http://dickey.his.com > ftp://dickey.his.com > -- Louis LeBlanc Fully Funded Hobbyist, KeySlapper Extrordinaire :) [EMAIL PROTECTED] http://acadia.ne.mediaone.netԿԬ
Re: VIM problem when used within mutt
On 11.07.2001 03:37:21 Louis LeBlanc wrote: > Yes, more readable, but also three times longer - which on smaller How about -u then? Just ~2 times longer and still more readable than "plain" diff.
Re: VIM problem when used within mutt
On Tue, Jul 10, 2001 at 09:37:21PM -0400, Louis LeBlanc wrote: > On 07/10/01 05:37 PM, Ryan Cook sat at the `puter and typed: > > read. The '-c' flag on a diff provides much more readable content. > Yes, more readable, but also three times longer - which on smaller > displays or shorter xterms, has the reverse effect. All a matter of actually, I've gotten to regard "diff -u" as more readable than "diff -c" (ymmv). -- Thomas E. Dickey <[EMAIL PROTECTED]> http://dickey.his.com ftp://dickey.his.com
Re: VIM problem when used within mutt
On 07/10/01 05:37 PM, Ryan Cook sat at the `puter and typed: > On Tue, Jul 10, 2001 at 08:18:20PM -0400, Louis LeBlanc wrote: > > > > Just out of curiosity, how come I rarely see people use the '-c' flag > on their diff output to this mailing list? I can't speak for anybody > but myself, but I, generally, find plain diff output difficult to > read. The '-c' flag on a diff provides much more readable content. > > Just an observation. > > /rc > Yes, more readable, but also three times longer - which on smaller displays or shorter xterms, has the reverse effect. All a matter of perspective, I guess. It'd also be easy to believe that I'm probably just too lazy to hit an extra three keys (unless you take this response into account :) L -- Louis LeBlanc Fully Funded Hobbyist, KeySlapper Extrordinaire :) [EMAIL PROTECTED] http://acadia.ne.mediaone.netԿԬ
Re: VIM problem when used within mutt
On Tue, Jul 10, 2001 at 08:18:20PM -0400, Louis LeBlanc wrote: > Date: Tue, 10 Jul 2001 20:18:20 -0400 > From: Louis LeBlanc <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED], [EMAIL PROTECTED] > Subject: Re: VIM problem when used within mutt > Message-ID: <[EMAIL PROTECTED]> > User-Agent: Mutt/1.3.19i > > I thought that file looked familiar. One problem with it. You must > have emacs set to autoreplace tabs or something. The trailing > whitespace could be from doing a cut and paste, though. > > I fixed your file by putting tabs back where they belong (tabs are > often a pain in the nexk when you work on code, but for regexps and > some config files, they are critical). Here is the diff between yours > (after I fixed it) and the one I use: > > $ diff muttvimrc .mutt/mail.vim > 1d0 > < > 75c74 > < " order is important here! > --- > > " order is imporant here! > 83,84c82,83 > < hi link mailHeaderKey Red > < hi link mailHeaderBlue > --- > > hi link mailHeaderKey Green > > hi link mailHeaderCyan > 86c85 > < hi link mailQuoted2 LightBlue > --- > > hi link mailQuoted2 Cyan Just out of curiosity, how come I rarely see people use the '-c' flag on their diff output to this mailing list? I can't speak for anybody but myself, but I, generally, find plain diff output difficult to read. The '-c' flag on a diff provides much more readable content. Just an observation. /rc > Pretty close. I do remember posting this a while back, and maybe I > did the bad thing and just did a copy/paste. If so, my fault you had > a hard time. This is actually a modified version of the one Felix von > Leitner wrote. His version is actually included with the Vim dist. > and can be found at /usr/share/vim/vim57/syntax/mail.vim (at least on > RH6.2) > > In order to avoid further tab confusion, I am bzipping your repaired > muttvimrc back up and attaching it that way. > > HTH > > Lou > > On 07/10/01 11:45 PM, Marco Fioretti sat at the `puter and typed: > > Hello, > > > > Some days ago, I asked for help on this list because I couldn't > > stand the colors appearing in vim/mutt when replying to messages. > > > > Several people explained how to fix this behavior. I'd like first of > > all to thank them, especially Felix von Leitner, for providing many > > useful suggestions. Eventually I set: > > > > set editor = "/usr/bin/vim -c '/^$/+1' -u '~/.mutt_vim.rc'" > > > > where mutt_vim_rc is the file attached to this message. > > > > Now colors are wonderful, but: > > > > 1) when I reply to message, I see an error message flash in the mutt > > window, too quick to read it. > > > > 2) vim behaves strangely: it doesn't react to the backspace key, or to the back > > arrow key, for example. Running from the command line "vim -s .mutt_vim.rc" > > doesn't produce any visible error. > > > > Any clues, or suggestions on how to capture the flashing error message? > > > > The only thing I can see weird in that file is that, having pasted it from > > the mutt window to an emacs buffer, it ended up with MANY blank spaces at > > the end of each line... > > > > TIA, > > Marco Fioretti > > > > -- > Louis LeBlanc > Fully Funded Hobbyist, KeySlapper Extrordinaire :) > [EMAIL PROTECTED] > http://acadia.ne.mediaone.netԿԬ --
Re: VIM problem when used within mutt
I thought that file looked familiar. One problem with it. You must have emacs set to autoreplace tabs or something. The trailing whitespace could be from doing a cut and paste, though. I fixed your file by putting tabs back where they belong (tabs are often a pain in the nexk when you work on code, but for regexps and some config files, they are critical). Here is the diff between yours (after I fixed it) and the one I use: $ diff muttvimrc .mutt/mail.vim 1d0 < 75c74 < " order is important here! --- > " order is imporant here! 83,84c82,83 < hi link mailHeaderKey Red < hi link mailHeaderBlue --- > hi link mailHeaderKey Green > hi link mailHeaderCyan 86c85 < hi link mailQuoted2 LightBlue --- > hi link mailQuoted2 Cyan Pretty close. I do remember posting this a while back, and maybe I did the bad thing and just did a copy/paste. If so, my fault you had a hard time. This is actually a modified version of the one Felix von Leitner wrote. His version is actually included with the Vim dist. and can be found at /usr/share/vim/vim57/syntax/mail.vim (at least on RH6.2) In order to avoid further tab confusion, I am bzipping your repaired muttvimrc back up and attaching it that way. HTH Lou On 07/10/01 11:45 PM, Marco Fioretti sat at the `puter and typed: > Hello, > > Some days ago, I asked for help on this list because I couldn't > stand the colors appearing in vim/mutt when replying to messages. > > Several people explained how to fix this behavior. I'd like first of > all to thank them, especially Felix von Leitner, for providing many > useful suggestions. Eventually I set: > > set editor = "/usr/bin/vim -c '/^$/+1' -u '~/.mutt_vim.rc'" > > where mutt_vim_rc is the file attached to this message. > > Now colors are wonderful, but: > > 1) when I reply to message, I see an error message flash in the mutt > window, too quick to read it. > > 2) vim behaves strangely: it doesn't react to the backspace key, or to the back > arrow key, for example. Running from the command line "vim -s .mutt_vim.rc" > doesn't produce any visible error. > > Any clues, or suggestions on how to capture the flashing error message? > > The only thing I can see weird in that file is that, having pasted it from > the mutt window to an emacs buffer, it ended up with MANY blank spaces at > the end of each line... > > TIA, > Marco Fioretti -- Louis LeBlanc Fully Funded Hobbyist, KeySlapper Extrordinaire :) [EMAIL PROTECTED] http://acadia.ne.mediaone.netԿԬ muttvimrc.bz2