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:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=YDG/sBVr61JJ7xDt
	svj7oETTtsLxMiurejfX/ryfd5VEOqwsB83yRWkmuPi2cfVPGgY/I3u1lHmOSZUH
	xPjWkkXLyRzvUClqVWWqlhYVpSlkWHm5ZIX8ZVehu7XmEYgy2NnWhy0XF/GfTHMj
	AWKvO1ZmwQjSZNedlMNLESDDkoY=
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:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=9P3L6f4erkDrFcuRS43Uih
	ChwCg=; b=D2Z/xIzk6UHG1JjnQYRf5OW2jENElT8Aq6oGf+YulJr0onHMkjenaR
	XTMmRpNsia49cuxK8gA068qFn9vEhokG/esBFUK1Dlozb8Oo11QzrmY3Usy1TSt7
	LDZ6Q6AeFwEqUr55xNbBw1tXNCDaZOuig7dw4zqn6CKteD3dxKA4A=
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.2 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 spammy=cf, H*MI:sk:6416598, H*f:sk:6416598, H*i:sk:6416598
X-HELO: limerock03.mail.cornell.edu
X-CornellRouted: This message has been Routed already.
Subject: Re: Any progress on "Fork issues ith long command lines and long $PATH"?
To: Richard Heintze <sieg_heintze AT yahoo DOT com>,
        "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
References: <569E92D1 DOT 9030506 AT cornell DOT edu> <641659872 DOT 6133623 DOT 1453246485856 DOT JavaMail DOT yahoo AT mail DOT yahoo DOT com>
From: Ken Brown <kbrown AT cornell DOT edu>
Message-ID: <569EE230.2060600@cornell.edu>
Date: Tue, 19 Jan 2016 20:26:08 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <641659872.6133623.1453246485856.JavaMail.yahoo@mail.yahoo.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

[Please don't top post.]

On 1/19/2016 6:34 PM, Richard Heintze wrote:
> Regarding my choice of terms: I was trying use terms consistent with that old link
> "https://cygwin.com/ml/cygwin/2011-02/msg00416.html".

That message doesn't even mention emacs.  That's why I said in my first 
reply to you that I couldn't make much sense of what you wrote.

> (1) So is there a fix for the problem described in this link "https://cygwin.com/ml/cygwin/2011-02/msg00416.html"? According to
> Corinna Vinschen's comments it is a Cygwin problem, not an emacs problem. I would love to have a fix.

I still don't know the connection between that message and emacs.  Could 
you say exactly what problem you're having?

> (2) I was using $USERPROFILE as an example. We have dozens of these environment variables pointing to dozens directories. They enable us to type in the same file name to emacs's find file (ctrl-x-ctrl-f) regardless of who is logged in or which computer we are logged into (assuming that every account has the same directory structure and propertly defined environment variables).  Yes we can manually translate them at a bash prompt but this is a lot more typing, cutting and pasteing. We also share the same .emacs file that contains thousands of file names that contain these environment variables. We will really missing feature of native emacs.

The fact that C-x C-f expands environment variables is not a special 
feature of native Windows emacs.  But the expansion has to yield a valid 
file name.  In the case of Cygwin emacs, that means a Posix path.

Maybe you could write a script that uses cygpath to convert the relevant 
environment variables to Posix paths, and then call this script from 
your .bashrc.

Ken

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