From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 50999@debbugs.gnu.org, stefan@marxist.se, Richard Stallman <rms@gnu.org>
Subject: bug#50999: 29.0.50; Deleting libraries obsolete since Emacs 24
Date: Fri, 12 Nov 2021 13:11:20 +0800 [thread overview]
Message-ID: <87ee7mq7pj.fsf@yahoo.com> (raw)
In-Reply-To: <874k8ihsuy.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 12 Nov 2021 05:59:17 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> It's just not practical. We have to get rid of things that we no longer
> think is very useful in Emacs, otherwise Emacs will grow unbounded, and
> we don't have the maintainer capacity for that.
What about what I proposed, i.e. not byte-compiling those files, and in
general paying no attention to them?
It would take quite a long time for that to have an effect on the size
of Emacs. And it wouldn't require any maintenance; we could have a
folder acting as a dumping ground for Lisp that would otherwise be
deleted.
> Emacs has a package system. If there's a feature we remove from Emacs
> that people think is useful, they'll create a package for it and carry
> on.
What about an ELPA package, playing the same role as the dumping ground
folder?
I look forward to hearing your thoughts on this, thanks.
next prev parent reply other threads:[~2021-11-12 5:11 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-03 21:42 bug#50999: 29.0.50; Deleting libraries obsolete since Emacs 24 Stefan Kangas
2021-10-04 9:40 ` Lars Ingebrigtsen
2021-10-04 13:25 ` Stefan Kangas
2021-10-05 7:02 ` Lars Ingebrigtsen
2021-10-05 12:27 ` Eli Zaretskii
2021-10-05 13:07 ` Phil Sainty
2021-10-05 13:39 ` Stefan Kangas
2021-10-06 1:28 ` Phil Sainty
2021-10-05 13:39 ` Stefan Kangas
2021-12-03 14:56 ` Stefan Kangas
2021-12-03 16:47 ` bug#50999: [External] : " Drew Adams
2021-12-07 21:26 ` Stefan Kangas
2021-12-07 21:34 ` Drew Adams
2021-12-07 21:58 ` Stefan Kangas
2021-12-04 1:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-05 12:31 ` Stefan Kangas
2021-12-05 12:31 ` Stefan Kangas
2021-12-05 20:55 ` Glenn Morris
2021-12-07 2:21 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-07 3:07 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-08 1:37 ` Stefan Kangas
2021-12-08 2:13 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-04 9:22 ` Eli Zaretskii
2021-12-04 10:32 ` Stefan Kangas
2022-06-17 12:03 ` Stefan Kangas
2021-11-10 11:21 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-12 4:20 ` Richard Stallman
2021-11-12 4:36 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-12 4:59 ` Lars Ingebrigtsen
2021-11-12 5:11 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-11-12 6:27 ` Lars Ingebrigtsen
2021-11-12 6:36 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-14 0:47 ` Lars Ingebrigtsen
2021-11-14 17:48 ` bug#50999: [External] : " Drew Adams
2021-11-14 17:53 ` Eli Zaretskii
2021-11-14 18:04 ` Drew Adams
2021-11-14 18:18 ` Eli Zaretskii
2021-11-14 18:35 ` Drew Adams
2021-11-14 18:57 ` Eli Zaretskii
2021-11-14 21:33 ` Drew Adams
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=87ee7mq7pj.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=50999@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
--cc=rms@gnu.org \
--cc=stefan@marxist.se \
/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).