From: Mark Oteiza <mvoteiza@udel.edu>
To: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: VC menu ?
Date: Thu, 06 Jul 2017 07:27:12 -0400 [thread overview]
Message-ID: <878tk1erfz.fsf@holos> (raw)
In-Reply-To: <A7CA2A27-DB7F-4DA6-A1A6-52444532D6A9@gmail.com> (Jean-Christophe Helary's message of "Thu, 6 Jul 2017 15:51:46 +0900")
Jean-Christophe Helary <jean.christophe.helary@gmail.com> writes:
> Why is the VC menu hidden in the Tool menu when it's such an important item in an emacs workflow? Couldn't we have VC as a standard base menu?
>
> I just discovered that the command John Wiegley suggested to use in an
> answer to a recent query of mine was *right under my nose* in the
> Tools/Version Control menu. If the VC menu had been next to Tool (just
> like other mode menus are) I would have probably tried a few commands
> there before asking...
Yes, and let's further add top-level menu items for every other
important tool in Emacs workflows. That way, the menu shows every
useful thing at once, and is simultaneously cumbersome to the point of
unusability.
Sarcasm aside, if you had ever flipped through the Emacs manual or
scrolled through a list of keybindings, you would have been aware of VC.
next prev parent reply other threads:[~2017-07-06 11:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 6:51 VC menu ? Jean-Christophe Helary
2017-07-06 11:27 ` Mark Oteiza [this message]
2017-07-06 12:07 ` Kaushal Modi
2017-07-06 12:10 ` Jean-Christophe Helary
2017-07-06 12:20 ` Andreas Schwab
2017-07-06 12:25 ` Jean-Christophe Helary
2017-07-06 12:41 ` Tino Calancha
2017-07-06 13:28 ` Stephen Berman
2017-07-07 13:16 ` Tino Calancha
2017-07-06 14:01 ` Ted Zlatanov
2017-07-06 14:20 ` Jean-Christophe Helary
2017-07-07 0:50 ` Mark Oteiza
2017-07-07 2:26 ` Jean-Christophe Helary
2017-07-07 4:29 ` Homeros Misasa
2017-07-07 12:31 ` Ted Zlatanov
2017-07-07 13:22 ` Drew Adams
2017-07-07 13:33 ` Ted Zlatanov
2017-07-07 13:31 ` Tino Calancha
2017-07-06 13:54 ` Ted Zlatanov
2017-07-06 17:03 ` Óscar Fuentes
2017-07-06 14:35 ` Stefan Monnier
2017-07-06 15:09 ` Jean-Christophe Helary
2017-07-06 15:15 ` Stefan Monnier
2017-07-06 16:49 ` Ted Zlatanov
2017-07-06 15:23 ` Eli Zaretskii
2017-07-08 1:25 ` Jean-Christophe Helary
2017-07-08 7:04 ` Eli Zaretskii
2017-07-09 22:59 ` Jean-Christophe Helary
2017-07-10 16:49 ` Eli Zaretskii
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=878tk1erfz.fsf@holos \
--to=mvoteiza@udel.edu \
--cc=emacs-devel@gnu.org \
--cc=jean.christophe.helary@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.
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).