unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Angelo Graziosi <angelo.graziosi@alice.it>,
	Emacs developers <emacs-devel@gnu.org>
Subject: RE: Visit New File menu item
Date: Sun, 13 Mar 2016 17:11:32 -0700 (PDT)	[thread overview]
Message-ID: <70ece5e6-c87f-4cc6-af91-10433a70d374@default> (raw)
In-Reply-To: <56E5F9C6.40305@alice.it>

> > Also, such changes should be discussed more thoroughly, waiting for
> > interested parties to chime in.  E.g., one problem with "New File" is
> > that we don't actually enforce the "new" part -- you can visit an
> > existing file via that menu item.  Not sure how important this nit is,
> > but OTOH that single word "Visit" is also hardly so very important
> > that we should rush making the change overnight.
> 
> Well said!
> 
> My opinion is that "New File" is wrong if linked to the sequence "C-x C-f".
> 
> Usually, I use "C-x C-f" both for loading ("visiting") an existing file
> in Emacs both to create a new file (not existing!).
> 
> Notice that other applications which have "New File" mean really a *new*
> (i.e. creating) file. Usually they have "C-N" for "New File" and "C-O"
> for "Open File". So using "New File" in Emacs seems misleading, unless
> you use a different key sequence for New/Open File.
> 
> Really I would remove the "Open File" item and would leave "Visit File"
> (without New), with the obvious key sequence "C-x C-f".
> 
> Why don't you like "Visit"? Why you want to follow others giving up the
> original tradition of Emacs?
> 
> Anyway this is only my opinion.

IIRC, all of this was hashed over in the older thread that I
mentioned could usefully serve as a starting point for a new
discussion (and it other threads before that one, IIRC).

I believe that I recall each of the things that you and Eli
have said, as well as everything that others have said so
far, already having been said before.

We should try to add to the previous discussion or move beyond
it, not just repeat it.

That said, I am glad that you have said what you did.  I just
wish that folks would take a look at previous discussions of
this - especially those who would like to propose a change.
So far, the proposed changes are not new, and the reasons
given for them are not new.



  reply	other threads:[~2016-03-14  0:11 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-13 23:37 Visit New File menu item Angelo Graziosi
2016-03-14  0:11 ` Drew Adams [this message]
2016-03-14  3:37 ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2016-03-11 16:58 Phillip Lord
2016-03-11 17:02 ` Joost Kremers
2016-03-11 21:30   ` John Wiegley
2016-03-11 21:36     ` Clément Pit--Claudel
2016-03-11 21:50     ` Drew Adams
2016-03-11 22:18       ` Phillip Lord
2016-03-11 22:16     ` Phillip Lord
2016-03-11 22:22       ` Mathias Dahl
2016-03-12  6:59       ` Yuri Khan
2016-03-12 19:26     ` Richard Stallman
2016-03-12 21:23       ` John Wiegley
2016-03-12 21:37         ` Phillip Lord
2016-03-12 21:41           ` John Wiegley
2016-03-12 23:35             ` Phillip Lord
2016-03-13  3:42             ` Eli Zaretskii
2016-03-13  3:56               ` John Wiegley
2016-03-13  4:00                 ` John Wiegley
2016-03-13 16:03                   ` Eli Zaretskii
2016-03-13 17:02                     ` John Wiegley
2016-03-13 19:56                       ` Phillip Lord
2016-03-13 20:23                         ` Eli Zaretskii
2016-03-13 20:38                         ` Nicolas Semrau
2016-03-13  3:43           ` Eli Zaretskii
2016-03-11 22:22 ` Nicolas Semrau

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=70ece5e6-c87f-4cc6-af91-10433a70d374@default \
    --to=drew.adams@oracle.com \
    --cc=angelo.graziosi@alice.it \
    --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).