unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Juri Linkov <juri@jurta.org>
Cc: Jared Finder <jfinder@crypticstudios.com>, 4100@debbugs.gnu.org
Subject: bug#4100: 23.1; Minor bugs in Emacs 23
Date: Thu, 03 Jun 2021 11:40:49 +0200	[thread overview]
Message-ID: <877djb5lr2.fsf@gnus.org> (raw)
In-Reply-To: <87ljlrjica.fsf@mail.jurta.org> (Juri Linkov's message of "Tue, 11 Aug 2009 02:57:57 +0300")

Juri Linkov <juri@jurta.org> writes:

>> Please change the "Visit New File" entry to a "New File" entry
>> defined as follows:
>> (define-key menu-bar-file-menu [new-file]
>>   '(menu-item "New File"
>>               (lambda ()
>>                 (interactive)
>>                 (switch-to-buffer (generate-new-buffer "*untitled*")))
>>               :enable (menu-bar-non-minibuffer-window-p)
>>               :help "Create a new buffer"))
>>
>> This corresponds to what just about every other editor on the planet
>> does -- prompt for a filename when the file is first SAVED.
>
> This makes sense since this new *untitled* buffer is just like the
> *scratch* buffer but you need also add (setq buffer-offer-save t)
> and (auto-save-mode 1) to *untitled* so exiting will ask a question
> about saving it to a file.

I'm not sure we want to confuse the users any further -- the normal
Emacs way here is to prompt for the file at start, and having this menu
work the opposite way wouldn't help with this.

So I'm closing this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2021-06-03  9:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <64CCCAABBBC73A44926EC2CB7E6CBF2B0FF5590746@proserpine.paragon.crypticstudios.com>
2009-08-10  2:46 ` bug#4100: 23.1; Minor bugs in Emacs 23 Jared Finder
2009-08-10 23:57   ` Juri Linkov
2021-06-03  9:40     ` Lars Ingebrigtsen [this message]

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=877djb5lr2.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=4100@debbugs.gnu.org \
    --cc=jfinder@crypticstudios.com \
    --cc=juri@jurta.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).