From: Oleksandr Gavenko <gavenkoa@gmail.com>
To: cygwin@cygwin.com
Subject: run.exe + conhost + emacs-w32 / emacsclient-w32 problem.
Date: Mon, 12 Jun 2017 12:51:00 -0000 [thread overview]
Message-ID: <vriu37b5v070.fsf@gavenkoa.example.com> (raw)
From some time I can't run emacs-w32 / emacsclient-w32 via run.exe from
cmd.exe or mintty.exe.
Actually at the end I use chain of call:
``e.bat`` with: run.exe --quote emacsclient-w32 -a e
``e`` with: cygstart --action=runas run emacs-w32
and then:
run --quote emacsclient-w32 ...
Now I have a problem to run directly:
run emacs-w32 -Q
during Windows 10 boot process, in first 1-2 min after boot from Win+R or cmd.
After that period of time I am able to start Emacs from Win+R "run emacs-w32 -Q".
It opens only from second time from cmd.exe on: run emacs-w32 -Q
It never opens from mintty on: run emacs-w32 -Q
Procmon showed that:
* 'run' creates 'conhost'
* 'run' creates 'emacs-w32'
* 'conhost' exits
* 'run' exits
* 'emacs-w32' exits
I see no any strange calls in procmon.
The most dangerous what was done is "Windows 10 Creators Update" after which I
started notice problems.
Previously in this list I asked about adding -mwindows to emacs-w32 build
process but that can lead to unknown errors so developers refused that option.
So I need to `run.exe` to hide console because it pollutes Alt+TAB menu as
additional useless item.
I believe that reason for emacs "failure" is exit of 'conhost'.
Any suggestion?
--
http://defun.work/
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
reply other threads:[~2017-06-12 12:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vriu37b5v070.fsf@gavenkoa.example.com \
--to=gavenkoa@gmail.com \
--cc=cygwin@cygwin.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.
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).