Case-insensitive filename completions

2000-11-01 Thread Kai Großjohann
Right now, Tramp uses `echo foo*' to find completions for foo. If we want completions to be case-insensitive, we have the following options: (1) Always retrieve the whole directory contents. This might be slow in large directories. (2) Say `echo [fF][oO][oO]*' instead. Here, it is not

Re: Case-insensitive filename completions

2000-11-01 Thread Edward J. Sabol
Say `echo [fF][oO][oO]*' instead. [...] > Thoughts? What is the motivation for wanting to do case-insensitive filename completions? I suppose this might be nice for computers with case-insensitive file systems (Windows, Mac OS HFS+), but it's certainly not a desirable feature for most Unix pla

Re: Case-insensitive filename completions

2000-11-01 Thread Daniel Pittman
On 01 Nov 2000, Kai Großjohann <[EMAIL PROTECTED]> wrote: > Right now, Tramp uses `echo foo*' to find completions for foo. If we > want completions to be case-insensitive, Please, don't. I am rather fond of my Unix behaviour. Making it case insensitive would break my expectations and cause tro

Re: Case-insensitive filename completions

2000-11-02 Thread Kai Großjohann
On Wed, 1 Nov 2000, [EMAIL PROTECTED] wrote: > What is the motivation for wanting to do case-insensitive filename > completions? I suppose this might be nice for computers with > case-insensitive file systems (Windows, Mac OS HFS+), but it's > certainly not a desirable feat

Re: Case-insensitive filename completions

2000-11-02 Thread Daniel Pittman
Kai Großjohann <[EMAIL PROTECTED]> writes: > > On 02 Nov 2000, [EMAIL PROTECTED] wrote: >> It should be supported. I don't know quite how, though, except maybe >> with find(1) based hacks. (-iname is your friend. :) > > `-iname' is peculiar to GNU find, I think. Solaris 2.6 doesn't have > it. Is

Re: Case-insensitive filename completions

2000-11-02 Thread Kai Großjohann
On 3 Nov 2000, Daniel Pittman wrote: > Kai Großjohann <[EMAIL PROTECTED]> writes: > >> Are you suggesting "find . -name '[fF][oO][oO]*' -print" rather >> than "echo [fF][oO][oO]*" because of command line length >> restrictions? > > No. I was suggesting it because it does not require nearly the s

Re: Case-insensitive filename completions

2000-11-02 Thread Kai Großjohann
On 2 Nov 2000, [EMAIL PROTECTED] wrote: > File name completion isn't case sensitive in my XEmacs; is this a > Windows thing (ick) or a new-GNU-Emacs thing? There is a variable completion-ignore-case. Of course, filename completion in Tramp should depend on this variable. kai -- I like BOTH ki

Re: Case-insensitive filename completions

2000-11-02 Thread Daniel Pittman
Kai Großjohann <[EMAIL PROTECTED]> writes: > > On 2 Nov 2000, [EMAIL PROTECTED] wrote: >> File name completion isn't case sensitive in my XEmacs; is this a >> Windows thing (ick) or a new-GNU-Emacs thing? > > There is a variable completion-ignore-case. Of course, filename > completion in Tramp sho

Re: Case-insensitive filename completions

2000-11-02 Thread Kai Großjohann
On 02 Nov 2000, [EMAIL PROTECTED] wrote: > It should be supported. I don't know quite how, though, except maybe > with find(1) based hacks. (-iname is your friend. :) `-iname' is peculiar to GNU find, I think. Solaris 2.6 doesn't have it. Are you suggesting "find . -name '[fF][oO][oO]*' -print