From: Ken Brown <kbrown@cornell.edu>
To: Richard Heintze <sieg_heintze@yahoo.com>,
"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Any progress on "Fork issues ith long command lines and long $PATH"?
Date: Tue, 19 Jan 2016 23:37:00 -0000 [thread overview]
Message-ID: <569E92D1.9030506@cornell.edu> (raw)
In-Reply-To: <54233810.5967218.1453230386996.JavaMail.yahoo@mail.yahoo.com>
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.
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
next prev parent reply other threads:[~2016-01-19 19:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1452453272.4723872.1452908121695.JavaMail.yahoo.ref@mail.yahoo.com>
[not found] ` <1452453272.4723872.1452908121695.JavaMail.yahoo@mail.yahoo.com>
2016-01-16 20:09 ` Richard Heintze
2016-01-16 20:29 ` Ken Brown
2016-01-19 19:40 ` Richard Heintze
2016-01-19 22:40 ` Ken Brown
2016-01-19 23:37 ` Ken Brown [this message]
2016-01-20 1:26 ` Richard Heintze
2016-01-20 5:39 ` Ken Brown
2016-01-20 12:19 ` Andrey Repin
2016-01-20 18:32 ` Ken Brown
2016-01-20 23:45 ` cyg Simple
2016-01-21 9:10 ` Richard Heintze
2016-01-21 15:42 ` Ken Brown
2016-01-24 11:57 ` Ken Brown
[not found] ` <628638256.152717.1453783725662.JavaMail.yahoo@mail.yahoo.com>
2016-01-26 19:56 ` Ken Brown
[not found] ` <813797665.101723.1454369130463.JavaMail.yahoo@mail.yahoo.com>
2016-02-01 23:42 ` Richard Heintze
2016-02-02 2:52 ` Ken Brown
2016-02-12 23:41 ` Richard Heintze
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=569E92D1.9030506@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.com \
--cc=sieg_heintze@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).