[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#55103: 29.0.50; Server mode + reuseable-frames + switch-to-buffer-ot
|
From: |
Po Lu |
|
Subject: |
bug#55103: 29.0.50; Server mode + reuseable-frames + switch-to-buffer-other-window + *scratch* => hang |
|
Date: |
Mon, 25 Apr 2022 16:55:18 +0800 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.91 (gnu/linux) |
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Yes, I don't think Emacs can, in general, know whether a frame is
> visible on the same actual display as another frame.
If that happens, then IMNSHO there is a problem in the user's setup,
since it's at the very least wasteful, and will probably cause problems
in the long run.
For example, drag-and-drop doesn't work between two frames with
different terminals connected to the same display.
- bug#55103: 29.0.50; Server mode + reuseable-frames + switch-to-buffer-other-window + *scratch* => hang, Derek Upham, 2022/04/24
- bug#55103: 29.0.50; Server mode + reuseable-frames + switch-to-buffer-other-window + *scratch* => hang, Lars Ingebrigtsen, 2022/04/25
- bug#55103: 29.0.50; Server mode + reuseable-frames + switch-to-buffer-other-window + *scratch* => hang,
Po Lu <=
- bug#55103: 29.0.50; Server mode + reuseable-frames + switch-to-buffer-other-window + *scratch* => hang, martin rudalics, 2022/04/25
- bug#55103: 29.0.50; Server mode + reuseable-frames + switch-to-buffer-other-window + *scratch* => hang, Lars Ingebrigtsen, 2022/04/25
- bug#55103: 29.0.50; Server mode + reuseable-frames + switch-to-buffer-other-window + *scratch* => hang, martin rudalics, 2022/04/25
- bug#55103: 29.0.50; Server mode + reuseable-frames + switch-to-buffer-other-window + *scratch* => hang, Derek Upham, 2022/04/26
- bug#55103: 29.0.50; Server mode + reuseable-frames + switch-to-buffer-other-window + *scratch* => hang, martin rudalics, 2022/04/26
- bug#55103: 29.0.50; Server mode + reuseable-frames + switch-to-buffer-other-window + *scratch* => hang, Lars Ingebrigtsen, 2022/04/26