unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: VC menu ?
Date: Fri, 07 Jul 2017 08:31:25 -0400	[thread overview]
Message-ID: <87r2xsjun6.fsf@lifelogs.com> (raw)
In-Reply-To: 87d19d6pf3.fsf@holos

On Thu, 06 Jul 2017 20:50:24 -0400 Mark Oteiza <mvoteiza@udel.edu> wrote: 

MO> 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.

MO> I agree.  It's but one of many useful self-documenting facilities in
MO> Emacs.  Unfortunately the original poster thinks the others are silly and
MO> that the menu should spoon feed.

That's not the impression I got, and would prefer to talk about the
proposal rather than people's thoughts. Also, I think many of our
discussions here tend to see Emacs users as experts with 10+ years of
experience (survivor bias).

Anyhow, my position is that the VC menu is as essential today as the
Recent and Buffers menus and should be at the top.

As a compromise, maybe we can show VC by default, but also have an
option in the VC menu to "Don't show VC menu at top, put it under
Tools." That way annoyed users can move it out easily.

Ted




  parent reply	other threads:[~2017-07-07 12:31 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
2017-07-07 12:31       ` Ted Zlatanov [this message]
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=87r2xsjun6.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=emacs-devel@gnu.org \
    /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).