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:mime-version:date:message-id:subject:from:to
	:content-type; q=dns; s=default; b=WMprYUUlibYbJaBbcGEY9IHXZn02N
	x4UBYOgS/inQKmSeRVSaaVMXE+Rmt1lyCIxlpvmaHazDQqA+McCEeOC3vBuO8t94
	DDZSixVBUrpDlLaS3wtVS/i1nPesPXGZ/ZyUFg35WeVJp7bQola3dJoX9FCS+5Bq
	zdU1rEXzx+EHs8=
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:mime-version:date:message-id:subject:from:to
	:content-type; s=default; bh=T+Y4amJTNFmvsznXZBgjxcg9Waw=; b=CoG
	LVj1cLsVqqRQpUvc0h62tlRsB755iDytUIKxGgkmQ6wCA2nl+PNjOrfMBO6LvP8a
	hOCguONbTZy0THqDUuf+491Nu980BYqQz6Pf3teHhfNLgHnpWFqxS/v0zONdwwtS
	w/MedsSB6MNkURI17JGY9l9fk82Pq6eO1fmWyn1A=
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
X-Spam-SWARE-Status:	No, score=-2.3 required=5.0 tests=BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,SPF_PASS autolearn=ham version=3.3.2
MIME-Version:	1.0
X-Received:	by 10.14.99.193 with SMTP id x41mr56389eef.52.1377130234614; Wed, 21 Aug 2013 17:10:34 -0700 (PDT)
Date:	Wed, 21 Aug 2013 18:10:34 -0600
Message-ID:	<CAOeMcq9_u9ehhwXjSPCNMGufYs82wH98TTYrRTnU_euHOeuasg@mail.gmail.com>
Subject:	Differences in emacsclient-w32 and emacs-w32
From:	Josh Hunsaker <nispio86 AT gmail DOT com>
To:	cygwin AT cygwin DOT com

I am having a problem opening files in emacs from Windows, and I think
that the cygwin build of emacs is causing the problem.

I have an "Edit" option in my windows context menu that sends files to
emacs via a registry key with value:

C:\cygwin\bin\emacsclient-w32.exe "%1"

If I have no open instance of emacs, then it will be opened, and the
file will load into a new buffer as expected.  I can also repeat this
action for many files, and each will load into its own buffer in the
current emacs instance, as expected.

By contrast, if I start emacs with emacs-w32.exe, whether from the
terminal or by clicking the icon, I am unable to open files from the
context menu.  Instead, a new _empty_ buffer is created with a name
like "F:\Users\nispio\.emacs".  The value of 'buffer-file-name' for
this empty buffer is
"/cygdrive/f/Users/nispio/F:\\Users\\nispio\\.emacs"

I cannot reproduce this problem in the standalone Windows emacs build
from ftp.gnu.org. The binaries emacs.exe and emacsclientw.exe work as
expected in that build.  For now, I have a reasonable workaround in
that I can create my first instance of emacs by opening a file from
the context menu.  However, after that if I want to open a file from
the command-line I have to use

$ emacsclient-w32 `cygpath -w ~/.emacs`

or else I get a similar problem as mentioned above, but in reverse.
Is there any way that I can correct this so that I can more
efficiently open files in emacs from both the command line and Windows
Explorer?

--
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 -