unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
Cc: Philip Kaludercic <philipk@posteo.net>,
	 emacs-devel <emacs-devel@gnu.org>,  Eli Zaretskii <eliz@gnu.org>,
	 arash@gnu.org, Stefan Kangas <stefankangas@gmail.com>,
	 jb@jeremybryant.net
Subject: A small(er) Emacs (was: Why not include all ELPA packages in an Emacs release?)
Date: Thu, 30 May 2024 10:34:35 -0400	[thread overview]
Message-ID: <jwvbk4nxtrh.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CAO48Bk9H1BcOSnv1rnxEpezpmSHQgXGWSk4Db_Yn29sZ+FUiKQ@mail.gmail.com> (Pedro Andres Aranda Gutierrez's message of "Thu, 30 May 2024 08:16:42 +0200")

> But just keep in mind that there are situations, where the platform
> must deploy Emacs on, might not be as relaxed WRT disk space... And
> it's not about a specific package, it's about a trickle of packages
> becoming a flood...

Emacs tarballs have grown over the years, some versions growing
very significantly.  Is it a concern?  Yes, to some extent.
Is it worth the effort of making a "slim Emacs" option?  Apparently not
because I don't know of anyone who has gone through the effort of
actually making it a reality.

IME if your target has enough disk constraints that installing the
full Emacs is a concern, you're probably better served by one of:
- Another editor (e.g. Zile).
- Tramp.
- just installing the full Emacs anyway.

If you think you have a good use case where a "slim Emacs" is better
than the above options, then by all means, get working on a patch.
If it's simple&clean enough we may even accept it.
I'm not holding my breath.


        Stefan




      parent reply	other threads:[~2024-05-30 14:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-29 16:31 Re Re: Why not include all ELPA packages in an Emacs release? Pedro Andres Aranda Gutierrez
2024-05-29 20:36 ` Philip Kaludercic
2024-05-30  6:16   ` Pedro Andres Aranda Gutierrez
2024-05-30  6:31     ` Philip Kaludercic
2024-05-30 10:36       ` Pedro Andres Aranda Gutierrez
2024-05-30 14:34     ` Stefan Monnier [this message]

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=jwvbk4nxtrh.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=arash@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jb@jeremybryant.net \
    --cc=paaguti@gmail.com \
    --cc=philipk@posteo.net \
    --cc=stefankangas@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).