all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tino Calancha <tino.calancha@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 39546@debbugs.gnu.org, larsi@gnus.org,
	Tino Calancha <tino.calancha@gmail.com>,
	michael.albinus@gmx.de, tsdh@gnu.org
Subject: bug#39546: 28.0.50; Do not require subr-x at run time
Date: Mon, 10 Feb 2020 18:26:13 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.21.2002101824100.27837@calancha-pc.dy.bbexcite.jp> (raw)
In-Reply-To: <831rr2cvci.fsf@gnu.org>



On Mon, 10 Feb 2020, Eli Zaretskii wrote:

>> In addition, it moves back replace-region-contents into subr.el: been a defun,
>> and documented in the manual, then it fits better inside subr.el.
>
> subr.el is preloaded, so doing that will enlarge the Emacs memory
> footprint.  Is that function important enough to have it preloaded?
According with its usage at Emacs source (only at json.el) I'd say
the answer to your question is: not worth to be at subr.el.





  reply	other threads:[~2020-02-10 17:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-10 13:59 bug#39546: 28.0.50; Do not require subr-x at run time Tino Calancha
2020-02-10 14:54 ` Michael Albinus
2020-02-10 17:35   ` Tino Calancha
2020-02-10 15:31 ` Eli Zaretskii
2020-02-10 17:26   ` Tino Calancha [this message]
2020-02-10 17:39     ` Eli Zaretskii
2020-02-10 19:19       ` Tassilo Horn
2020-02-10 19:59         ` Eli Zaretskii
2020-02-10 20:17           ` Tassilo Horn
2020-02-10 19:30       ` Tino Calancha
2020-02-10 19:54         ` Tassilo Horn
2020-02-10 20:34           ` Tino Calancha
2020-02-10 20:49             ` Tino Calancha
2020-02-10 21:00               ` Tino Calancha
2020-02-14 10:16                 ` Eli Zaretskii
2020-02-19 13:41                 ` Lars Ingebrigtsen
2020-08-08 14:06                   ` Lars Ingebrigtsen

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=alpine.DEB.2.21.2002101824100.27837@calancha-pc.dy.bbexcite.jp \
    --to=tino.calancha@gmail.com \
    --cc=39546@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.org \
    --cc=michael.albinus@gmx.de \
    --cc=tsdh@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 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.