unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jonas Bernoulli <jonas@bernoul.li>
To: Stefan Kangas <stefankangas@gmail.com>, Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, rms@gnu.org
Subject: Re: Adding with-editor to Emacs?
Date: Sat, 02 Sep 2023 23:26:18 +0200	[thread overview]
Message-ID: <87v8cs9shx.fsf@bernoul.li> (raw)
In-Reply-To: <CADwFkmn08rnbMbBk0rSkBy1jcCiWMF-E9Gj73y4N+KYWrWg8qA@mail.gmail.com>

Stefan Kangas <stefankangas@gmail.com> writes:

> Jonas Bernoulli <jonas@bernoul.li> writes:
>
>> Identifying the authors of the broken Emacs installations, contacting
>> them and explaining the issue to them, and then waiting for months/years
>> until the updates trickle down to users, was not an option.  I need a
>> solution now.  And this was such an exhausting experience, I did not
>> have the energy to *also* contact everyone who had messed up their Emacs
>> package.  And it is such a bad memory (it was the first time I got
>> massively attacked for publishing free software), that I am also not
>> volunteering to do that work now.
>
> Wow, what a ride.  I admire your patience, is all I can say.

Thanks.  Sometimes I have to vent a bit, even if I usually end up
regretting to have done so in public.  It helps to hear some
understanding words.  We've all been there, sometimes things just
get to stressful.

>>> Do you mean that emacsclient is installed in a place that just typing
>>> "emacsclient RET" at the shell prompt fails to run it?  If so, that's
>>> a broken installation, and Emacs shouldn't really try to fix that.
>>
>> I think this is a very reasonable for Emacs.  In other words, the best
>> course of action is to just forget the suggestion that with-editor is
>> added to Emacs.  There is no real need and nobody volunteering to do the
>> work anyway.
>
> It sounds like with-editor for the most part contains workarounds for
> broken Emacs installations?

That was the original feature but now it also contains a poorman's
substitute for emacsclient/server that works processes started from
Emacs (but also including processes running on remote machines).

As far as I am concerned, the package was done then.  Then requests to
support various emacs shells came in, and of course this could also be
useful for async-shell-command, and it became complex enough to warrant
a manual.  I wrote the in org and export it to texi, and of course once
(if) with-editor is added to Emacs, I will be informed that the
generated texi is not up to snuff....

This all started with a rather reasonable feature that just depended on
things not being broken, and then spiraled completely out of control,
with people asking me to add just add one more feature, again and again,
because after all with-editor would be the logical place to implement it.

Oh no!  Some memory is coming back.  When it was originally suggested
that we switch from "git commit -m 'done'" to "EDITOR=emacsclient git
commit", I agreed that this was obviously the right thing to do, but I
actually also realized that doing so would be risky and wanted to do it
slowly as an opt-in feature to avoid breakage, but everyone was "no no,
that is totally safe" and talked me into just pulling the plug.

So I hope you all understand now why I get a bit touchy when being
asked to work on this just a little more.

> Is there anything in use-package that does
> not belong to that category, and that you therefore think *should*
> really be fixed in Emacs?
>
> Perhaps it would be worth focusing on just that part.

(use-package?  I'll assume you meant with-editor.)

Replacing server-window with server-window-alist or something like that.



  reply	other threads:[~2023-09-02 21:26 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   ` Adding with-editor to Emacs? Jonas Bernoulli
2023-09-01 16:12     ` 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 [this message]
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=87v8cs9shx.fsf@bernoul.li \
    --to=jonas@bernoul.li \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    --cc=stefankangas@gmail.com \
    /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).