Re: ksh in vi-mode and line editing

2022-10-19 Thread Uwe Werler
On 19 Oct 08:49, Klemens Nanni wrote: > On Wed, Aug 31, 2022 at 05:16:27PM +0200, Uwe Werler wrote: > > Hi folks, > > > > I'm just wondering why there's a test for an empty line and args to start > > the > > editor for line editing. In bash one can start vi immediately with an empty > > line by

Re: ksh in vi-mode and line editing

2022-10-19 Thread Uwe Werler
Hi Klemens, On 19 Oct 08:49, Klemens Nanni wrote: > On Wed, Aug 31, 2022 at 05:16:27PM +0200, Uwe Werler wrote: > > Hi folks, > > > > I'm just wondering why there's a test for an empty line and args to start > > the > > editor for line editing. In bash one can start vi immediately with an empty

Re: ksh in vi-mode and line editing

2022-10-19 Thread Klemens Nanni
On Wed, Aug 31, 2022 at 05:16:27PM +0200, Uwe Werler wrote: > Hi folks, > > I'm just wondering why there's a test for an empty line and args to start the > editor for line editing. In bash one can start vi immediately with an empty > line by ^v. Might be there's another reason I don't understand

Re: ksh in vi-mode and line editing

2022-10-19 Thread Uwe Werler
On 31 Aug 17:16, Uwe Werler wrote: > Hi folks, > > I'm just wondering why there's a test for an empty line and args to start the > editor for line editing. In bash one can start vi immediately with an empty > line by ^v. Might be there's another reason I don't understand for this test? > > >