public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed

From: Manlio Perillo <manlio.perillo@gmail•com>
To: John Keeping <john@keeping•me.uk>
Cc: Marc Khouzam <marc.khouzam@ericsson•com>,
	Junio C Hamano <gitster@pobox•com>,
	"git@vger•kernel.org" <git@vger•kernel.org>,
	"szeder@ira•uka.de" <szeder@ira•uka.de>,
	"felipe.contreras@gmail•com" <felipe.contreras@gmail•com>
Subject: Re: [PATCH v4] git-completion.bash: add support for path completion
Date: Tue, 08 Jan 2013 19:28:40 +0100	[thread overview]
Message-ID: <50EC6558.6080608@gmail.com> (raw)
In-Reply-To: <20130108180518.GO6440@serenity.lan>

-----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 perform any
>> filename-specific processing".
>>
>> Unfortunately this option must be passed to the complete builtin
>> command, and we can not do this, since the comspec not always contains
>> filenames.
> 
> You should also be able to pass it to 'compopt' during completion in
> order to change the behaviour for only the current completion.
> 

Thanks, compopt is what I wanted.

I was reading an old Bash manual (for Bash 3.1), and compopt is only
available starting from Bash 4.0.

I will do some test, being careful to not break the code for Bash < 4.0
and the other supported shells.



Regards  Manlio
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlDsZVgACgkQscQJ24LbaUQlAACdGbhOuGICCYFwkRTPJla+3JGT
EcQAoINEGvdwtOz1QFbAA4FqoI3c7VSa
=5Oqw
-----END PGP SIGNATURE-----

next prev parent reply	other threads:[~2013-01-08 18:29 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 [this message]
2013-01-06 18:00       ` Manlio Perillo

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=50EC6558.6080608@gmail.com \
    --to=manlio.perillo@gmail$(echo .)com \
    --cc=felipe.contreras@gmail$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=gitster@pobox$(echo .)com \
    --cc=john@keeping$(echo .)me.uk \
    --cc=marc.khouzam@ericsson$(echo .)com \
    --cc=szeder@ira$(echo .)uka.de \
    /path/to/YOUR_REPLY

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox