GNU bug report logs - #79058
30.1; involking signal using emacsclient takes very long time to complete ~2 seconds

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Bror Winther <bbw <at> nobad.coffee>
Cc: 79058 <at> debbugs.gnu.org
Subject: bug#79058: 30.1; involking signal using emacsclient takes very long time to complete ~2 seconds
Date: Mon, 28 Jul 2025 15:50:29 +0300

> From: Bror Winther <bbw <at> nobad.coffee>
> Date: Mon, 28 Jul 2025 05:07:16 +0200
> Cc: 79058 <at> debbugs.gnu.org
> 
> I do feel that cli the option --no-wait should honor the meaning and not wait 
> for errors. It smells like a bug or oversight that it doesn’t. The current behaviour 
> contradicts the help text.

No, that's not what --no-wait is about.  The user manual spells that
out:

  ‘-n’
  ‘--no-wait’
       Let ‘emacsclient’ exit immediately, instead of waiting until all
       server buffers are finished.  You can take as long as you like to
       edit the server buffers within Emacs, and they are _not_ killed
       when you type ‘C-x #’ in them.

So --no-wait means do not wait until the user is done editing the
server buffers and dismisses them with "C-x #".

Previous Next

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