From: Giovanni Biscuolo <g@xelera.eu>
To: Mark H Weaver <mhw@netris.org>,
Pierre Neidhardt <mail@ambrevar.xyz>,
Guix Devel <guix-devel@gnu.org>
Subject: Re: emacs-lucid (was Re: Emacs closure at ~900MB?)
Date: Tue, 29 Sep 2020 10:49:53 +0200 [thread overview]
Message-ID: <878sct55n2.fsf@roquette.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87h7rk8pmz.fsf@netris.org>
[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]
Hello Mark,
thank you for your interest.
Mark H Weaver <mhw@netris.org> writes:
[...]
>> IMHO it's useful to have emacs-lucid in official Guix, with subsitutes
>> available for end users (I'm not using emacs in daemon mode over X11
>> over SSH for fear of chrashes).
>
> FYI, our 'emacs-no-x-toolkit' package has a closure size of 390.9 MiB
> and does _not_ have the Gtk bug described above. That's why I use it.
Yes I know that emacs version, I'm also considering using it (I do not
remember why I decided I needed an X toolkit... I should just try).
> Are there additional benefits to 'emacs-lucid' that are not already
> addressed by 'emacs-no-x-toolkit'?
emacs-lucid would have an X toolkit that does not crash the daemon when
remotely connecting, some people like to have that (an X tookit I mean)
even if usually it's not strictly needed.
> I'm not necessarily opposed to adding another Emacs variant, but I
> don't yet understand the motivation.
Help some users avoid experiencing "the bug", but I understand that
probably the use base for emacs-lucid is tiny.
Thanks! Gio'
--
Giovanni Biscuolo
Xelera IT Infrastructures
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2020-09-29 8:50 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 11:16 Emacs closure at ~900MB? zimoun
2020-09-22 11:31 ` Pierre Neidhardt
2020-09-22 11:34 ` zimoun
2020-09-22 11:45 ` Pierre Neidhardt
2020-09-22 11:50 ` Efraim Flashner
2020-09-24 17:28 ` emacs-lucid (was Re: Emacs closure at ~900MB?) Giovanni Biscuolo
2020-09-24 18:08 ` zimoun
2020-09-25 8:28 ` Giovanni Biscuolo
2020-09-25 10:23 ` Pierre Neidhardt
2020-09-25 23:06 ` zimoun
2020-09-29 8:42 ` Giovanni Biscuolo
2020-09-29 9:51 ` zimoun
2020-09-29 10:44 ` Giovanni Biscuolo
2020-09-26 16:32 ` Mark H Weaver
2020-09-26 18:26 ` Pierre Neidhardt
2020-09-26 21:26 ` Mark H Weaver
2020-09-27 6:33 ` Pierre Neidhardt
2020-09-27 10:53 ` Pierre Neidhardt
2020-09-27 20:49 ` Bonface M. K.
2020-09-28 6:43 ` Pierre Neidhardt
2020-09-28 10:49 ` Bonface M. K.
2020-09-28 8:56 ` zimoun
2020-09-28 9:25 ` Pierre Neidhardt
2020-09-28 12:02 ` zimoun
2020-09-28 14:42 ` Pierre Neidhardt
2020-09-28 19:16 ` Bengt Richter
2020-09-28 19:21 ` zimoun
2020-09-28 8:40 ` zimoun
2020-09-28 9:25 ` Pierre Neidhardt
2020-09-28 19:54 ` Mark H Weaver
2020-09-29 7:56 ` Pierre Neidhardt
2020-09-29 8:49 ` Giovanni Biscuolo [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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878sct55n2.fsf@roquette.i-did-not-set--mail-host-address--so-tickle-me \
--to=g@xelera.eu \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
--cc=mhw@netris.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/guix.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).