From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: jonas@bernoul.li, 71971@debbugs.gnu.org
Subject: bug#71971: 31.0.50; Add user option server-window-alist
Date: Sat, 06 Jul 2024 14:22:17 +0300 [thread overview]
Message-ID: <86cynq4vfa.fsf@gnu.org> (raw)
In-Reply-To: <871q463hke.fsf@gmx.de> (bug-gnu-emacs@gnu.org)
> Cc: Jonas Bernoulli <jonas@bernoul.li>
> Date: Sat, 06 Jul 2024 13:06:57 +0200
> From: Michael Albinus via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> A new user option `server-window-alist' shall be added to server.el. Every
> entry shall be of type (REGEXP . SERVER-WINDOW). REGEXP is used to filter
> for the buffer's file name, and if it matches, SERVER-WINDOW shall be
> applied. SERVER-WINDOW itself has the same type as the `server-window'
> user option.
>
> If no regexp matches, the value of user option `server-window' shall be
> used.
>
> This new user option is the same as the existing
> `with-editor-server-window-alist' from package with-editor.el. Mid-term,
> the former shall replace the latter.
Is it possible to describe the typical use cases which this option
targets? Given that client frames/windows are not meant for specific
buffers (IOW, a client frame/window can be used for editing several
buffers), what kind of workflow will benefit from this option?
(And please don't say "the same cases as those where server-window is
useful", because I don't understand its usefulness, either.)
Thanks.
next prev parent reply other threads:[~2024-07-06 11:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-06 11:06 bug#71971: 31.0.50; Add user option server-window-alist Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-06 11:22 ` Eli Zaretskii [this message]
2024-07-06 11:58 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-06 14:16 ` Jonas Bernoulli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-06 14:47 ` Eli Zaretskii
2024-07-08 17:41 ` Jonas Bernoulli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-08 17:56 ` Eli Zaretskii
2024-07-09 19:05 ` Jonas Bernoulli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-10 11:35 ` Eli Zaretskii
2024-07-10 16:32 ` Jonas Bernoulli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-10 18:02 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-19 16:45 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=86cynq4vfa.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=71971@debbugs.gnu.org \
--cc=jonas@bernoul.li \
--cc=michael.albinus@gmx.de \
/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.