From: Homeros Misasa <homeros.misasa@gmail.com>
To: Jean-Christophe Helary <jean.christophe.helary@gmail.com>,
emacs-devel@gnu.org
Subject: Re: VC menu ?
Date: Fri, 7 Jul 2017 13:29:20 +0900 [thread overview]
Message-ID: <CAGjTQLEcfU44a24Uu75w=t4N1yUeFEqpro8Wj3_KO=c0qy1tWg@mail.gmail.com> (raw)
In-Reply-To: <AF7EF472-9B32-450E-9DD0-2B546AD01901@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1825 bytes --]
How about to organize popup-menu? Popup-menu does not concern width. I
list my
special citizen (VC, iMenu, Buffer, Frame, Bookmark, and Recenf) in
popup-menu
via right click. Problem is, more work, members are getting closer to menu
bar.
On Fri, Jul 7, 2017 at 11:26 AM, Jean-Christophe Helary <
jean.christophe.helary@gmail.com> wrote:
>
> > On Jul 7, 2017, at 9:50, Mark Oteiza <mvoteiza@udel.edu> wrote:
> >
> >
> > Ted Zlatanov <tzz@lifelogs.com> writes:
> >> On Thu, 06 Jul 2017 07:27:12 -0400 Mark Oteiza <mvoteiza@udel.edu>
> wrote:
> >> MO> Sarcasm aside, if you had ever flipped through the Emacs manual or
> >> MO> scrolled through a list of keybindings, you would have been aware
> of VC.
> >>
> >> I think menu-driven UI discovery is fun and an essential part of the GUI
> >> experience.
> >
> > I agree. It's but one of many useful self-documenting facilities in
> > Emacs. Unfortunately the original poster thinks the others are silly and
> > that the menu should spoon feed.
>
> Not all the "others". I think your sarcasm is not smart and not relevant
> to the discussion, I also think (and I wrote) that it *is* silly to
> consider equivalent the VC menu and the Games and some other menus in the
> context of a development text editor where version control is a core
> feature. I also consider not useful the a posteriori exemples of
> "discoverability" that pop up every time there is a question similar to the
> one I asked. Discoverability should not be confused with exploration.
>
> I do understand Eli's considerations about screen real estate though, even
> if I think with Ted and Oscar that VC should be considered a special
> citizen of the top menu. Now, if you have anything of interest to add to
> the discussion please do, otherwise I don't see much point going on.
>
> Jean-Christophe
>
[-- Attachment #2: Type: text/html, Size: 2536 bytes --]
next prev parent reply other threads:[~2017-07-07 4:29 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
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 [this message]
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='CAGjTQLEcfU44a24Uu75w=t4N1yUeFEqpro8Wj3_KO=c0qy1tWg@mail.gmail.com' \
--to=homeros.misasa@gmail.com \
--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 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.