all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: emacs-devel@gnu.org
Subject: Re: VC menu ?
Date: Thu, 6 Jul 2017 23:20:11 +0900	[thread overview]
Message-ID: <B81049B4-F4BB-46DC-A41F-9798B987F7A3@gmail.com> (raw)
In-Reply-To: <87y3s1ll4o.fsf@lifelogs.com>


> On Jul 6, 2017, at 23:01, Ted Zlatanov <tzz@lifelogs.com> wrote:
> 
> 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. We should not expect users to be diligent readers[1].

Indeed. My original question was a git question and John replied with a vc answer, which was of course the best possible answer but I had git in mind and would not have thought of checking for vc features (especially since it has been repeated here that native git support in emacs was not complete, or something like that).

So it is not really an issue that features are discoverable or not, or documented or not, it is about knowing what you are looking for in the first place. If the VC menu had been right there, I would have probably tested "Compare with base version" or "Show other version" and would have *discovered* that feature, and then would have I checked the manual to see what it actually does and what the other vc functions do, but only after seeing that VC functions work good enough for git issues.

Jean-Christophe 

> Ted
> 
> [1] as previously posted:
> 
> Rule #1 of writing manuals: They Won't Read It. 

No, it's "They don't know where to start, and it's 643 pages, so it's always for when one has the time, which is not often."


  reply	other threads:[~2017-07-06 14:20 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 [this message]
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=B81049B4-F4BB-46DC-A41F-9798B987F7A3@gmail.com \
    --to=jean.christophe.helary@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=tzz@lifelogs.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.