From: Dmitry Gutov <dgutov@yandex.ru>
To: Tom Tromey <tom@tromey.com>
Cc: 25710@debbugs.gnu.org
Subject: bug#25710: Acknowledgement (25.1.91; vc-retrieve-tag does not offer branch namd completion)
Date: Wed, 15 Feb 2017 01:31:05 +0200 [thread overview]
Message-ID: <93d9799f-955c-0451-55a0-3595ad26dc96@yandex.ru> (raw)
In-Reply-To: <87inoczdun.fsf@tromey.com>
On 14.02.2017 23:01, Tom Tromey wrote:
> Dmitry> Should we call it list-tags, similarly to the name of the command?
>
> This bit is fine by me.
It would be a bit pointless without the second part. If we decide
against it, list-branches is probably the better choice.
So I wonder what other people think.
> Dmitry> And return tags together with branches in the Git implementation.
>
> I am not so sure about this. I've never (literally never) wanted to
> check out a tag with Git. I do sometimes check out a specific revision.
Me neither, but... people do use tags to mark specific, *important*
revisions. And supposedly check them out sometimes (maybe to see the
exact code the "current production" version has?).
I do check out specific revisions sometimes too, but providing
completion for that is fairly impossible. Completing tags seems like the
next best thing.
> But... the UI doesn't prohibit this, it just only offers branches for
> completion. I tend to think that's the most useful.
Branches are most useful indeed.
> Another idea would be to add a defcustom for this.
I don't imagine having tags in there would really hurt, even if we don't
pick them. IME tags usually follow a particular naming convention, so
they won't interfere with completion.
next prev parent reply other threads:[~2017-02-14 23:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 23:11 bug#25710: 25.1.91; vc-retrieve-tag does not offer branch namd completion Tom Tromey
[not found] ` <handler.25710.B.148702752518881.ack@debbugs.gnu.org>
2017-02-14 3:13 ` bug#25710: Acknowledgement (25.1.91; vc-retrieve-tag does not offer branch namd completion) Tom Tromey
2017-02-14 10:24 ` Dmitry Gutov
[not found] ` <87inoczdun.fsf@tromey.com>
2017-02-14 23:31 ` Dmitry Gutov [this message]
2017-02-15 4:35 ` Tom Tromey
2017-02-17 1:26 ` Dmitry Gutov
2017-02-17 4:09 ` Tom Tromey
2017-02-19 22:13 ` Dmitry Gutov
2017-03-04 18:06 ` Tom Tromey
2017-03-06 11:42 ` Dmitry Gutov
2020-08-11 7:56 ` Stefan Kangas
2020-08-11 19:44 ` Dmitry Gutov
2020-08-19 11:39 ` Lars Ingebrigtsen
2017-02-16 3:38 ` bug#25710: Branch completion on vc-retrive-tag Artem Malyshev
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=93d9799f-955c-0451-55a0-3595ad26dc96@yandex.ru \
--to=dgutov@yandex.ru \
--cc=25710@debbugs.gnu.org \
--cc=tom@tromey.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.