Re: ksh ^R vs EDITOR=vi

2017-08-28 Thread Paul de Weerd
On Mon, Aug 28, 2017 at 09:52:56PM +0200, Jeremie Courreges-Anglas wrote: | On Mon, Aug 28 2017, Stuart Henderson wrote: | > On 2017-08-28, mar...@martinbrandenburg.com wrote: | >> What works is to set EDITOR in your profile, then set -o emacs. The other | >> order will result in the shell chan

Re: ksh ^R vs EDITOR=vi

2017-08-28 Thread Jeremie Courreges-Anglas
On Mon, Aug 28 2017, Stuart Henderson wrote: > On 2017-08-28, mar...@martinbrandenburg.com > wrote: >> What works is to set EDITOR in your profile, then set -o emacs. The other >> order will result in the shell changing to vi mode. > > That's fine until you su :) > >> Or we could all set EDITOR

Re: ksh ^R vs EDITOR=vi

2017-08-28 Thread Stuart Henderson
On 2017-08-28, mar...@martinbrandenburg.com wrote: > What works is to set EDITOR in your profile, then set -o emacs. The other > order will result in the shell changing to vi mode. That's fine until you su :) > Or we could all set EDITOR to ed, the STANDARD text editor. An alternative hack is

Re: ksh ^R vs EDITOR=vi

2017-08-28 Thread martin
> From andreas.kah...@nbis.se Mon Aug 28 09:27:40 2017 > Date: Mon, 28 Aug 2017 10:53:45 +0200 > From: Andreas Kusalananda =?iso-8859-1?B?S+Ro5HJp?= > To: Jan Stary > Subject: Re: ksh ^R vs EDITOR=vi > > ^R is for searching backwards in the command line history in Emacs mode

Re: ksh ^R vs EDITOR=vi

2017-08-28 Thread Andreas Kusalananda Kähäri
On Sun, Aug 27, 2017 at 05:02:36PM +0200, Jan Stary wrote: > This is current/amd64. I am using ksh(1) as a shell. > Using ^R opens a search in the command history. > However, with 'export EDITOR=vi', pressing ^R > just literarily types '^R' and does not open > the history search. Is that expected?

Re: ksh ^R vs EDITOR=vi

2017-08-27 Thread Florian Ermisch
Am 27. August 2017 23:43:38 MESZ schrieb Jeremie Courreges-Anglas : >On Sun, Aug 27 2017, Florian Ermisch >wrote: >> Hi Jeremie, >> >> Am 27. August 2017 17:57:57 MESZ schrieb Jeremie Courreges-Anglas >: >>>On Sun, Aug 27 2017, Jan Stary wrote: This is current/amd64. I am using ksh(1) as

Re: ksh ^R vs EDITOR=vi

2017-08-27 Thread Jeremie Courreges-Anglas
On Sun, Aug 27 2017, Florian Ermisch wrote: > Hi Jeremie, > > Am 27. August 2017 17:57:57 MESZ schrieb Jeremie Courreges-Anglas > : >>On Sun, Aug 27 2017, Jan Stary wrote: >>> This is current/amd64. I am using ksh(1) as a shell. >>> Using ^R opens a search in the command history. >>> However, wi

Re: ksh ^R vs EDITOR=vi

2017-08-27 Thread Florian Ermisch
Hi Jeremie, Am 27. August 2017 17:57:57 MESZ schrieb Jeremie Courreges-Anglas : >On Sun, Aug 27 2017, Jan Stary wrote: >> This is current/amd64. I am using ksh(1) as a shell. >> Using ^R opens a search in the command history. >> However, with 'export EDITOR=vi', pressing ^R >> just literarily ty

Re: ksh ^R vs EDITOR=vi

2017-08-27 Thread Martin Bock
No idea about ^R, but typing ESC /pattern in vi mode looks for earlier commands containing pattern ... On Sun, Aug 27, 2017 at 05:02:36PM +0200, Jan Stary wrote: > This is current/amd64. I am using ksh(1) as a shell. > Using ^R opens a search in the command history. > However, with 'export EDITOR

Re: ksh ^R vs EDITOR=vi

2017-08-27 Thread Jeremie Courreges-Anglas
On Sun, Aug 27 2017, Jan Stary wrote: > This is current/amd64. I am using ksh(1) as a shell. > Using ^R opens a search in the command history. > However, with 'export EDITOR=vi', pressing ^R > just literarily types '^R' and does not open > the history search. Is that expected? EDITOR=vi puts the

ksh ^R vs EDITOR=vi

2017-08-27 Thread Jan Stary
This is current/amd64. I am using ksh(1) as a shell. Using ^R opens a search in the command history. However, with 'export EDITOR=vi', pressing ^R just literarily types '^R' and does not open the history search. Is that expected? Jan