Received: by 10.42.72.200 with SMTP id p8mr494588icj.85.1312403967079;
        Wed, 03 Aug 2011 13:39:27 -0700 (PDT)
X-BeenThere: vim_dev@googlegroups.com
Received: by 10.231.77.5 with SMTP id e5ls149753ibk.0.gmail; Wed, 03 Aug 2011
 13:39:22 -0700 (PDT)
Received: by 10.42.156.197 with SMTP id a5mr2396088icx.7.1312403962185;
        Wed, 03 Aug 2011 13:39:22 -0700 (PDT)
Received: by 10.42.156.197 with SMTP id a5mr2396087icx.7.1312403962176;
        Wed, 03 Aug 2011 13:39:22 -0700 (PDT)
Return-Path: <Charles.E.Campb...@nasa.gov>
Received: from ndgssmtp01.ndc.nasa.gov (ndgssmtp01.gsfc.nasa.gov [128.183.245.24])
        by gmr-mx.google.com with ESMTP id z10si384658icv.7.2011.08.03.13.39.22;
        Wed, 03 Aug 2011 13:39:22 -0700 (PDT)
Received-SPF: pass (google.com: best guess record for domain of Charles.E.Campb...@nasa.gov designates 128.183.245.24 as permitted sender) client-ip=128.183.245.24;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: best guess record for domain of Charles.E.Campb...@nasa.gov designates 128.183.245.24 as permitted sender) smtp.mail=Charles.E.Campb...@nasa.gov
Received: from xorn.gsfc.nasa.gov (xorn.ndc.nasa.gov [128.183.227.241])
	by ndgssmtp01.ndc.nasa.gov (Postfix) with ESMTP id 28F30BB12FD
	for <vim_dev@googlegroups.com>; Wed,  3 Aug 2011 15:39:21 -0500 (CDT)
Message-ID: <4E39B1F8.1060508@nasa.gov>
Date: Wed, 03 Aug 2011 16:39:20 -0400
From: Charles Campbell <Charles.E.Campb...@nasa.gov>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14
MIME-Version: 1.0
To: vim_dev@googlegroups.com
Subject: Re: [patch] move to next error
References: <20110801213041.GA26269@256bit.org> <201108022030.p72KUm3G019064@masaka.moolenaar.net> <20110802205042.GH26269@256bit.org>
In-Reply-To: <20110802205042.GH26269@256bit.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Christian Brabandt wrote:
> Hi Bram!
>
> On Di, 02 Aug 2011, Bram Moolenaar wrote:
>
>    
>> Christian Brabandt wrote:
>>
>>      
>>> this patch fixes this issue from the todo list:
>>>
>>>
>>> ,----
>>> | 8   Add a command to jump to the next character highlighted with
>>> | "Error".
>>> `----
>>>
>>> It implements the [e and ]e movement commands, which move to the
>>> previous or next error. And while I was at it, I also made [t ]t move to
>>> the previous/next item that is highlighted with TODO highlighting.
>>>        
>> Thanks, I'll put it on the todo list.
>>
>> We are running out of command characters, taking two more from the ] and
>> [ list makes me wonder how many users will use them.  Perhaps we should
>> have one "move to highlight" command with an argument to specify what
>> kind of highlighting?  That would be more future safe.
>>      
> Like what? Something like ]h plus a char, that identifies the
> highlighting?
>    
What about  [h and ]h, which would move to the next/previous instance of 
the highlighting group specified in a new vim option; as a suggestion, 
jumphlgroup .  This would be instead of [t and ]t, and could be used 
instead of [e and]e, too, I suppose.

Regards,
Chip Campbell