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: Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: VC menu ?
Date: Mon, 10 Jul 2017 07:59:39 +0900	[thread overview]
Message-ID: <90D1C755-C33D-4561-A0C1-F959E4CA1FBA@gmail.com> (raw)
In-Reply-To: <83o9svl884.fsf@gnu.org>


> On Jul 8, 2017, at 16:04, Eli Zaretskii <eliz@gnu.org> wrote:
> 
> I'm actually unconvinced VC warrants its own top-level menu item.
> AFAIR, it's in "Tools" in every IDE I ever saw, so Emacs is not the
> odd one out here.

I don't write prose in other IDEs, I don't do most of the things I do in other IDEs, or simple text editors for that matter. Besides, most "writing environment" don't have strong version control commands at all and you have to use the external commands to access them (macOS provides very simple vc on a file basis where you can choose to "go back in time", but that works only with some applications).

In the Magit thread you just hinted how vc commands were important. I don't think I'll ever need Magit for anything I need to do here (and I found John Wiegley's bottom-up introduction to be the best thing I ever read about git) and having a visual reminder of things I can do readily available is very important to me as a non-expert user of git/vcs/emacs, etc.

>  Also, why should that be more important than, say,
> "Compile" or "Shell command" or "Compare"?

"Compile" is a single command.
"Shell command" too is a single command.
There are no top menu slots for single commands at the moment, so they don't compare.

I can't say anything about "Compare".

>  That this particular
> community is a heavy user of some VCS doesn't yet mean we should skew
> Emacs to our specific needs, especially since most of us hardly ever
> use the menus anyway.

I think you may be missing the point. Version controlling is not something that is useful only to (expert) code writers. It is useful to (and really should be used for) any kind of writing, and visual aids are especially useful to beginners and non-(or casual) code writer.

For me, the VC menu would rather compare to the Buffer menu. It is equally useful because they are both visual aids for concepts that the beginner is not familiar with and after a while they can be ignored when the user has practiced the commands enough.

I guess it is just a configuration away to move VC around, but I'd rather have it at the top by default (and move it some place else later eventually, when I know how to configure the thing, ie. when I've become an "expert").

Now, if you tell me how to move VC to the top, I'll do that for my machine and will stop arguing :)

Jean-Christophe


  reply	other threads:[~2017-07-09 22:59 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
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 [this message]
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=90D1C755-C33D-4561-A0C1-F959E4CA1FBA@gmail.com \
    --to=jean.christophe.helary@gmail.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 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.