From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: phillip.lord@russet.org.uk, rms@gnu.org,
monnier@IRO.UMontreal.CA, emacs-devel@gnu.org
Subject: Re: Core ELPA was: Testing fontification, indentation, and buffer manipulation
Date: Tue, 12 Mar 2019 16:52:31 +0100 [thread overview]
Message-ID: <m2sgvs6qf4.fsf@gmail.com> (raw)
In-Reply-To: <83h8c83xqw.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 12 Mar 2019 17:42:31 +0200")
>>>>> On Tue, 12 Mar 2019 17:42:31 +0200, Eli Zaretskii <eliz@gnu.org> said:
>> From: Richard Stallman <rms@gnu.org> Date: Mon, 11 Mar 2019
>> 23:38:24 -0400 Cc: monnier@IRO.UMontreal.CA,
>> emacs-devel@gnu.org
>>
>> > The changes I am suggesting would (eventually when finished)
>> produce two > tar balls "emacs" and "emacs-with-elpa". The
>> latter would come with > additional ELPA packages; it would
>> only be generated with a configure > option but, of course, to
>> build in this way would require access to > those ELPA
>> packages. To build only the former would not require access >
>> to those ELPA packages.
>>
>> That's not unreasonable. I'm not arguing against that.
Eli> I will note that this is going where XEmacs was before, and I
Eli> don't think the result was encouraging, FWIW.
Back when I still used XEmacs, downloading the 'sumo' tarball with all
the packages was the second step Iʼd perform after downloading the
sources, so in practice splitting them out didnʼt do much for me. OTOH
I donʼt think XEmacs ever had anything like elpa.
BTW, I may have missed part of the discussion, but why do we need two
tar balls? Could we not just have a 'download a bunch of elpa
packages' elisp function instead? [1] (Iʼll note that I essentially do
this manually for things like org-mode which are in core and elpa).
Robert
Footnotes:
[1] Iʼm spoiled: Iʼm rarely without an Internet connection
next prev parent reply other threads:[~2019-03-12 15:52 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 15:43 Testing fontification, indentation, and buffer manipulation Daniele Nicolodi
2019-01-15 18:45 ` Yuri Khan
2019-01-19 15:07 ` Daniele Nicolodi
2019-01-21 10:45 ` Jostein Kjønigsen
2019-01-21 20:57 ` Richard Stallman
2019-01-23 23:22 ` Phillip Lord
2019-01-24 2:09 ` Stefan Monnier
2019-01-24 10:29 ` Phillip Lord
2019-01-24 14:48 ` Ted Zlatanov
2019-01-26 0:46 ` Stefan Monnier
2019-01-26 7:17 ` Eli Zaretskii
2019-01-26 10:41 ` Phillip Lord
2019-02-20 19:59 ` Core ELPA was: " Phillip Lord
2019-02-27 23:05 ` Stefan Monnier
2019-03-01 15:55 ` Phillip Lord
2019-03-01 17:25 ` Stefan Monnier
2019-03-01 21:39 ` Phillip Lord
2019-03-01 22:07 ` Stefan Monnier
2019-03-02 11:14 ` Phillip Lord
2019-03-03 3:23 ` Stefan Monnier
2019-03-03 18:06 ` Phillip Lord
2019-03-08 2:51 ` Stefan Monnier
2019-03-10 11:45 ` Phillip Lord
2019-03-10 18:02 ` Stefan Monnier
2019-03-11 22:46 ` Phillip Lord
2019-03-12 1:11 ` Stefan Monnier
2019-03-12 23:02 ` Phillip Lord
2019-03-13 19:05 ` Stefan Monnier
2019-03-13 22:41 ` Phillip Lord
2019-03-02 3:36 ` Richard Stallman
2019-03-02 11:21 ` Phillip Lord
2019-03-03 3:00 ` Richard Stallman
2019-03-03 17:52 ` Phillip Lord
2019-03-04 3:27 ` Richard Stallman
2019-03-10 11:27 ` Phillip Lord
2019-03-11 1:23 ` Richard Stallman
2019-03-11 22:08 ` Phillip Lord
2019-03-12 3:38 ` Richard Stallman
2019-03-12 15:42 ` Eli Zaretskii
2019-03-12 15:52 ` Robert Pluim [this message]
2019-03-12 17:25 ` Eli Zaretskii
2019-03-12 22:49 ` Phillip Lord
2019-03-12 22:48 ` Phillip Lord
2019-03-12 18:37 ` XEmacs packages (was: Core ELPA was: Testing fontification, indentation, and buffer manipulation) Stefan Monnier
2019-03-13 3:32 ` Core ELPA was: Testing fontification, indentation, and buffer manipulation Richard Stallman
2019-01-16 7:58 ` Helmut Eller
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2sgvs6qf4.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
--cc=phillip.lord@russet.org.uk \
--cc=rms@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.