From: Tom Tromey <tom@tromey.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Tom Tromey <tom@tromey.com>, 25710@debbugs.gnu.org
Subject: bug#25710: Acknowledgement (25.1.91; vc-retrieve-tag does not offer branch namd completion)
Date: Tue, 14 Feb 2017 21:35:33 -0700 [thread overview]
Message-ID: <87wpcsxe96.fsf@tromey.com> (raw)
In-Reply-To: <93d9799f-955c-0451-55a0-3595ad26dc96@yandex.ru> (Dmitry Gutov's message of "Wed, 15 Feb 2017 01:31:05 +0200")
>>>>> "Dmitry" == Dmitry Gutov <dgutov@yandex.ru> writes:
>> Another idea would be to add a defcustom for this.
Dmitry> I don't imagine having tags in there would really hurt, even if we
Dmitry> don't pick them. IME tags usually follow a particular naming
Dmitry> convention, so they won't interfere with completion.
Emacs itself has 144 tags, while I have about 16 branches.
So for me at least, for this project, that's 90% clutter and 10% things
I might actually want to complete.
For my gdb checkout I have 32 branches and there are 636 tags, so the
ratio is even worse there -- about 5% useful things.
Tom
next prev parent reply other threads:[~2017-02-15 4:35 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
2017-02-15 4:35 ` Tom Tromey [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wpcsxe96.fsf@tromey.com \
--to=tom@tromey.com \
--cc=25710@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
/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.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).