unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Amin Bandali <bandali@gnu.org>
Cc: emacs-erc@gnu.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: [ELPA] New package: ERC
Date: Sun, 19 Sep 2021 16:38:31 +0200	[thread overview]
Message-ID: <875yuwpr4o.fsf@gnus.org> (raw)
In-Reply-To: <87tuih3jfq.fsf@gnu.org> (Amin Bandali's message of "Sat, 18 Sep 2021 13:03:21 -0400")

Amin Bandali <bandali@gnu.org> writes:

> 1. Making the iso8601 dependency optional; or even better, adding it
>    to GNU ELPA and adapting it to only use the new functions like
>    `string-replace' on newer Emacsen.
>
>    What do you think about this, Lars?

I don't think there's much point in using `string-replace' at all in
packages that are meant to be used in older Emacs versions -- they can
be trivially rewritten to use `replace-regexp-in-string' always.

But I'm not sure whether it makes much sense to put a bunch of the
built-in Emacs libraries in ELPA -- perhaps it does make sense for
iso8601.el (even if there's been some internal time changes for time
representation of sub-second times), but for instance:

> 2. Adding browse-url to GNU ELPA, since erc-button uses its
>    `browse-url-button-regexp', which was only added in Emacs 27.
>    We could probably adjust erc-button to fall back onto Gnus's
>    `gnus-button-url-regexp' on older Emacsen, but I think I'd
>    rather not do that.

It's just a slippery slope, as you've found out with erc.  Putting stuff
into ELPA adds a real added maintenance cost, because you can't use
modern idioms and better constructs like:

> 3. Not using `with-suppressed-warnings' (added in Emacs 27) on older
>    Emacsen and perhaps fall back on `with-no-warnings' for the single
>    use of that macro instead.

Using `with-no-warnings' is usually a disservice, because it pastes over
other potential errors other than the one you meant to inhibit.

So I'm sceptical about all of this -- is the added utility of having
these libraries in ELPA for users so big that we want to take on the
added maintenance burden?

I'm doubtful.

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



  reply	other threads:[~2021-09-19 14:38 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-18 17:03 [ELPA] New package: ERC Amin Bandali
2021-09-19 14:38 ` Lars Ingebrigtsen [this message]
2021-09-26 15:22   ` Amin Bandali
2021-09-26 19:28     ` Philip Kaludercic
2021-09-26 20:41       ` Amin Bandali
2021-09-27 10:22         ` Philip Kaludercic
2021-09-28  2:36           ` Amin Bandali
2021-09-26 20:15     ` Stefan Kangas
2021-09-26 21:03       ` Amin Bandali
2021-09-27 10:23         ` Philip Kaludercic
2021-09-29  1:26           ` Amin Bandali
2021-09-27 19:42     ` Stefan Monnier
2021-09-29  1:40       ` Amin Bandali
2021-09-29  3:30         ` Stefan Monnier
2021-09-29  4:11           ` Amin Bandali
2021-09-20 16:48 ` Stefan Monnier
2021-09-21  0:16 ` Emanuel Berg via General discussion about ERC
2021-09-21  5:31   ` Corwin Brust
2021-09-21  7:12     ` Emanuel Berg via General discussion about ERC
2021-09-21 23:56       ` Amin Bandali

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=875yuwpr4o.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=bandali@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-erc@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).