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
