git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: janparadowski <janp617@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] Prevent space after directories in tcsh completion
Date: Tue, 1 Jul 2014 10:45:28 -0700 (PDT)	[thread overview]
Message-ID: <1404236728065-7614312.post@n2.nabble.com> (raw)
In-Reply-To: <E59706EF8DB1D147B15BECA3322E4BDC06997E@eusaamb103.ericsson.se>

Hello

script works beautifully except for a small thing:

reporoot> ls 
 folder/ folder_file.txt

reproot> git commit fo<TAB>
completes to git commit folderSPACE without presenting the completion
options

(git diff fo<TAB> completes as expected to git diff folder and gives the 2
completion options)

is that easily fixable too?



--
View this message in context: http://git.661346.n2.nabble.com/PATCH-Prevent-space-after-directories-in-tcsh-completion-tp7574444p7614312.html
Sent from the git mailing list archive at Nabble.com.

      reply	other threads:[~2014-07-01 17:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-07 19:07 [PATCH] Prevent space after directories in tcsh completion Marc Khouzam
2014-07-01 17:45 ` janparadowski [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1404236728065-7614312.post@n2.nabble.com \
    --to=janp617@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).