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 github.2...@yendor.com wrote:
tcsh users who happen to have 'set noclobber' elsewhere in their ~/.tcshrc or
~/.cshrc startup files
.
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.tcsh
index 6104a42..4a790d8 100644
--- a/contrib/completion/git-completion.tcsh
+++ b/contrib/completion
-by: Junio C Hamano gits...@pobox.com
Reviewed-by: Christian Couder christian.cou...@gmail.com
Signed-off-by: Ariel Faigon github.2...@yendor.com
---
contrib/completion/git-completion.tcsh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/contrib/completion/git-completion.tcsh
b
-by: Junio C Hamano notificati...@github.com
Mentored-by: Christian Couder christian.cou...@gmail.com
Signed-off-by: Ariel Faigon github.2...@yendor.com
---
contrib/completion/git-completion.tcsh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/contrib/completion/git
Hi,
Quoting Marc Khouzam marc.khou...@gmail.com:
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
On Fri, Apr 24, 2015 at 7:30 AM, SZEDER Gábor sze...@ira.uka.de wrote:
Hi,
Quoting Marc Khouzam marc.khou...@gmail.com:
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.
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 ftab
you can run:
bash ~/.git-completion.tcsh.bash git
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
Quoting Perry Rajnovic perry.rajno...@gmail.com:
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
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:
-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 have
-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?
-BEGIN PGP SIGNED MESSAGE
-completion.bash.
I also noted that zsh on my system have preinstalled git completion
support (enabled with autoload).
The code is not the one available in the git source tree.
I don't know if the code is from Debian or zsh.
$tcsh
synapsis:~/projects/git/contrib/git source ~/.git-completion.tcsh
13 matches
Mail list logo
