From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Lennart Borgman" Newsgroups: gmane.emacs.devel Subject: Re: Yanking isearch to highlight-regexp Date: Mon, 16 Jun 2008 13:13:02 +0200 Message-ID: References: <4853F884.7000609@gmail.com> <48545D78.8080103@gmail.com> <4854E536.8040407@gmail.com> <87k5gql900.fsf@jurta.org> <48558541.5000209@gmail.com> <87od62iblh.fsf@jurta.org> <4855A147.20703@gmail.com> <87od61emcv.fsf@jurta.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_20693_8919838.1213614782234" X-Trace: ger.gmane.org 1213614800 21118 80.91.229.12 (16 Jun 2008 11:13:20 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 16 Jun 2008 11:13:20 +0000 (UTC) Cc: David Koppelman , emacs-devel@gnu.org To: "Juri Linkov" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jun 16 13:14:01 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1K8Cet-0007ss-Ke for ged-emacs-devel@m.gmane.org; Mon, 16 Jun 2008 13:13:59 +0200 Original-Received: from localhost ([127.0.0.1]:51648 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K8Ce5-0003gH-Cr for ged-emacs-devel@m.gmane.org; Mon, 16 Jun 2008 07:13:09 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K8Ce1-0003fU-Ct for emacs-devel@gnu.org; Mon, 16 Jun 2008 07:13:05 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K8Cdz-0003ey-UM for emacs-devel@gnu.org; Mon, 16 Jun 2008 07:13:04 -0400 Original-Received: from [199.232.76.173] (port=57751 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K8Cdz-0003ev-P3 for emacs-devel@gnu.org; Mon, 16 Jun 2008 07:13:03 -0400 Original-Received: from fg-out-1718.google.com ([72.14.220.159]:6125) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1K8Cdz-0008Qk-Cq for emacs-devel@gnu.org; Mon, 16 Jun 2008 07:13:03 -0400 Original-Received: by fg-out-1718.google.com with SMTP id l26so3813816fgb.30 for ; Mon, 16 Jun 2008 04:13:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=sGBnUWGCSfUbDx8pXwTf75aUUeg7WSEeWvdodJoXFQc=; b=jgh2LWigZk2rz+YBz+E+Liia66T1gAL6pqKWBZDkpbVCwlyQWTODcZaIK6AoWr1Gu1 sCBPIZKQ0f7QN2ZE4+FWm49nTHPRu3P65dxG8wSFWXaWGtTCZPoqNg3tccy1Q7CAouHh ow32ZMf8lea17jyRBR7PhgczejdZAjoOd5yhA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=R+PH5NRzhPEs1MX745uGQCqzAytfNTFPfnj5SpQWYUFpZcGt5i1EJU6fQcsGz9kqDk /sQG+CFIF9kmtUYfJz+Zy5W/ke36ywNhUbnH8Xb4MhxRvt7SyIvC1uCSIHqWUlbjrjfi A1C42uKAijfBK+wXCexR5Gr+1AVboTiw6pmqE= Original-Received: by 10.86.60.14 with SMTP id i14mr7721187fga.75.1213614782251; Mon, 16 Jun 2008 04:13:02 -0700 (PDT) Original-Received: by 10.86.66.2 with HTTP; Mon, 16 Jun 2008 04:13:02 -0700 (PDT) In-Reply-To: <87od61emcv.fsf@jurta.org> X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:99299 Archived-At: ------=_Part_20693_8919838.1213614782234 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On 6/16/08, Juri Linkov wrote: > > >>>> I think the key `C-x w' by its mnemonics would be more suitable for > >>>> a command that writes to the file like `C-x C-w'. > >>>> > >>>> As the comment in hi-lock.el suggests to bind it rather to `C-z h', > >>> I just want the key binding to be the same as I use outside of isearch. > >>> > >>> There were no global binding for `occur' so in that case I thought > >>> `M-s o' was good, but in this case I would really prefer the same > >>> binding inside isearch. > >> > >> `C-x w h' is not available until hi-lock.el is loaded, but `M-s h' > >> is the pretty harmless and convenient key binding to keep the > >> isearch highlighting permanent in the entire buffer. > > > > Yes, but I suggested adding `C-x w h' to global-map too. Is there any > > reason not to do that? (It is useful, not dangerous and the binding seems > > to be reserved.) > > I think it is better to reserve the global `C-x w' for more > mnemonic commands (e.g. "write" or "window"), and rebind hi-lock > keys to the search specific prefix key. That idea seems good to me as long as a key for highlight-regexp is defined in global-map. ------=_Part_20693_8919838.1213614782234 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
On 6/16/08, Juri Linkov <juri@jurta.org> wrote:
>>>> I think the key `C-x w' by its mnemonics would be more suitable for
>>>> a command that writes to the file like `C-x C-w'.
>>>>
>>>> As the comment in hi-lock.el suggests to bind it rather to `C-z h',
>>> I just want the key binding to be the same as I use outside of isearch.
>>>
>>> There were no global binding for `occur' so in that case I thought
>>> `M-s o' was good, but in this case I would really prefer the same
>>> binding inside isearch.
>>
>> `C-x w h' is not available until hi-lock.el is loaded, but `M-s h'
>> is the pretty harmless and convenient key binding to keep the
>> isearch highlighting permanent in the entire buffer.
>
> Yes, but I suggested adding `C-x w h' to global-map too. Is there any
> reason not to do that? (It is useful, not dangerous and the binding seems
> to be reserved.)

I think it is better to reserve the global `C-x w' for more
mnemonic commands (e.g. "write" or "window"), and rebind hi-lock
keys to the search specific prefix key.
 
That idea seems good to me as long as a key for highlight-regexp is defined in global-map.

 

 
------=_Part_20693_8919838.1213614782234--