On 2016-02-19 at 22:13, Chris Bannister wrote:
> On Wed, Feb 17, 2016 at 10:14:06AM +0100, Nicolas George wrote:
>
>> Le nonidi 29 pluviôse, an CCXXIV, to...@tuxteam.de a écrit :
>>
>>> It can be creepily smart, like knowing the branches in your
>>> project when you do git checkout bla or things
On Wed, Feb 17, 2016 at 10:14:06AM +0100, Nicolas George wrote:
> Le nonidi 29 pluviôse, an CCXXIV, to...@tuxteam.de a écrit :
> > It can be creepily smart, like knowing the branches in your project
> > when you do git checkout bla or things like that. Not bad.
>
> You mean what zsh already did in
On 2016-02-19 at 13:28, Jean-Baptiste Thomas wrote:
>> I wouldn't want to get by without tab completion either, but
>> programmable completion as I've seen it implemented in packages
>> provided by Debian seems to break some behaviors in the built-in
>> tab completion on which I had come to rely,
> I wouldn't want to get by without tab completion either, but
> programmable completion as I've seen it implemented in packages provided
> by Debian seems to break some behaviors in the built-in tab completion
> on which I had come to rely, so I always turn it off on my machines.
By "turning off"
On 2016-02-18, The Wanderer wrote:
>
> I'm not sure I understand. How is this different from basic tab
> completion, as opposed to the programmable completion which is provided
> via the bash-completion package and is being discussed in this thread?
>
> I wouldn't want to get by without tab comple
On 2016-02-17 at 12:43, Lisi Reisz wrote:
> On Wednesday 17 February 2016 16:54:15 John L. Ries wrote:
>
>>> Seriously, when does bash-completion actually help someone on
>>> the command line? The only time I notice it is when a pattern is
>>> buggy and doesn't let me complete a filename even whe
(435)867-8885 |
> --|
>
> On Wednesday 2016-02-17 01:57, Anders Andersson wrote:
> >Date: Wed, 17 Feb 2016 01:57:30
> >From: Anders Andersson
> >To: Debian users mailing list
> >Subject: Re: bash-completion, tab and ambiguous globs
&
Wednesday 2016-02-17 01:57, Anders Andersson wrote:
Date: Wed, 17 Feb 2016 01:57:30
From: Anders Andersson
To: Debian users mailing list
Subject: Re: bash-completion, tab and ambiguous globs
On Tue, Feb 16, 2016 at 11:15 AM, Jean-Baptiste Thomas
wrote:
In bash, typing, say, "ls x*y" t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Feb 17, 2016 at 10:14:06AM +0100, Nicolas George wrote:
> Le nonidi 29 pluviôse, an CCXXIV, to...@tuxteam.de a écrit :
> > It can be creepily smart, like knowing the branches in your project
> > when you do git checkout bla or things like that.
Le nonidi 29 pluviôse, an CCXXIV, to...@tuxteam.de a écrit :
> It can be creepily smart, like knowing the branches in your project
> when you do git checkout bla or things like that. Not bad.
You mean what zsh already did in its default distribution fifteen years ago?
And, of course, without break
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Feb 17, 2016 at 09:57:30AM +0100, Anders Andersson wrote:
> On Tue, Feb 16, 2016 at 11:15 AM, Jean-Baptiste Thomas
> wrote:
> > In bash, typing, say, "ls x*y" then tab lists all the possible
> > expansions of "x*y" on the next line, then print
On Tue, Feb 16, 2016 at 11:15 AM, Jean-Baptiste Thomas
wrote:
> In bash, typing, say, "ls x*y" then tab lists all the possible
> expansions of "x*y" on the next line, then prints the command
> line anew with "x*y" replaced by longest common stem.
>
> With bash-completion installed, "x*y" is summar
In bash, typing, say, "ls x*y" then tab lists all the possible
expansions of "x*y" on the next line, then prints the command
line anew with "x*y" replaced by longest common stem.
With bash-completion installed, "x*y" is summarily replaced by
its first match.
Is there any way to restore the normal
13 matches
Mail list logo
