From: Kyle Moffett <mrmacman_g4@mac.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
Dave Young <hidave.darkstar@gmail.com>,
Li Yang-r58472 <LeoLi@freescale.com>,
Josh Triplett <josh@kernel.org>,
Jan Engelhardt <jengelh@computergmbh.de>,
Chris Shoemaker <c.shoemaker@cox.net>,
Josh Triplett <josht@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [OT] Vim highlighting for trailing spaces
Date: Fri, 29 Jun 2007 20:00:19 -0400 [thread overview]
Message-ID: <6849664D-7A3F-47CF-A976-2EFE44502E6D@mac.com> (raw)
In-Reply-To: <d120d5000706290549n9c2babfua0f4563e603835b5@mail.gmail.com>
On Jun 29, 2007, at 08:49:42, Dmitry Torokhov wrote:
> On 6/29/07, Michael Tokarev <mjt@tls.msk.ru> wrote:
>> highlight WhitespaceEOL ctermbg=red guibg=red
>> match WhitespaceEOL /\s\+$/
>>
>> Works without any glitches here (not "laggy"). But I don't use
>> syntax coloring - never tried if it works with coloring or not.
>>
>
> That only highlights whitespace at the end of the lines. You might
> want to use pattern below to also highlight "tab after space" in
> the middle of the line:
>
> :highlight RedundantSpaces ctermbg=red guibg=red
> :match RedundantSpaces /\s\+$\| \+\ze\t/
You missed the nice part about my vimrc patterns: :-D
Kyle Moffett wrote:
> It always displays trailing whitespace and spaces-before tabs...
> except if your cursor is at the end of the whitespace.
They intentionally *don't* display whitespace at the end of the line
to the left of your cursor. I tried that one (that you quoted), but
got annoyed by the fact that immediately after you typed any space or
tab you had a little red blob to the left of the cursor. So some of
that "lagginess" is intentionaly (although not all of it, due to vim
limitations).
Cheers,
Kyle Moffett
next prev parent reply other threads:[~2007-06-30 0:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 17:59 [PATCH] CodingStyle: Add information about trailing whitespace Josh Triplett
2007-06-27 18:05 ` Chris Shoemaker
2007-06-27 18:17 ` Josh Triplett
2007-06-27 19:32 ` Chris Shoemaker
2007-06-27 22:18 ` Jan Engelhardt
2007-06-28 6:00 ` dave young
2007-06-28 6:08 ` Josh Triplett
2007-06-28 6:29 ` dave young
2007-06-28 6:52 ` Jan Engelhardt
2007-06-28 6:58 ` Josh Triplett
2007-06-28 7:08 ` Li Yang-r58472
2007-06-28 7:10 ` Dave Young
2007-06-28 7:20 ` Dave Young
2007-06-29 3:11 ` [OT] Vim highlighting for trailing spaces Kyle Moffett
2007-06-29 7:39 ` Jan Engelhardt
2007-06-29 7:53 ` Josh Triplett
2007-06-29 8:01 ` Jan Engelhardt
2007-06-29 8:42 ` Josh Triplett
2007-06-29 9:21 ` Björn Steinbrink
2007-06-29 9:26 ` Dave Young
2007-06-29 12:40 ` Michael Tokarev
2007-06-29 12:49 ` Dmitry Torokhov
2007-06-30 0:00 ` Kyle Moffett [this message]
2007-06-29 2:03 ` [PATCH] CodingStyle: Add information about trailing whitespace Andy Isaacson
2007-06-27 19:31 ` Andrew Morton
2007-06-27 22:14 ` Jan Engelhardt
2007-06-27 22:14 ` Oleg Verych
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6849664D-7A3F-47CF-A976-2EFE44502E6D@mac.com \
--to=mrmacman_g4@mac.com \
--cc=LeoLi@freescale.com \
--cc=akpm@linux-foundation.org \
--cc=c.shoemaker@cox.net \
--cc=dmitry.torokhov@gmail.com \
--cc=hidave.darkstar@gmail.com \
--cc=jengelh@computergmbh.de \
--cc=josh@kernel.org \
--cc=josht@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®