From: Philip Kaludercic <philipk@posteo.net>
To: emacs-devel@gnu.org
Subject: Re: Proposal: Forwards-Compatibility Library for Emacs
Date: Tue, 21 Sep 2021 13:05:35 +0000 [thread overview]
Message-ID: <87tuiersdc.fsf@posteo.net> (raw)
In-Reply-To: <877dfavmzw.fsf@posteo.net> (Philip Kaludercic's message of "Mon, 20 Sep 2021 23:35:47 +0000")
Philip Kaludercic <philipk@posteo.net> writes:
> ;; Is this excusable?
> ;;
> ;; ;;;; Ensure NonGNU ELPA is in `package-archives'
> ;; (eval-after-load "package"
> ;; (lambda ()
> ;; (unless (or (rassoc "https://elpa.nongnu.org/nongnu/" package-archives)
> ;; (rassoc "http://elpa.nongnu.org/nongnu/" package-archives)
> ;; (rassoc "https://elpa.nongnu.org/nongnu-devel/" package-archives)
> ;; (rassoc "http://elpa.nongnu.org/nongnu-devel/" package-archives))
> ;; (add-to-list 'package-archives '("nongnu" . "https://elpa.nongnu.org/nongnu/")))))
I also wanted to bring attention to this snippet, which if uncommented
might be a lot more controversial than the actual content of the library
itself. More generally, if a compatibility library were to be used more
widely, it would offer a possible route to update old defaults, such as
in this case, adding NonGNU ELPA to package-archives, or perhaps update
the default values of the IRC servers used by rcirc and ERC from
freenode to libera. If this could even be excused (and I get why people
could have issues with this), it would have to be used very
conservatively to not interfere with any existing configurations.
--
Philip Kaludercic
next prev parent reply other threads:[~2021-09-21 13:05 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-20 23:35 Proposal: Forwards-Compatibility Library for Emacs Philip Kaludercic
2021-09-21 0:30 ` Adam Porter
2021-09-21 4:10 ` Lars Ingebrigtsen
2021-09-21 8:28 ` Philip Kaludercic
2021-09-21 12:31 ` Stefan Monnier
2021-09-21 12:40 ` Eli Zaretskii
2021-09-21 12:50 ` Stefan Kangas
2021-09-21 13:38 ` Arthur Miller
2021-09-21 13:49 ` João Távora
2021-09-21 13:00 ` Philip Kaludercic
2021-09-21 13:12 ` Eli Zaretskii
2021-09-21 13:28 ` Philip Kaludercic
2021-09-21 13:24 ` João Távora
2021-09-21 13:29 ` Philip Kaludercic
2021-09-21 13:50 ` João Távora
2021-09-21 14:59 ` Lars Ingebrigtsen
2021-09-21 12:58 ` Philip Kaludercic
2021-09-21 13:37 ` Arthur Miller
2021-09-21 13:54 ` Philip Kaludercic
2021-09-21 14:18 ` Arthur Miller
2021-09-21 15:02 ` Lars Ingebrigtsen
2021-09-21 15:40 ` João Távora
2021-09-21 16:10 ` Philip Kaludercic
2021-09-21 16:22 ` João Távora
2021-09-21 17:22 ` Lars Ingebrigtsen
2021-09-21 17:29 ` João Távora
2021-09-21 19:24 ` Stefan Monnier
2021-09-21 21:06 ` Philip Kaludercic
2021-09-21 21:50 ` Stefan Monnier
2021-09-22 6:48 ` Philip Kaludercic
2021-09-22 17:53 ` Stefan Monnier
2021-09-22 18:54 ` Philip Kaludercic
2021-09-22 19:15 ` Stefan Monnier
2021-09-21 21:57 ` Lars Ingebrigtsen
2021-09-21 22:08 ` João Távora
2021-09-21 22:16 ` Lars Ingebrigtsen
2021-09-21 22:24 ` João Távora
2021-09-21 22:25 ` Lars Ingebrigtsen
2021-09-21 22:34 ` João Távora
2021-09-22 6:53 ` Philip Kaludercic
2021-09-22 7:12 ` João Távora
2021-09-22 7:14 ` Arthur Miller
2021-09-21 13:05 ` Philip Kaludercic [this message]
2021-09-21 13:27 ` Arthur Miller
2021-09-21 13:45 ` Philip Kaludercic
2021-09-21 14:05 ` Arthur Miller
2021-09-21 22:17 ` Richard Stallman
2021-09-21 22:24 ` Lars Ingebrigtsen
2021-09-22 9:54 ` Philip Kaludercic
2021-10-04 23:00 ` [ELPA] Add compat.el Philip Kaludercic
2021-10-07 7:03 ` Old (static) builds of Emacs Philip Kaludercic
2021-10-07 7:48 ` Michael Albinus
2021-10-07 7:56 ` Philip Kaludercic
2021-10-07 12:49 ` Stefan Monnier
2021-10-07 20:29 ` Philip Kaludercic
2021-10-07 21:21 ` Stefan Monnier
2021-11-30 21:21 ` Philip Kaludercic
2021-12-01 13:15 ` Stefan Monnier
2021-10-07 20:49 ` [ELPA] Add compat.el Philip Kaludercic
2021-10-08 5:56 ` Eli Zaretskii
2021-10-08 9:59 ` Philip Kaludercic
2021-10-08 11:10 ` Eli Zaretskii
2021-10-08 11:35 ` Philip Kaludercic
2021-10-08 7:45 ` Mattias Engdegård
2021-10-08 10:00 ` Philip Kaludercic
2021-10-15 19:08 ` Philip Kaludercic
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=87tuiersdc.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=emacs-devel@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 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).