From: Kaushal Modi <kaushal.modi@gmail.com>
To: Mark Oteiza <mvoteiza@udel.edu>,
Jean-Christophe Helary <jean.christophe.helary@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: VC menu ?
Date: Thu, 06 Jul 2017 12:07:03 +0000 [thread overview]
Message-ID: <CAFyQvY0nkU3DZL6V0C4Wyg_OgjmxJJtw1BBdqWu+zkeip_Eegw@mail.gmail.com> (raw)
In-Reply-To: <878tk1erfz.fsf@holos>
[-- Attachment #1: Type: text/plain, Size: 891 bytes --]
On Thu, Jul 6, 2017, 7:27 AM Mark Oteiza <mvoteiza@udel.edu> wrote:
>
> 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,
:)
The menu (including the nested menus) is just a tip of the iceberg. You
cannot possibly fit everything in menus.
You might find it useful to learn other command discovery tools like
apropos or completion systems like Ido and Ivy/Counsel (Elpa) that show you
commands that match your minibuffer input interactively. For instance,
searching for "vc-" shows me all the commands containing that string when
using Ivy/Counsel.
if
you had ever flipped through the Emacs manual or
> scrolled through a list of keybindings, you would have been aware of VC.
--
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 1754 bytes --]
next prev parent reply other threads:[~2017-07-06 12:07 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
2017-07-06 12:07 ` Kaushal Modi [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFyQvY0nkU3DZL6V0C4Wyg_OgjmxJJtw1BBdqWu+zkeip_Eegw@mail.gmail.com \
--to=kaushal.modi@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jean.christophe.helary@gmail.com \
--cc=mvoteiza@udel.edu \
/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.