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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	q=dns; s=default; b=avqUXO5PkAhAJcxI/Gnt9W+XrV8TeOpYSJaVWl2LqsH
	XmlUxexl0i/4zEInQBkwv/1M456GUBVNVaFaks6nam4pM+LrM/ih8RWCr8IfIVua
	l2JMX0Zvtd69Osl7gYJCIkw7Fz51ryIefhsYqjdmcDW6ay/EyFbFf5qrtywFf624
	=
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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	s=default; bh=gI0X8/eH6sHmED43AxZbTlrlHzk=; b=lMhrFdnq/W7N6n0L5
	j50iZHW25lW7Kd72ISQiMqxXWUq6oVRetEd2SCeNYoF38dj9E13KPA3TIA7EIMU1
	zIU8un/GnyqhLxJbKCd/W87/Oy55Z8HoDz3Nb1ydTlFUclL7T4cc77gXP97IniEI
	JAbUxiP8sFqMdqSN1W3dQ7xoIQ=
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.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE,SPF_PASS autolearn=ham version=3.3.2
X-Received:	by 10.69.17.1 with SMTP id ga1mr11482389pbd.38.1377151553943; Wed, 21 Aug 2013 23:05:53 -0700 (PDT)
Message-ID:	<5215AA3D.4020604@gmail.com>
Date:	Thu, 22 Aug 2013 14:05:49 +0800
From:	Arthur Tu <arthur DOT jim DOT tu AT gmail DOT com>
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Differences in emacsclient-w32 and emacs-w32
References:	<CAOeMcq9_u9ehhwXjSPCNMGufYs82wH98TTYrRTnU_euHOeuasg AT mail DOT gmail DOT com>
In-Reply-To:	<CAOeMcq9_u9ehhwXjSPCNMGufYs82wH98TTYrRTnU_euHOeuasg@mail.gmail.com>

I have a registry file which works fine.

    Windows Registry Editor Version 5.00

    [HKEY_CLASSES_ROOT\*\shell\openWithEmacs]

    [HKEY_CLASSES_ROOT\*\shell\openWithEmacs\command]
    @="C:\\cygwin\\bin\\run.exe /usr/bin/bash.exe -l -c
    \"/usr/bin/emacsclient-w32.exe -c \\\"%1\\\" -a \\\"\\\"\""

Do notice that this only works with run version 1.29. I don't have time 
to fix the incompatibility with latest run 1.30.


On 8/22/2013 8:10 AM, Josh Hunsaker wrote:
> 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
>


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