From: Derek Upham <derek_upham@mailfence.com>
To: martin rudalics <rudalics@gmx.at>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 55103@debbugs.gnu.org
Subject: bug#55103: 29.0.50; Server mode + reuseable-frames + switch-to-buffer-other-window + *scratch* => hang
Date: Mon, 25 Apr 2022 20:49:52 -0700 [thread overview]
Message-ID: <87v8uwpkpr.fsf@priss.frightenedpiglet.com> (raw)
In-Reply-To: <5f45b6bc-8664-2d61-ee0e-b7fc6fa221b0@gmx.at>
martin rudalics <rudalics@gmx.at> writes:
>> Then t doesn't seem like a very useful value?
>
> Maybe Derek will tell us whether '0' is not sufficient for him.
All of this came from me experimenting with the configuration
suggested in the Perspective package:
https://github.com/nex3/perspective-el#some-musings-on-emacs-window-layouts
I guess the author doesn’t use the server.
After looking at the “Action Alists for Buffer Display” docs, I
tried ‘visible’ and that fixes the problem. In particular, I
brought up *scratch* in a separate TTY client, and Emacs filtered
that display from consideration, like we would want.
Is ‘t’ is ever useful, I wonder? What other categories are there
besides visible frames and iconified frames (both covered by ‘0’),
and this edge case?
Anyway to summarize: this is not a dire problem, it was just weird
and worth investigating. The proposed fix works for me.
Thanks,
Derek
next prev parent reply other threads:[~2022-04-26 3:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 1:20 bug#55103: 29.0.50; Server mode + reuseable-frames + switch-to-buffer-other-window + *scratch* => hang Derek Upham
2022-04-25 7:56 ` Lars Ingebrigtsen
2022-04-25 8:55 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-25 9:12 ` martin rudalics
2022-04-25 9:43 ` Lars Ingebrigtsen
2022-04-25 17:37 ` martin rudalics
2022-04-26 3:49 ` Derek Upham [this message]
2022-04-26 7:39 ` martin rudalics
2022-04-26 10:12 ` Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v8uwpkpr.fsf@priss.frightenedpiglet.com \
--to=derek_upham@mailfence.com \
--cc=55103@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rudalics@gmx.at \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.