From: Michael Albinus <michael.albinus@gmx.de>
To: Jonas Bernoulli <jonas@bernoul.li>
Cc: Eli Zaretskii <eliz@gnu.org>,
manuel@ledu-giraud.fr, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: with-editor seems like a bug fix
Date: Sat, 06 Jul 2024 13:15:15 +0200 [thread overview]
Message-ID: <87wmly22m4.fsf@gmx.de> (raw)
In-Reply-To: <87frsrk2ak.fsf@bernoul.li> (Jonas Bernoulli's message of "Tue, 02 Jul 2024 21:43:31 +0200")
Jonas Bernoulli <jonas@bernoul.li> writes:
Hi Jonas,
>>>> - Use always emacsclient, locally or remote
>>>> - Check for emacsclient only at the well know places
>>>> - Recommend to use with-editor from ELPA if this fails
>>>
>>> I'd need to see the patch to understand what that means in practice.
>>
>> If Jonas agrees this approach, I could try to puzzle something together.
>
> Sounds good to me in principal.
Sorry for the late reply. I'm very slow these days :-(
> I am unsure whether you plan to add a stripped-down with-editor.el to
> Emacs or implement the mentioned functionality in existing libraries.
> The latter seems more reasonable to me (and I'm guessing that's what
> you had in mind).
Yes, the latter.
I will implement this in several steps. For every step I'll write a bug
report (severity wishlist) first, so we have a place to discuss. And not
to poison the emacs-devel ML with our jabber :-)
> Please also consider these features:
>
> - Add `server-window-alist'. This would allow both packages and users
> to specify that certain buffers should be displayed differently from
> the default specified by `server-window'.
That's the first step. Bug#71971.
> - Allow running `server-start' in multiple emacs instances, without
> the user/package who calls that, having figure out if another instance
> is already using the same name. I.e., something to replace:
>
> (unless (process-live-p server-process)
> (when (server-running-p server-name)
> (setq server-name (format "server%s" (emacs-pid)))
> (when (server-running-p server-name)
> (server-force-delete server-name)))
> (server-start))
I'll check.
> Cheers,
> Jonas
Best regards, Michael.
next prev parent reply other threads:[~2024-07-06 11:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 3:07 with-editor seems like a bug fix Richard Stallman
2024-06-27 5:58 ` Eli Zaretskii
2024-06-27 6:14 ` Po Lu
2024-06-27 9:44 ` Manuel Giraud via Emacs development discussions.
2024-06-27 10:29 ` Eli Zaretskii
2024-06-27 10:58 ` Michael Albinus
2024-06-29 11:06 ` Michael Albinus
2024-06-29 12:38 ` Eli Zaretskii
2024-06-29 12:47 ` Michael Albinus
2024-06-29 12:58 ` Eli Zaretskii
2024-06-29 14:39 ` Michael Albinus
2024-06-29 15:58 ` Eli Zaretskii
2024-06-29 16:08 ` Michael Albinus
2024-07-02 19:43 ` Jonas Bernoulli
2024-07-06 11:15 ` Michael Albinus [this message]
2024-06-30 11:51 ` Manuel Giraud via Emacs development discussions.
2024-07-01 1:52 ` Stefan Kangas
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wmly22m4.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jonas@bernoul.li \
--cc=manuel@ledu-giraud.fr \
--cc=rms@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).