From: zimoun <zimon.toutoune@gmail.com>
To: Giovanni Biscuolo <g@xelera.eu>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: emacs-lucid (was Re: Emacs closure at ~900MB?)
Date: Sat, 26 Sep 2020 01:06:25 +0200 [thread overview]
Message-ID: <86blhttq1a.fsf@gmail.com> (raw)
In-Reply-To: <87blhutg3n.fsf@roquette.i-did-not-set--mail-host-address--so-tickle-me>
On Fri, 25 Sep 2020 at 10:28, Giovanni Biscuolo <g@xelera.eu> wrote:
> If that's the case could you please add a comment in #41732 that points
> to #43538 explaining that it solves the use cases of #41732, possibly
> with some examples and/or a Coockbook section?
Attempt currently happening… :-)
See: <https://issues.guix.gnu.org/43578#8>
> Re the subject: do you think #43578 can help users in getting
> emacs-lucid starting from emacs? Do you have an example please?
I do not know. However, I am not personally motivated by emacs-lucid.
Maybe I miss something but if I read correctly, this toolkit is old and
so I do not know how it is maintained. Is the new HarfBuzz included?
Well, #41732 and #43578 change the Emacs VM when compiling Emacs
packages and not the rendering toolkit. Other said, compiling Emacs
packages with the package emacs or emacs-lucid is exactly the same. The
difference between emacs and emacs-lucid is the rendering toolkit, not
the VM. AFAIU.
> AFAIU having a public emacs-lucid in Guix master is a better solution
> for users, but I may be missing something! :-D
You mean better because the GTK bug? Well, I am extensively using Emacs
and I do not remember hitting this bug. Maybe I do not use Emacs
enough. ;-)
Cheers,
simon
next prev parent reply other threads:[~2020-09-25 23:06 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 [this message]
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
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=86blhttq1a.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=g@xelera.eu \
--cc=guix-devel@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 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).