From: Eli Zaretskii <eliz@gnu.org>
To: Constantin Kulikov <zxnotdead@gmail.com>
Cc: 72345@debbugs.gnu.org, code@sebasmonia.com
Subject: bug#72345: 29.4; Emacs daemon on Windows OS
Date: Mon, 29 Jul 2024 15:12:58 +0300 [thread overview]
Message-ID: <86bk2gz99x.fsf@gnu.org> (raw)
In-Reply-To: <CAFkz2yrfSoKq8VD2M8qGksJakO_DdU9iRiFCssJqfHg-bdFC=w@mail.gmail.com> (message from Constantin Kulikov on Mon, 29 Jul 2024 12:28:08 +0300)
> From: Constantin Kulikov <zxnotdead@gmail.com>
> Date: Mon, 29 Jul 2024 12:28:08 +0300
>
> I found the root of the problem. The horrors I described in starting post happens only if you specify custom
> command line parameters in emacs --daemon command, like:
>
> ```
> # emacs.exe --daemon -myparam test
> ```
>
> Which can be used in a config like:
>
> ```
> (let ((myparamcons (member "-myparam" command-line-args)))
> (setq myparam (cadr myparamcons)))
> ```
>
> If you specify such a command line argument then the server file is not created by default and if you manually
> (server-start) from your config then emacs read-* functions are trying to read input from the terminal. But
> interestingly that if you press C-x C-c in emacsclient frame -- then emacs request to save modified files are
> handled properly in GUI frame.
>
> So the "solution" is not to specify any custom command line arguments.
> I consider it as a bug.
I can reproduce this in Emacs 29, but not on the current emacs-30
release branch, which will eventually become Emacs 30.1. Emacs 30
refuses to start in this case:
d:\>emacs --daemon -Q -myparam test
Starting Emacs daemon.
Unknown option `-myparam'
d:\>echo %ERRORLEVEL%
-1
and after the above, I see no Emacs process running, so it exited with
status -1 after reporting the error.
Thus, I guess we already fixed this bug.
next prev parent reply other threads:[~2024-07-29 12:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-28 22:08 bug#72345: 29.4; Emacs daemon on Windows OS Constantin Kulikov
2024-07-29 0:20 ` Constantin Kulikov
2024-07-29 9:28 ` Constantin Kulikov
2024-07-29 10:52 ` Constantin Kulikov
2024-07-29 12:12 ` Eli Zaretskii [this message]
2024-08-24 8:20 ` Eli Zaretskii
2024-07-29 3:43 ` Sebastián Monía
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=86bk2gz99x.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=72345@debbugs.gnu.org \
--cc=code@sebasmonia.com \
--cc=zxnotdead@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).