GNU bug report logs - #76870
31.0.50; server-start with non-nil arg LEAVE-DEAD can write confusing warnings

Previous Next

Package: emacs;

Reported by: Jens Schmidt <jschmidt4gnu <at> vodafonemail.de>

Date: Sat, 8 Mar 2025 15:46:04 UTC

Severity: normal

Found in version 31.0.50

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Jens Schmidt <jschmidt4gnu <at> vodafonemail.de>
Cc: 76870 <at> debbugs.gnu.org
Subject: bug#76870: 31.0.50; server-start with non-nil arg LEAVE-DEAD can write confusing warnings
Date: Sun, 09 Mar 2025 12:39:46 +0200
> Date: Sat, 8 Mar 2025 18:27:50 +0100
> Cc: 76870 <at> debbugs.gnu.org
> From: Jens Schmidt <jschmidt4gnu <at> vodafonemail.de>
> 
> >>      ⛔ Warning (server): Unable to stop an external Emacs server.
> >>      There is an existing Emacs server, named "server"
> >>      Stop it either in its Emacs session or call M-x server-force-delete to forcibly disconnect it.
> > 
> > This doesn't seem to be very different from the current message.
> 
> Except that I use the word "stop" instead of "start" in its first
> line...

But that is confusing.  This message is for the case when the user
wants to start a server; the fact that the previous one should be
stopped is a side effect.  So talking about "stopping" will confuse,
IMO.

> Do we agree that the following are all equivalent in effect
> 
>   M-: (server-start t) RET
> 
>   C-u M-x server-start RET
> 
>   C-- M-x server-mode RET
> 
> and all should *stop* the server without restarting it?

Yes.

> If yes, then I find it confusing to read that Emacs could not
> *start* the server in the resulting warning.

So you want to have an alternative message about stopping only?  That
could be a good idea, yes.




This bug report was last modified 56 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.