Re: [PATCH] Handle path completion and colon for tcsh script

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 02/02/2013 21:10, Junio C Hamano ha scritto: Marc Khouzam marc.khou...@ericsson.com writes: Recent enhancements to git-completion.bash provide intelligent path completion for git commands. Such completions do not add the '/' at the end of

Re: [PATCH] Handle path completion and colon for tcsh script

Manlio Perillo manlio.peri...@gmail.com writes: The problem is that when using the new `compopt -o filenames` command, Bash assumes COMPREPLY contains a list of filenames, and when it detects a directory name, it adds a slash. The problem is, if the directory name *already* has a slash, Bash

RE: [PATCH] Handle path completion and colon for tcsh script

The problem is, if the directory name *already* has a slash, Bash adds another slash! So bash users do see the trailing slash because bash adds one to what we compute and return, which we do strip the trailing slash exactly because we know bash will add one. The problem is slightly

Re: [PATCH] Handle path completion and colon for tcsh script

Thanks for a detailed explanation. The two examples illustrating different interpretation of the same word were really good. Will replace and requeue. -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at