Re: ksh tab completion bug

2020-11-10 Thread Michael Forney
Hi Anton, Thanks for providing those links to the past discussion. Anton Lindqvist wrote: > As I would address this, the numbers of arguments passed to the > completion related routines is already painfully^W long. I would rather > take a step back and introduce a `struct globstate' (just an

Re: ksh tab completion bug

2020-11-10 Thread Anton Lindqvist
On Tue, Nov 10, 2020 at 06:49:28PM +0100, Sven M. Hallberg wrote: > Apologies for jumping in as a bystander, but if I may comment: > > Anton Lindqvist on Tue, Nov 10 2020: > > Been brought up before[1] and rejected[2][3]. > > Anton Lindqvist on Sun, Jul 02, 2017: > > diff below in which slashes

Re: ksh tab completion bug

2020-11-10 Thread Sven M . Hallberg
Apologies for jumping in as a bystander, but if I may comment: Anton Lindqvist on Tue, Nov 10 2020: > Been brought up before[1] and rejected[2][3]. Anton Lindqvist on Sun, Jul 02, 2017: > diff below in which slashes are discarded when comparing the length. I > don't know if any other character

Re: ksh tab completion bug

2020-11-09 Thread Anton Lindqvist
On Mon, Nov 09, 2020 at 11:15:36PM -0800, Michael Forney wrote: > I noticed some strange behavior of ksh in emacs mode when completing > file names that contain spaces (or other characters that need > escaping). > > To illustrate the problem, consider two files 'a b c test1' and > 'a b c test2'.

ksh tab completion bug

2020-11-09 Thread Michael Forney
I noticed some strange behavior of ksh in emacs mode when completing file names that contain spaces (or other characters that need escaping). To illustrate the problem, consider two files 'a b c test1' and 'a b c test2'. ksh will correctly complete `a` and `a\ b\ c\ ` to the common prefix `a\ b\