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=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
MIME-Version: 1.0
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
Content-Type: text/plain; charset=ISO-8859-1

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