X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:mime-version
	:content-type; q=dns; s=default; b=Yi23Y5K/sEx4jLOfa87z85mcCzWa2
	L1Fx8U0a8H6YOryiaf7FX5+kzZsQLrmC2+XAaagkBMgEGH/UDxAikk5iJXsvjrdH
	8MUlP08pXu2Q3HVpSJ3NH2r8OnhLfxEmH5SfQfKSkvqUF0x0dAjlCRuHekWLBo8u
	tCcTo+I8Zl6ZzQ=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:mime-version
	:content-type; s=default; bh=q3D931FbInLaSuU+CSeHri8E3hE=; b=E/+
	9F5lFqOpw161lSk6cjSB26iLrvttEpwZ7V8PJp0K7QwMsTt78m8AcFL2JhYWZK5K
	KHQ4EPfsmIuN0HxrPj6px/paYzCcLBri8a+dsshf9Ejq5U2G9lwKQPFcwdNcSO8O
	+WHVEyZUso7pFXPTaHix6QU4fKynHQ0WNZv+cIAA=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=1.8 required=5.0 tests=BAYES_20,FREEMAIL_FROM,KAM_LAZY_DOMAIN_SECURITY,KAM_OTHER_BAD_TLD autolearn=no version=3.3.2 spammy=Alt, Creators, creators, cmd.exe
X-HELO:	blaine.gmane.org
To:	cygwin AT cygwin DOT com
From:	Oleksandr Gavenko <gavenkoa AT gmail DOT com>
Subject:	run.exe + conhost + emacs-w32 / emacsclient-w32 problem.
Date:	Mon, 12 Jun 2017 15:51:15 +0300
Lines:	49
Message-ID:	<vriu37b5v070.fsf@gavenkoa.example.com>
Mime-Version:	1.0
User-Agent:	Gnus/5.13 (Gnus v5.13) Emacs/25.2 (cygwin)
X-IsSubscribed:	yes

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

- Raw text -