zsh-workers
 help / color / mirror / code / Atom feed
From: Daniel Hahler <genml+zsh-workers@thequod.de>
To: zsh-workers@zsh.org
Subject: Re: _git commit object name completion
Date: Tue, 19 May 2015 09:13:52 +0200	[thread overview]
Message-ID: <555AE2B0.8010202@thequod.de> (raw)
In-Reply-To: <150518214003.ZM6919@torch.brasslantern.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 19.05.2015 06:40, Bart Schaefer wrote:
> On May 19,  1:38am, Daniel Shahaf wrote:
> }
> } % git checkout f<TAB><TAB><TAB>
> } f82ecfc  -- [f82ecfc] m (3 minutes ago)
> } 
> } I expected 'f82ecfc' to be added to the command-line immediately, as
> } it's the only completion.  Instead, I only get the list of possible
> } completions and the buffer remains unmodified, no matter how many times
> } I press <TAB>.
> 
> I'd make a small wager that this is another effect of workers/35101.  If
> you revert 454f079852deb0c704870c7d5a462485f1e65bbf, do you get the result
> you expect?
> 

Yes, 454f079 also triggered that issue, and it should be fixed by now.

Basically it promoted __git_recent_commits to be used by default, while it was
previously only used for --fixup and --squash.


Regards,
Daniel.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iD8DBQFVWuKwfAK/hT/mPgARArbfAKCTOoPr5ahHhyJopuVRZ7qcVtR4IwCgjebt
AGFXeoX64dJ4a/kks0NrC3Y=
=MRpi
-----END PGP SIGNATURE-----


  reply	other threads:[~2015-05-19  7:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19  1:38 Daniel Shahaf
2015-05-19  4:40 ` Bart Schaefer
2015-05-19  7:13   ` Daniel Hahler [this message]
2015-05-19  8:27 ` Daniel Hahler
2015-06-02 10:18   ` Daniel Shahaf
2015-06-06 19:27     ` Bart Schaefer
2015-06-07 22:38       ` Daniel Hahler
2015-06-11 11:30         ` ChangeLog generation (was: Re: _git commit object name completion) Daniel Shahaf

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=555AE2B0.8010202@thequod.de \
    --to=genml+zsh-workers@thequod.de \
    --cc=zsh-workers@zsh.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).