unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "M. Ian Graham" <hello@miangraham.com>
To: "55149@debbugs.gnu.org" <55149@debbugs.gnu.org>
Cc: "thorn@fastmail.fm" <thorn@fastmail.fm>,
	"monnier@iro.umontreal.ca" <monnier@iro.umontreal.ca>
Subject: bug#55149: 29.0.50; Commit f30625943e broke magit/with-editor
Date: Thu, 28 Apr 2022 04:06:49 +0000	[thread overview]
Message-ID: <vc4x8k5oonhvmE8JezBSgc4_Wxc_44UPJ0ojQ__9qQNUioNZf2dHhlv17HGOWxn2nvRw3qoTeOxScSQf22UHMt86ZlgrJbA1Y1B6JFl_Lpc=@miangraham.com> (raw)
In-Reply-To: <87wnfa3cop.fsf@fastmail.fm>

[-- Attachment #1: Type: text/plain, Size: 1442 bytes --]

> With stock-emacs when doing "emacsclient foo.txt", it just prints "Waiting for Emacs..." but finishes immediately.

Hi, quick clarification on this: As far as I can tell from my own observations, all emacsclient breakage here is a downstream side-effect of magit/with-editor's advice calls somehow getting messed up.

Observed breakage:

Using bc9be5449e1127bc1b05a6cad8471c6eba52c8e9 and prior I cannot reproduce any related problems. Magit works properly.
Using f30625943edefbd88ebf84acbc254ed88db27beb and later causes the magit-commit command to break with a GitError ("problem with the editor", where the editor is emacsclient) before displaying its message editor window. Given the commit contents I assume the advice-add usage in with-editor is being affected somehow.

emacsclient issues:

In the same emacs instance as above, only after first reproducing the magit-commit error (and presumably leaving a stalled client connection in place), later emacsclient usage fails via the CLI.
Given a new session using a fresh server-start and using basic emacsclient commands, I don't observe any problems.

If I'm misunderstanding anyone and you're able to repro manual emacsclient breakage with a fresh server, please follow up.

I'm not yet sure what a minimal breaking advice test looks like. Trying simple advice-add calls that look similar to with-editor's hasn't turned up any problems yet. I'll shout back if I find something.
-Ian

[-- Attachment #2: Type: text/html, Size: 2144 bytes --]

  parent reply	other threads:[~2022-04-28  4:06 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28  5:15 bug#55161: 29.0.50; [PATCH] oclosure transcription error redux dick
2022-04-28 10:23 ` bug#55149: " Lars Ingebrigtsen
2022-04-27 12:48   ` bug#55149: 29.0.50; Commit f30625943e broke magit/with-editor Tassilo Horn
2022-04-27 19:41     ` No Wayman
2022-04-27 21:48       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-28  3:39         ` Tassilo Horn
2022-04-28  4:02           ` No Wayman
2022-04-28  6:58         ` Juri Linkov
2022-04-28  7:12           ` Tassilo Horn
2022-04-28  7:22             ` Juri Linkov
2022-04-28  7:31               ` Tassilo Horn
2022-04-28 13:39           ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-28 14:14             ` Tassilo Horn
2022-04-28 14:28               ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-28 14:39                 ` Tassilo Horn
2022-04-28  2:06     ` bug#55149: (No Subject) M. Ian Graham
2022-04-28  4:06     ` M. Ian Graham [this message]
2022-04-28  4:47       ` bug#55149: 29.0.50; Commit f30625943e broke magit/with-editor Tassilo Horn
2022-04-28  6:12         ` M. Ian Graham
2022-04-28  6:28           ` Tassilo Horn
2022-04-28  6:56             ` M. Ian Graham
2022-04-28 13:50     ` bug#55149: bug#55161: 29.0.50; [PATCH] oclosure transcription error redux Rudolf Schlatte
2022-04-28 13:28   ` dick
2022-04-28 13:42   ` bug#55149: " Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-28 15:26     ` bug#55161: bug#55149: 29.0.50; Commit f30625943e broke magit/with-editor Jonas Bernoulli
2022-04-28 16:32       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-28 22:49         ` Jonas Bernoulli
2022-04-28 23:44           ` Stefan Monnier 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

  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='vc4x8k5oonhvmE8JezBSgc4_Wxc_44UPJ0ojQ__9qQNUioNZf2dHhlv17HGOWxn2nvRw3qoTeOxScSQf22UHMt86ZlgrJbA1Y1B6JFl_Lpc=@miangraham.com' \
    --to=hello@miangraham.com \
    --cc=55149@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=thorn@fastmail.fm \
    /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).