From: Robert Pluim <rpluim@gmail.com>
To: Sean Whitton <spwhitton@spwhitton.name>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: master f2d2fe6fc8: server-execute: Initialize the *scratch* buffer
Date: Wed, 04 May 2022 16:56:14 +0200 [thread overview]
Message-ID: <87h76573e9.fsf@gmail.com> (raw)
In-Reply-To: <87v8ule4p8.fsf@athena.silentflame.com> (Sean Whitton's message of "Wed, 04 May 2022 07:46:11 -0700")
>>>>> On Wed, 04 May 2022 07:46:11 -0700, Sean Whitton <spwhitton@spwhitton.name> said:
Sean> Hello,
Sean> On Wed 04 May 2022 at 04:34pm +02, Robert Pluim wrote:
>>>>>>> On Wed, 04 May 2022 07:23:32 -0700, Sean Whitton <spwhitton@spwhitton.name> said:
Sean> In order to factor it out of the C as well I need to define it in C with
Sean> the DEFUN macro, right? Otherwise each C callsite would have to use
Sean> Ffuncall, which doesn't seem right.
>>
>> You'll need to weigh the cost of implementing it in C against the need
>> to use Ffuncall. For something like this thatʼs not going to be called
>> a lot Iʼd be strongly tempted to choose the easiest implementation
>> language, ie elisp.
Sean> The C thing is in other-buffer and other-buffer-safely -- I think those
Sean> get called quite often?
Probably. And it looks like itʼs only 6 lines or so of code, so maybe
you can put those in a DEFUN.
Robert
--
next prev parent reply other threads:[~2022-05-04 14:56 UTC|newest]
Thread overview: 28+ 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 [this message]
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
2022-05-10 1:49 ` Sean Whitton
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=87h76573e9.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=spwhitton@spwhitton.name \
/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).