all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Albinus via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Jonas Bernoulli <jonas@bernoul.li>
Cc: Eli Zaretskii <eliz@gnu.org>, 71971@debbugs.gnu.org
Subject: bug#71971: 31.0.50; Add user option server-window-alist
Date: Wed, 10 Jul 2024 20:02:01 +0200	[thread overview]
Message-ID: <87plrlf7mu.fsf@gmx.de> (raw)
In-Reply-To: <87ttgxtdfr.fsf@bernoul.li> (Jonas Bernoulli's message of "Wed, 10 Jul 2024 18:32:56 +0200")

Jonas Bernoulli <jonas@bernoul.li> writes:

Hi,

> Thanks for the clarifications, I understand better now and agree its
> a worthwhile goal.  Unfortunately I have no idea how to do it, but I
> look forward to see what you and others come up with.  I can't think
> of anything myself, for now at least.

What I could imagine is, that emacsclient gets the option to send an
identification, a string, to the server. With this, on the server side,
a set of preferences (variables) could be set for a given
identification, which matches a regexp. Not only for server-window, but
any variable. This would look like

((REGEXP (VAR . VALUE) .. (VAR . VALUE))
 (REGEXP (VAR . VALUE) .. (VAR . VALUE))
 ...)

Any VAR, like server-window, would use its related VALUE, which has
precedence.

Packages, like magit, could prepare such preferences, and activate if
the corresponding emacsclient sends an identification which matches a
regexp. User could prepare their own preferences, and invoke emacsclient
with their private identification, like 'emacsclient --ident="my-identification"'.

On protocol level between emacsclient and server.el, we would need a new
command '-ident'. Or, if we must be backwards compatible, we could use
'eval' to set it, or we could use a special formatted '-comment'.

This doesn't say which variables we recommend to use for
preferences. Just a mean to communicate between emacsclient and
server.el.

> Cheers!

Best regards, Michael.





  reply	other threads:[~2024-07-10 18:02 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
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 [this message]
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=87plrlf7mu.fsf@gmx.de \
    --to=bug-gnu-emacs@gnu.org \
    --cc=71971@debbugs.gnu.org \
    --cc=eliz@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.