From: Stefan Vollmar <vollmar@nf.mpg.de>
To: Drew Adams <drew.adams@oracle.com>
Cc: help-gnu-emacs@gnu.org, Kevin Rodgers <kevin.d.rodgers@gmail.com>
Subject: Re: Emacs ignores modified state of "untitled" buffer
Date: Fri, 28 May 2010 23:21:01 +0200 [thread overview]
Message-ID: <497A0D9B-8342-4222-BC60-EA77B3DCF95A@nf.mpg.de> (raw)
In-Reply-To: <95F4903F7E4B48DAA566AF099AB10B11@us.oracle.com>
[-- Attachment #1: Type: text/plain, Size: 1741 bytes --]
Dear Drew,
On 28.05.2010, at 19:18, Drew Adams wrote:
[...]
> I would propose (and have proposed ;-)) simply `New File' as the menu item. It
> is common nowadays to have a menu item `New' for creation when the object to be
> created is clear, and `New Foo' to make clear that it creates a foo object. (I
> use `New File' and `New Directory' in my own code, `menu-bar+.el'.)
>
> Whether we use `Visit' or `Open' for an existing whatever is not so important.
> What is important is to clearly distinguish the case of creation (`New').
in my reply to Kevin of May 26 the modified left-mode button in the toolbar was labelled "New Document (Org)" (we used the same label in the corresponding first entry of the "File" menu). I absolutely agree that the "New" part is essential.
Kevin's code conforms (probably not a coincidence) to the Apple Human Interface Guidelines:
http://www.devworld.apple.com/mac/library/documentation/UserExperience/Conceptual/AppleHIGuidelines/XHIGMenus/XHIGMenus.html
I have had Windows users look at the Emacs version with the File New option and they said it was a significant improvement, immediately adding that, by the way, they had never heard of "visiting" a file (not surprising).
I believe that Xah Lee had these kind of changes in mind here: http://xahlee.org/emacs/modernization.html
I do not agree with everything but he has a few points, I think.
Warm regards,
Stefan
--
Dr. Stefan Vollmar, Dipl.-Phys.
Head of IT group
Max-Planck-Institut für neurologische Forschung
Gleuelerstr. 50, 50931 Köln, Germany
Tel.: +49-221-4726-213 FAX +49-221-4726-298
Tel.: +49-221-478-5713 Mobile: 0160-93874279
Email: vollmar@nf.mpg.de http://www.nf.mpg.de
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 4409 bytes --]
next prev parent reply other threads:[~2010-05-28 21:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 14:52 Emacs ignores modified state of "untitled" buffer Stefan Vollmar
2010-05-19 15:04 ` Drew Adams
2010-05-19 20:34 ` Stephen Berman
2010-05-20 12:45 ` Kevin Rodgers
2010-05-20 13:29 ` Drew Adams
2010-05-20 14:00 ` Stefan Vollmar
2010-05-21 2:00 ` Kevin Rodgers
2010-05-21 2:06 ` Lennart Borgman
2010-05-21 1:56 ` Kevin Rodgers
2010-05-21 8:03 ` Stefan Vollmar
2010-05-21 13:17 ` Kevin Rodgers
2010-05-21 13:59 ` Stefan Vollmar
2010-05-21 14:11 ` Kevin Rodgers
2010-05-21 14:30 ` Stefan Vollmar
2010-05-21 17:15 ` Lennart Borgman
2010-05-21 20:49 ` Stefan Vollmar
2010-05-21 20:56 ` Lennart Borgman
2010-05-21 14:20 ` Drew Adams
2010-05-28 14:32 ` Kevin Rodgers
2010-05-28 17:18 ` Drew Adams
2010-05-28 21:21 ` Stefan Vollmar [this message]
[not found] ` <mailman.2.1275067137.32597.help-gnu-emacs@gnu.org>
2010-05-29 1:04 ` Tim X
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=497A0D9B-8342-4222-BC60-EA77B3DCF95A@nf.mpg.de \
--to=vollmar@nf.mpg.de \
--cc=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=kevin.d.rodgers@gmail.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.
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).