From: Sean Whitton <spwhitton@spwhitton.name>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org, 55257@debbugs.gnu.org,
Robert Pluim <rpluim@gmail.com>, Eli Zaretskii <eliz@gnu.org>
Subject: Re: master f2d2fe6fc8: server-execute: Initialize the *scratch* buffer
Date: Mon, 09 May 2022 18:49:02 -0700 [thread overview]
Message-ID: <87ilqerwc1.fsf@athena.silentflame.com> (raw)
In-Reply-To: <jwvr152prjh.fsf-monnier+emacs@gnu.org>
Hello,
On Mon 09 May 2022 at 02:11pm -04, Stefan Monnier wrote:
> I know you didn't like my `scratch-buffer--create` suggestion because of
> the double dash, but I think at least "scratch" would be very welcome in it.
I've done s/initial/scratch/ which is better because this function
always uses *scratch* rather than, say, looking at initial-buffer-choice.
> Now that I look at it again, it occurs to me that maybe we should do
> something like:
>
> (defun scratch-buffer (&optional display)
> "Create the \*scratch\* buffer.
> If the buffer doesn't exist, create it first.
> If DISPLAY (or when used interactively), switch to it."
> (interactive (list t))
> (let ((buf (get-buffer "*scratch*")))
> (unless buf
> ;; Don't touch the buffer contents or mode unless we know that
> ;; we just created it.
> (with-current-buffer (setq buf (get-buffer-create "*scratch*"))
> (when initial-scratch-message
> (insert (substitute-command-keys initial-scratch-message))
> (set-buffer-modified-p nil))
> (funcall initial-major-mode)))
> (when display (pop-to-buffer-same-window buf))
> buf))
>
> i.e. combine the new function with the existing command, so we don't
> need to come up with a new name.
Nice idea, but I'd argue for keeping them separate. I find it more
natural to distinguish functions called for their return values and
commands.
--
Sean Whitton
prev parent reply other threads:[~2022-05-10 1:49 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <165162665935.26821.8964921720746152690@vcs2.savannah.gnu.org>
[not found] ` <20220504011059.9F667C009A8@vcs2.savannah.gnu.org>
2022-05-04 2:14 ` master f2d2fe6fc8: server-execute: Initialize the *scratch* buffer Stefan Monnier
2022-05-04 5:40 ` Sean Whitton
2022-05-04 12:47 ` Stefan Monnier
2022-05-04 14:23 ` Sean Whitton
2022-05-04 14:34 ` Robert Pluim
2022-05-04 14:46 ` Sean Whitton
2022-05-04 14:56 ` Robert Pluim
2022-05-04 14:42 ` Stefan Monnier
2022-05-04 15:41 ` Sean Whitton
2022-05-04 16:26 ` Stefan Monnier
2022-05-05 22:07 ` Sean Whitton
2022-05-05 22:13 ` Sean Whitton
2022-05-06 11:34 ` Stefan Monnier
2022-05-06 19:20 ` Sean Whitton
2022-05-06 19:24 ` Lars Ingebrigtsen
2022-05-06 5:40 ` Eli Zaretskii
2022-05-06 19:26 ` Sean Whitton
2022-05-07 5:30 ` Eli Zaretskii
2022-05-07 13:51 ` Stefan Monnier
2022-05-07 14:12 ` Eli Zaretskii
2022-05-07 16:29 ` Sean Whitton
2022-05-07 16:41 ` Eli Zaretskii
2022-05-07 17:02 ` Sean Whitton
2022-05-06 7:41 ` Juri Linkov
2022-05-06 19:28 ` Sean Whitton
2022-05-08 0:27 ` bug#55257: " Sean Whitton
2022-05-09 18:11 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-09 18:11 ` Stefan Monnier
2022-05-10 1:49 ` bug#55257: " Sean Whitton
2022-05-10 1:49 ` Sean Whitton [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ilqerwc1.fsf@athena.silentflame.com \
--to=spwhitton@spwhitton.name \
--cc=55257@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rpluim@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.
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.