All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>,
	"SZEDER Gábor" <szeder.dev@gmail.com>
Cc: Felipe Contreras <felipe.contreras@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH try2 0/4] completion: bash: a bunch of fixes
Date: Wed, 23 Dec 2020 18:21:02 -0600	[thread overview]
Message-ID: <5fe3deee26d38_7855a208ed@natae.notmuch> (raw)
In-Reply-To: <xmqq1rfg8e3j.fsf@gitster.c.googlers.com>

Junio C Hamano wrote:
> SZEDER Gábor <szeder.dev@gmail.com> writes:
> 
> > On Wed, Dec 23, 2020 at 07:38:12AM -0600, Felipe Contreras wrote:
> > ...
> >> I see 5 courses of action:
> >> 
> >>  1. Drop the offending patch: this is wrong because the bug is still
> >>     there, we are just not checking for it.
> >>  2. Add a BASH prereq just for that test, or test_expect_unstable (we
> >>     would need to add extra code for both of those).
> >>  3. Add the fix, but not the test for the fix.
> >
> > I'm for this option 3: this patch does fix a bug for users of Bash
> > v4.0 or later, while it doesn't change the behavior with v3.2 or
> > earlier (and with zsh, if I understand correctly).  OTOH, the test
> > doesn't seem to be all that useful: while it does demonstrate the
> > issue, it checks only one of those callsites that passed the wrong
> > suffix, and, more importantly, it doesn't protect us from adding
> > another callsites with similarly wrong suffex in the future.
> 
> Yeah, I might have preferred, if we didn't read your "doesn't seem
> to be all that useful", to keep the test with prereq on bash 4, but
> I think either way is fine.

Even if we add a prereq on BASH4, he is right that the test wouldn't be
all that useful, because it's checking only for one conditional branch,
and the function has quite a few, from the top of my head there are about
10.

A more useuful test would at least add one check for each one of the
cases. It still would be dependent on the current implementation, but
would be more useful.

I can add that in a future patch series, once the other issues are
resolved.

Cheers.

-- 
Felipe Contreras

      reply	other threads:[~2020-12-24  0:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-19 14:06 [PATCH try2 0/4] completion: bash: a bunch of fixes Felipe Contreras
2020-12-19 14:06 ` [PATCH try2 1/4] completion: bash: fix prefix detection in branch.* Felipe Contreras
2020-12-19 14:06 ` [PATCH try2 2/4] completion: bash: add correct suffix in variables Felipe Contreras
2020-12-19 14:06 ` [PATCH try2 3/4] completion: bash: fix for suboptions with value Felipe Contreras
2020-12-19 14:06 ` [PATCH try2 4/4] completion: bash: fix for multiple dash commands Felipe Contreras
2020-12-23  9:14 ` [PATCH try2 0/4] completion: bash: a bunch of fixes Junio C Hamano
2020-12-23 13:38   ` Felipe Contreras
2020-12-23 14:19     ` SZEDER Gábor
2020-12-23 14:31       ` Felipe Contreras
2020-12-23 20:25       ` Junio C Hamano
2020-12-24  0:21         ` Felipe Contreras [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=5fe3deee26d38_7855a208ed@natae.notmuch \
    --to=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=szeder.dev@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.