unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: luangruo@yahoo.com, eliz@gnu.org, email@johnmuhl.mx,
	schwab@linux-m68k.org, emacs-devel@gnu.org
Subject: Re: Bootstrap broken between 2893cb6a21af3384cf5d6dc2b6bbdd5ebba8e1ad and 469fe6a040d6df612c00ea169670c6d8d7e58563
Date: Sun, 19 Dec 2021 23:43:49 -0500	[thread overview]
Message-ID: <E1mzAWb-0005WS-B0@fencepost.gnu.org> (raw)
In-Reply-To: <87tuf4yj4q.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun,  19 Dec 2021 11:38:29 +0100)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > Yes, I think that sounds like a good idea -- I have no idea why rmail
  > has its own loaddefs in the first place.

I think this goes back to the days when it was important for Emacs to
fit in a machine with 1 meg of memory space, not virtualized.

Rmail consisted of several Lisp files, each with its own autoloads,
and none of those autoloads was needed until rmail.el had been loaded.
rmail-loaddefs.el enabled who did not use Rmail to avoid sacrificing
space for those autoloads.

This is completely unnecessary nowadays.

-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)





  parent reply	other threads:[~2021-12-20  4:43 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-16 23:47 Bootstrap broken between 2893cb6a21af3384cf5d6dc2b6bbdd5ebba8e1ad and 469fe6a040d6df612c00ea169670c6d8d7e58563 Andreas Schwab
2021-12-16 23:54 ` john muhl
2021-12-17  6:48 ` Lars Ingebrigtsen
2021-12-17  7:07   ` Po Lu
2021-12-17  7:20     ` Lars Ingebrigtsen
2021-12-17  8:04       ` Lars Ingebrigtsen
2021-12-17 12:15         ` Eli Zaretskii
2021-12-18  7:34           ` Lars Ingebrigtsen
2021-12-18  9:27             ` Eli Zaretskii
2021-12-19 10:38               ` Lars Ingebrigtsen
2021-12-19 16:52                 ` Eli Zaretskii
2021-12-19 16:53                 ` Stefan Monnier
2021-12-19 17:09                   ` Eli Zaretskii
2021-12-19 17:14                   ` Stefan Kangas
2021-12-19 17:16                   ` secondary loaddefs [was Re: Bootstrap broken betweeen ...] Glenn Morris
2021-12-20  4:43                 ` Richard Stallman [this message]
2021-12-17 12:42         ` Bootstrap broken between 2893cb6a21af3384cf5d6dc2b6bbdd5ebba8e1ad and 469fe6a040d6df612c00ea169670c6d8d7e58563 Stefan Monnier
2021-12-18  7:29           ` Lars Ingebrigtsen
2021-12-18 16:28             ` Stefan Monnier
2021-12-19 10:52               ` Lars Ingebrigtsen
2021-12-17  7:16   ` Kévin Le Gouguec

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=E1mzAWb-0005WS-B0@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=email@johnmuhl.mx \
    --cc=larsi@gnus.org \
    --cc=luangruo@yahoo.com \
    --cc=schwab@linux-m68k.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).