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: Tue, 29 Sep 2020 11:51:27 +0200 [thread overview]
Message-ID: <CAJ3okZ0wT1FwrKdiYQixztePWrBUS071e2qXLJ9m-V8wHhBZBA@mail.gmail.com> (raw)
In-Reply-To: <87blhp55zb.fsf@roquette.i-did-not-set--mail-host-address--so-tickle-me>
On Tue, 29 Sep 2020 at 10:42, Giovanni Biscuolo <g@xelera.eu> wrote:
> Please consider I'm still on Emacs 26.3 since one package I use does not
> work with 27.1... and I still have not tested "the bug" in a pure
> anvironmentt with emacs 27.1 only
Ouch! Which one is it?
> I'm affected by that bug every time I do:
>
> 1. on machine A: start emacs --daemon
> 2. on machine B: ssh -Y me@A
> 3. on machine B: emacsclient -c (in ssh session)
Sorry, I miss where this emacsclient is started? A or B?
If you start emacsclient on B and try to connect over SSH to the
server on A, which option do you provide? (naive question because I
have always failed to do that :-))
Personally, I have 2 uses cases:
i.
machine A: emacs --daemon
machine B: ssh -C me@A -t emacsclient -t
and I never do "ssh -CX me@A -t emacsclient -c" because the network is
usually too slow to export DISPLAY; machines A and B are usually a bit
far in my cases.
ii.
machine B: start emacs --daemon
machine B: emacsclient -c
machine B: open via TRAMP over ssh on A
And Tramp crashes time to time.
> AFAIU this bug is still affecting other Emacs users using GTK as X
> toolkit.
Yeah, for sure. And as you noted too, it is difficult to know what is
the exact status of this bug. :-)
All the best,
simon
next prev parent reply other threads:[~2020-09-29 9:52 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 [this message]
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=CAJ3okZ0wT1FwrKdiYQixztePWrBUS071e2qXLJ9m-V8wHhBZBA@mail.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).