From: John Wiegley <jwiegley@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: joostkremers@fastmail.fm, emacs-devel@gnu.org, rms@gnu.org,
phillip.lord@russet.org.uk
Subject: Re: Visit New File menu item
Date: Sun, 13 Mar 2016 10:02:38 -0700 [thread overview]
Message-ID: <m2k2l6paz5.fsf@newartisans.com> (raw)
In-Reply-To: <83k2l6fjq0.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 13 Mar 2016 18:03:51 +0200")
[-- Attachment #1: Type: text/plain, Size: 1338 bytes --]
>>>>> Eli Zaretskii <eliz@gnu.org> writes:
> It's okay to revisit that decision, but such changes should not be done
> during a pretest, no matter how simple they look: you never know what
> baggage they could bring with them, and pretest must not change behavior,
> unless required to fix a bug.
> 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.
You make excellent points, Eli.
Phillip, I'm sorry to give you the go ahead and then turn it around, but I
can't ignore Eli's wise counsel on this point.
Can one of you please revert this for emacs-25? (I'm traveling at the moment).
After, let's discuss which menu options we might want to change and why, so
that others have more of a chance to chime in. Although there was a mini-
consensus on "New File", maybe we didn't give it enough time.
Thank you,
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 629 bytes --]
next prev parent reply other threads:[~2016-03-13 17:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 16:58 Visit New File menu item 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2016-03-13 23:37 Angelo Graziosi
2016-03-14 0:11 ` Drew Adams
2016-03-14 3:37 ` 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=m2k2l6paz5.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=johnw@gnu.org \
--cc=joostkremers@fastmail.fm \
--cc=phillip.lord@russet.org.uk \
--cc=rms@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).