This is the mail archive of the
mailing list for the Cygwin project.
Re: Any progress on "Fork issues ith long command lines and long $PATH"?
- From: Richard Heintze <sieg_heintze at yahoo dot com>
- To: Ken Brown <kbrown at cornell dot edu>, "cygwin at cygwin dot com" <cygwin at cygwin dot com>
- Date: Tue, 19 Jan 2016 23:34:45 +0000 (UTC)
- Subject: Re: Any progress on "Fork issues ith long command lines and long $PATH"?
- Authentication-results: sourceware.org; auth=none
- References: <569E92D1 dot 9030506 at cornell dot edu>
- Reply-to: Richard Heintze <sieg_heintze at yahoo dot com>
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 "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.
(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.
>On Tuesday, January 19, 2016 11:48 AM, Ken Brown <firstname.lastname@example.org> 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: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple