quot; output ;-)
In case anybody is wondering, that "Helped-by: notifications@github"
was merely because I said "this change makes sense, care to send it
over to us at git@vger?" from github UI on Ariel's commit. I do not
deserve helped-by for merely encouraging participa
t noclobber' users.
Helped-by: Junio C Hamano
Reviewed-by: Christian Couder
Signed-off-by: Ariel Faigon
---
contrib/completion/git-completion.tcsh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/contrib/completion/git-completion.tcsh
b/contrib/completion/git-completion
The subject is better but still not quite there. I suggest:
[PATCH] git-completion.tcsh: fix redirect with noclobber
On Tue, Jun 9, 2015 at 1:01 AM, Ariel Faigon wrote:
> tcsh users who happen to have 'set noclobber' elsewhere in their ~/.tcshrc or
> ~/.cshrc startup files g
;set noclobber' users.
Helped-by: Junio C Hamano
Mentored-by: Christian Couder
Signed-off-by: Ariel Faigon
---
contrib/completion/git-completion.tcsh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/contrib/completion/git-completion.tcsh
b/contrib/completion/git-com
On Fri, Apr 24, 2015 at 7:30 AM, SZEDER Gábor wrote:
> Hi,
>
> Quoting Marc Khouzam :
>>
>> Hi,
>>
>> I did notice the problem a while ago and had traced it back to the
>> fact that the bash completion scripts no longer adds the trailing '/'
>> at the end of directories.
>> Tcsh needs that '/' to
Hi,
Quoting Marc Khouzam :
Hi,
I did notice the problem a while ago and had traced it back to the
fact that the bash completion scripts no longer adds the trailing '/'
at the end of directories.
Tcsh needs that '/' to know not to add that annoying extra space.
Bash 3 needed to put it that trai
he tcsh script, so things work.
I tried with both git add and git rm and didn't see the problem as you
described it.
You can troubleshoot the git-completion.tcsh script by running the
generated final script directly. For example, to see the completions
for a command line like:
git rm f
y
Gábor,
I updated git to include the macports install with bash completion. under bash
it does not exhibit the problem as I described it. To be sure that the
completion scripts installed via macports weren’t newer/different (the .bash
completion file had a few minor diffs from what I had been u
Quoting Perry Rajnovic :
When using the auto-completion included with git for tcsh, several
commands do directly completion with an additional space appended to
the end, which defeats the ability to complete to a deeper
sub-directory.
For example, if I have a git repository including the follo
When using the auto-completion included with git for tcsh, several commands do
directly completion with an additional space appended to the end, which defeats
the ability to complete to a deeper sub-directory.
For example, if I have a git repository including the following:
basedir/foo/bar/somef
t caused by your changes.
>
> another problem is that a space is added after a directory name.
>
>> The lastest version of git-completion.tcsh in the pu branch should
>> fix that problem. It was committed yesterday so you may not have it.
>
Ok, thanks.
Reg
> -Original Message-
> From: git-ow...@vger.kernel.org
> [mailto:git-ow...@vger.kernel.org] On Behalf Of Manlio Perillo
> Sent: Wednesday, January 09, 2013 2:17 PM
> To: git@vger.kernel.org
> Subject: git-completion.tcsh and git-completion.zsh are broken?
>
&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
I have finally resolved all the problems with my path completion in
git-completion.bash and, in order to avoid regressions, I'm checking the
git-completion.zsh and git-completion.tcsh scripts, since they use the
bash completion support.
I
13 matches
Mail list logo
