Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15720
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: Binding Containing Escape Key Fails to Escape History Search |
| Date | 2019-12-12 16:01 -0500 |
| Message-ID | <mailman.747.1576184499.1979.bug-bash@gnu.org> (permalink) |
| References | (1 earlier) <6fcf6dd7-a0b5-8868-797c-cefbcc3346a2@case.edu> <20191031223246.GA8439@midnight> <72ba8e76-5962-3855-2361-d05cf34569a1@case.edu> <20191209001514.GA935957@midnight> <177cc3e6-5ee4-aeb3-41ff-2c92b1f7d52d@case.edu> |
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/
Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Re: Binding Containing Escape Key Fails to Escape History Search Chet Ramey <chet.ramey@case.edu> - 2019-12-12 16:01 -0500
csiph-web