-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 08/01/2013 19:05, John Keeping ha scritto:
> [...]
>>
>> After some searching, I found how this is supposed to be done.
>> It is possible to use the -o filenames option to tell Bash completion
>> that "the compspec generates filenames, so it can per
On Tue, Jan 08, 2013 at 06:54:09PM +0100, Manlio Perillo wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Il 05/01/2013 21:23, Marc Khouzam ha scritto:
>> [...]
>> 4- Completion choices include their entire path, which is not what bash does
>> by default. For example:
>>> cd git/cont
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 05/01/2013 21:23, Marc Khouzam ha scritto:
> [...]
> 4- Completion choices include their entire path, which is not what bash does
> by default. For example:
>> cd git/contrib
>> ls completion/git-
> git-completion.bash git-completion.tcsh git-co
ail.com
> Subject: Re: [PATCH v4] git-completion.bash: add support for
> path completion
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Il 05/01/2013 21:23, Marc Khouzam ha scritto:
> > [...]
> > Below are two suggestions that are in line with this effort
&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 05/01/2013 21:23, Marc Khouzam ha scritto:
> [...]
> Below are two suggestions that are in line with this effort but that are not
> regressions.
>
> A) It would be nice if
> git commit -a
> also completed with untracked files
>
$ git commit -a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 05/01/2013 21:23, Marc Khouzam ha scritto:
> [...]
> Thanks for this, it improves the situation dramatically.
> I did further testing with your patch and found some less obvious
> issues. I didn't debug the script myself as I'm not that familiar wi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 05/01/2013 07:27, Junio C Hamano ha scritto:
> Junio C Hamano writes:
>
>> Marc Khouzam writes:
>>
>>> I've been playing with it but I'm not getting the expected
>>> behavior when I cd to a sub-directory.
>>
>> Thanks for testing. Manlio?
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 05/01/2013 21:23, Marc Khouzam ha scritto:
> [...]
> I did further testing with your patch and found some less obvious
> issues. I didn't debug the script myself as I'm not that familiar with
> it either, but I think the testcases below should help
> Junio C Hamano writes:
>
>> Marc Khouzam writes:
>>
>>> I've been playing with it but I'm not getting the expected
>>> behavior when I cd to a sub-directory.
>>
>> Thanks for testing. Manlio?
>
> Can you try the attached patch?
Thanks for this, it improves the situation dramatically.
I di
Junio C Hamano writes:
> Marc Khouzam writes:
>
>> I've been playing with it but I'm not getting the expected
>> behavior when I cd to a sub-directory.
>
> Thanks for testing. Manlio?
Can you try the attached patch?
As I am not familiar with the completion machinery, take this with a
large g
Marc Khouzam writes:
> I've been playing with it but I'm not getting the expected
> behavior when I cd to a sub-directory.
Thanks for testing. Manlio?
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info
> -Original Message-
> From: git-ow...@vger.kernel.org
> [mailto:git-ow...@vger.kernel.org] On Behalf Of Manlio Perillo
> Sent: Friday, December 21, 2012 11:55 AM
> To: git@vger.kernel.org
> Cc: sze...@ira.uka.de; felipe.contre...@gmail.com; Manlio Perillo
> Subject: [PATCH v4] git-comple
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 21/12/2012 18:59, Junio C Hamano ha scritto:
> Manlio Perillo writes:
>
>> +case "$path" in
>> +?*/*) echo "${path%%/*}/" ;;
>> +*) echo $path ;;
>
> $path unquoted???
>
Missed again, thanks.
I hope this is r
Manlio Perillo writes:
> + case "$path" in
> + ?*/*) echo "${path%%/*}/" ;;
> + *) echo $path ;;
$path unquoted???
> +# __git_index_files accepts 1 or 2 arguments:
> +# 1: Options to pass to ls-files (required).
> +#Supported options are --cached, --modif
14 matches
Mail list logo
