This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Any progress on "Fork issues ith long command lines and long $PATH"?

Regarding my choice of terms: I was trying use terms consistent with that old link 

(1) So is there a fix for the problem described in this link "";? According to 
Corinna Vinschen's comments it is a Cygwin problem, not an emacs problem. I would love to have a fix.
(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.

Thank you

>On Tuesday, January 19, 2016 11:48 AM, Ken Brown <> wrote:
>On 1/19/2016 2:06 PM, Richard Heintze wrote:
>> Anyway, I'm getting very similar symptoms on cygwin64 with windows 10 with FSF emacs 23.2, 24.2& 24.5.

>By the way, some people might be confused by your phrase "FSF emacs". 
>You're talking about a native Windows build of emacs as opposed to a 
>Cygwin build of emacs.  Both are based on the same sources and have the 
>same connection to the FSF.


Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]