From: Jonas Bernoulli <jonas@bernoul.li>
To: emacs-devel <emacs-devel@gnu.org>
Cc: rms@gnu.org
Subject: Adding with-editor to Emacs?
Date: Fri, 01 Sep 2023 16:38:02 +0200 [thread overview]
Message-ID: <87r0nidkmt.fsf@bernoul.li> (raw)
In-Reply-To: <E1qbslO-0006oK-RA@fencepost.gnu.org>
Richard Stallman <rms@gnu.org> writes:
> Are you involved in developing this?
Yes, I am the primary author. Contributions by other people are pretty
minor, or by people who have already done the copyright paperwork, so
that should not be a problem.
> It seems to me that this would fit best in emacsclient and its
> associated Lisp code -- that having it as a separate package
> is extra baggage.
>
> WDYT?
Adding this to Emacs would make sense. We would have to determine to
what extend existing code should be updated to do what this package does
and what parts should remain in a package/library in its own right.
For example, it would make sense to deprecate variable `server-window'
with a new `server-window-alist', even if the rest of with-editor.el
remained a separate library, or even outside of Emacs. (The new
variable would give packages more control over how their windows should
be displayed, if they have special needs, while still allowing users
to customize the default, or even to override the packages' wishes.)
I think the next step is to ask Eli and others, how they would want to
integrate the library / the functionality it provides.
An obstacle in getting this done quickly, is that I am getting requests
to do work in areas that I wasn't planning on touching any time soon,
with a higher than usual frequency. So the process of integrating this
into Emacs could be somewhat slow, depending on how much we diverge from
just merging this as-is in the form of a separate library/package.
> having it as a separate package is extra baggage.
Maybe. As far as adding `server-window-alist' goes, that would
certainly be a win.
But other than that, this package is basically "done" in its current
form. Work is only really required when someone found yet another way
to package Emacs, without thinking too much about emacsclient, if at
all. So I must point out that the primary effect for my personally
will be extra work, and not just in the short term.
Cheers,
Jonas
next parent reply other threads:[~2023-09-01 14:38 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <85msy98sni.fsf@elpa.gnu.org>
[not found] ` <E1qbslO-0006oK-RA@fencepost.gnu.org>
2023-09-01 14:38 ` Jonas Bernoulli [this message]
2023-09-01 16:12 ` Adding with-editor to Emacs? Eli Zaretskii
2023-09-01 17:25 ` Jim Porter
2023-09-01 17:44 ` Jonas Bernoulli
2023-09-01 18:42 ` Eli Zaretskii
2023-09-01 20:23 ` Jonas Bernoulli
2023-09-02 6:19 ` Eli Zaretskii
2023-09-02 18:12 ` Jonas Bernoulli
2023-09-02 18:57 ` Eli Zaretskii
2023-09-02 21:04 ` Jonas Bernoulli
2023-09-03 17:02 ` Lynn Winebarger
2023-09-03 17:21 ` Eli Zaretskii
2023-09-03 18:21 ` Lynn Winebarger
2023-09-03 18:37 ` Eli Zaretskii
2023-09-02 19:56 ` Stefan Kangas
2023-09-02 21:26 ` Jonas Bernoulli
2023-09-02 23:07 ` Stefan Kangas
2023-09-03 5:00 ` Eli Zaretskii
2023-09-02 11:39 ` Michael Albinus
2023-09-02 16:52 ` Jonas Bernoulli
2023-10-17 10:23 ` Michael Albinus
2023-10-17 17:18 ` Manuel Giraud via Emacs development discussions.
2023-10-17 18:09 ` Michael Albinus
2023-10-17 19:26 ` Manuel Giraud via Emacs development discussions.
2023-09-03 14:36 ` Manuel Giraud via Emacs development discussions.
2023-09-03 15:34 ` Eli Zaretskii
2023-09-03 18:54 ` Manuel Giraud via Emacs development discussions.
2023-09-03 19:26 ` Eli Zaretskii
2023-09-04 8:21 ` Manuel Giraud via Emacs development discussions.
2023-09-04 12:18 ` Eli Zaretskii
2023-09-04 12:44 ` Manuel Giraud via Emacs development discussions.
2023-09-04 13:18 ` Manuel Giraud via Emacs development discussions.
2023-09-06 0:59 ` Richard Stallman
2023-09-05 0:27 ` Richard Stallman
2023-09-15 21:59 ` Björn Bidar
2023-09-17 23:03 ` Richard Stallman
2023-09-18 8:59 ` Philip Kaludercic
2023-09-20 18:35 ` Richard Stallman
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=87r0nidkmt.fsf@bernoul.li \
--to=jonas@bernoul.li \
--cc=emacs-devel@gnu.org \
--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).