From: Manlio Perillo <manlio.perillo@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Marc Khouzam <marc.khouzam@ericsson.com>,
git@vger.kernel.org, szeder@ira.uka.de,
felipe.contreras@gmail.com
Subject: Re: [PATCH v4] git-completion.bash: add support for path completion
Date: Sun, 06 Jan 2013 19:00:21 +0100 [thread overview]
Message-ID: <50E9BBB5.3000707@gmail.com> (raw)
In-Reply-To: <7vehi0qh4x.fsf@alter.siamese.dyndns.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Il 05/01/2013 07:27, Junio C Hamano ha scritto:
> Junio C Hamano <gitster@pobox.com> writes:
>
>> Marc Khouzam <marc.khouzam@ericsson.com> 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, it seems to fix the problem.
> As I am not familiar with the completion machinery, take this with a
> large grain of salt. Here is my explanation of what is going on in
> this "how about this" fixup:
>
> * Giving --git-dir from the command line (or GIT_DIR environment)
> without specifying GIT_WORK_TREE is to signal Git that you are at
> the top of the working tree. "git ls-files" will then show the
> full tree even outside the real $cwd because you are lying to
> Git.
>
I was not aware of this, and blindly copied the code from the other
existing functions.
However the other completion functions never have to deal with paths in
the working directory.
I have applied the patch to my local branch.
> [...]
Regards Manlio
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlDpu7UACgkQscQJ24LbaUSmUACgl+OKUyvpp183kFZGmBpOfqm1
yqEAnjxcqmZYvWSeIpOo6cNFl/dnMH76
=oE/+
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2013-01-06 18:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-21 16:54 [PATCH v4] git-completion.bash: add support for path completion Manlio Perillo
2012-12-21 17:59 ` Junio C Hamano
2012-12-21 19:02 ` Manlio Perillo
2013-01-04 21:25 ` Marc Khouzam
2013-01-04 23:20 ` Junio C Hamano
2013-01-05 6:27 ` Junio C Hamano
2013-01-05 20:23 ` Marc Khouzam
2013-01-05 21:27 ` Manlio Perillo
2013-01-06 18:39 ` Manlio Perillo
2013-01-07 13:43 ` Manlio Perillo
2013-01-07 15:26 ` Marc Khouzam
2013-01-08 17:54 ` Manlio Perillo
2013-01-08 18:05 ` John Keeping
2013-01-08 18:28 ` Manlio Perillo
2013-01-06 18:00 ` Manlio Perillo [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=50E9BBB5.3000707@gmail.com \
--to=manlio.perillo@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=marc.khouzam@ericsson.com \
--cc=szeder@ira.uka.de \
/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).