Re: bug: command-line-tab-completion

On Mon, 2 Oct 2006 12:18:51 +0200
Atman Sense <mattenklicker@xxxxxxx> wrote:

> I have problems with command-line-tab-completion:
> If you have a file name with spaces, the completion does not work.
Completion of a command whose name includes space(s) won't work, because the 
part of the entered command after any whitespace will be treated as argument(s).

On the other hand, completion of command argument(s) which include spaces does 
seem to work. Note that the default keybinding for a <Tab> press in the command 
line is to look everywhere in $PATH for completion. If the keybinding 
action-parameter is set to "files" it will look instead in the active directory 
(see the distributed file "ACTIONS" at the "command.complete" entry). Space(s) 
in any completed name are escaped with "\" (in the "files" mode at least, I 
didn't test a real command with spaces).


> If you have files: "test 1.jpg, test 2.jpg, test 3.jpg" and you try to
> display them with "xv test*.jpg" it doesn't work because the file names
> are not encapsulated with "" or \
True. AFAIK no shell does automatic quoting of any parameter with spaces. How 
would a shell know what to quote, as against what is intended whitespace? In 
e2, you can select the items and run "xv %f".

Regards
Tom


-- 
Users can unsubscribe from the list by sending email to 
emelfm2-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field or by 
logging into the web interface.

Other related posts: