From: Cornelius Weig
Command completion only recognizes a subset of the available options for
the various git commands. The set of recognized options needs to balance
between having all useful options and to not clutter the terminal.
This commit adds all long-options that are mentioned in the ma
On 02/02/2017 03:00 AM, SZEDER Gábor wrote:
>> Personally, I agree with you that
>>> Adding more long options that git commands learn along the way is
>>> always an improvement.
>> However, people may start complaining that their terminal becomes too
>> cluttered when doing a double-Tab. In my cove
On Wed, Feb 1, 2017 at 5:49 PM, Cornelius Weig
wrote:
> Hi Gabor,
>
> thanks for taking a look at these commits.
>
> On 01/31/2017 11:17 PM, SZEDER Gábor wrote:
>> On Fri, Jan 27, 2017 at 10:17 PM, wrote:
>>> From: Cornelius Weig
>>>
>>> Recognize several new long-options for bash completion i
Hi Gabor,
thanks for taking a look at these commits.
On 01/31/2017 11:17 PM, SZEDER Gábor wrote:
> On Fri, Jan 27, 2017 at 10:17 PM, wrote:
>> From: Cornelius Weig
>>
>> Recognize several new long-options for bash completion in the following
>> commands:
>
> Adding more long options that git
On Fri, Jan 27, 2017 at 10:17 PM, wrote:
> From: Cornelius Weig
>
> Recognize several new long-options for bash completion in the following
> commands:
Adding more long options that git commands learn along the way is
always an improvement. However, seeing "_several_ new long options"
(or "som
From: Cornelius Weig
Recognize several new long-options for bash completion in the following
commands:
- apply: --recount --directory=
- archive: --output
- branch: --column --no-column --sort= --points-at
- clone: --no-single-branch --shallow-submodules
- commit: --patch --short --date --a
6 matches
Mail list logo
