This is the mail archive of the
cygwin
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 19:06:26 +0000 (UTC)
- Subject: Re: Any progress on "Fork issues ith long command lines and long $PATH"?
- Authentication-results: sourceware.org; auth=none
- References: <569AA38E dot 7040205 at cornell dot edu>
- Reply-to: Richard Heintze <sieg_heintze at yahoo dot com>
Thanks. Here is the missing link:
https://cygwin.com/ml/2011-02/msg00416.html .
Wow! that is link very old. I hope that means that someone has a fix!
Anyway, I'm getting very similar symptoms on cygwin64 with windows 10 with FSF emacs 23.2, 24.2& 24.5. I don't have this problem on cygwin32 and windows 8.1.
I also do not get this problem with Cygwin emacs-w32 on windows 10 with cygwin64 (strangely enough).
Unfortunately, the following file name (for example) works with fsf emacs and not Cygwin emacs-w32:
$USERPROFILE/Documents/hello.txt
Even some bash commands accept this but emacs-w32 does not.
I use these environment variables extensively to facilitate moving between different windows logins.
Thanks
Siegfrie
On Saturday, January 16, 2016 12:10 PM, Ken Brown <kbrown@cornell.edu> wrote:
On 1/16/2016 2:38 PM, Richard Heintze wrote:
>
>
>
> On Friday, January 15, 2016 5:35 PM, Richard Heintze <sieg_heintze@yahoo.com> wrote:
>
> regarding: https://cygwin.com/ml/cygwin/2011-02/msg00416.html
>
> I'm getting similar errors (see link below) but only on Windows 10 with Cygwin 64.
You seem to have omitted the link.
> When I use Cygwin emacs instead of FSF emacs I do not get this error on Windows 10.
> Unfortunately, Cygwin emacs does not allow me to make extensive use of my my environment variables embedded in file path/names like the windows version of FSF emacs does. This is a major problem!
What do you mean by "environment variables embedded in file path/names"?
> I do not get this error with windows 8 and Cygwin32.
>
> Do you think installing cygwin32 on Windows 10 would solve the problem? If it does not solve the problem, can I uninstalling cygwin32 by just deleting c\:Cygwin?
>
> Has this been reported as a bug? Has any progress been made on fixing it?
I can't make much sense out of what you wrote, but I'm responding as
Cygwin's emacs maintainer. Is there some emacs problem I can help you
with? If so, please make a complete, self-contained report.
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
--
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