unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Tassilo Horn" <tsdh@gnu.org>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: 39546@debbugs.gnu.org, larsi@gnus.org, michael.albinus@gmx.de,
	Tino Calancha <tino.calancha@gmail.com>
Subject: bug#39546: 28.0.50; Do not require subr-x at run time
Date: Mon, 10 Feb 2020 21:17:08 +0100	[thread overview]
Message-ID: <a32e591e-082e-4076-942f-6c3808f1d9d3@beta.fastmail.com> (raw)
In-Reply-To: <83mu9qb4d0.fsf@gnu.org>

Am Mo, 10. Feb 2020, um 20:59, schrieb Eli Zaretskii:
> > From: Tassilo Horn <tsdh@gnu.org>
> > Cc: Tino Calancha <tino.calancha@gmail.com>,  39546@debbugs.gnu.org,
> >   larsi@gnus.org,  michael.albinus@gmx.de
> > Date: Mon, 10 Feb 2020 20:19:05 +0100
> > 
> > I've already submitted patches to hindent (and I think to some other 3rd
> > party package providing code formatting by replacing with the output of
> > some formatting tool) using that function.
> > 
> > Anyway, if it is going to be moved, I'd to ask you to move it in
> > emacs-27 so that I can check for and fix external usages I know of
> > without having to distinguish emacs versions.
> 
> Then maybe we shouldn't move it, just for these reasons.

If we all think that replace.el is the right place and it has the benefit of being loaded at startup, then I'm all for it. The hindent PR is not yet merged anyway, and the other one was quickly accepted, so an addendum patch will be, too.

I'd like to see more usages of that function. Basically every package providing support for external formatters should use it, e.g., I'm going to submit a patch for rust-mode providing formatting using rustfmt anytime soon. So better change it now than regretting that multiple not so uncommon packages require subr-x at runtime.

Bye,
Tassilo





  reply	other threads:[~2020-02-10 20:17 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
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 [this message]
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

  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=a32e591e-082e-4076-942f-6c3808f1d9d3@beta.fastmail.com \
    --to=tsdh@gnu.org \
    --cc=39546@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.org \
    --cc=michael.albinus@gmx.de \
    --cc=tino.calancha@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 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).