unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rms@gnu.org,  emacs-devel@gnu.org
Subject: Re: with-editor seems like a bug fix
Date: Thu, 27 Jun 2024 14:14:13 +0800	[thread overview]
Message-ID: <87a5j6vrnu.fsf@yahoo.com> (raw)
In-Reply-To: <86frsz6i6v.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 27 Jun 2024 08:58:00 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> Is there any chance we can convince the author to sign papers,
>> or perhaps have someone else write different code to do this job?
>
> That's not the issue here.  The issue is to understand what are the
> problems with-editor tries to solve, and then decide which ones of
> them we want to solve in Emacs and how.  This was the conclusion from
> that Sep 2023 discussion, at least from my POV.

None the less, it would be prudent to get papers from its developers, I
think, it being intimately connected with Magit.  Which calls to mind
the question, whatever became of our plans to import Magit into core?



  reply	other threads:[~2024-06-27  6:14 UTC|newest]

Thread overview: 16+ 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 [this message]
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-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=87a5j6vrnu.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=eliz@gnu.org \
    --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).