Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #15720 > unrolled thread

Re: Binding Containing Escape Key Fails to Escape History Search

Started byChet Ramey <chet.ramey@case.edu>
First post2019-12-12 16:01 -0500
Last post2019-12-12 16:01 -0500
Articles 1 — 1 participant

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Binding Containing Escape Key Fails to Escape History Search Chet Ramey <chet.ramey@case.edu> - 2019-12-12 16:01 -0500

#15720 — Re: Binding Containing Escape Key Fails to Escape History Search

FromChet Ramey <chet.ramey@case.edu>
Date2019-12-12 16:01 -0500
SubjectRe: Binding Containing Escape Key Fails to Escape History Search
Message-ID<mailman.747.1576184499.1979.bug-bash@gnu.org>
On 12/8/19 7:15 PM, sunnycemetery@gmail.com wrote:
> On 2019-11-04 14:41, Chet Ramey wrote:
>> If \ef and Alt+f generate distinct character sequences, you can bind them 
>> separately. If they don't, you can't. This has nothing to do with whether 
>> or not incremental searching expands keyboard macros.
> 
> In that case, how would one go about binding æ such that it both exits an 
> incremental search and executes forward-word?

There isn't, really. Any character that doesn't end the search or map to
one of a few editing functions that the isearch code uses to modify the
search string is added to the search string.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/

[toc] | [standalone]


Back to top | Article view | gnu.bash.bug


csiph-web