From: speech.free@gmail.com
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs deadlocks on sub-process reads and writes
Date: Sun, 19 Oct 2014 08:26:00 -0700 (PDT) [thread overview]
Message-ID: <a91ed522-3d59-4d18-9970-4db6e56b53fa@googlegroups.com> (raw)
In-Reply-To: <mailman.11496.1413724706.1147.help-gnu-emacs@gnu.org>
Unfortunately I am not set up to build emacs myself. Is there an rc1 windows binary available somewhere? It is not on the official site yet. It is also not on your ezwinports site. I use msys2/mingw packages. According to a recent thread emacs does no yet build on my platform. My arch linux virtual box does not have X and I use telnet to connect to it. Emacs does not work well over a telnet link on mintty. If official release is just around the corner I can wait for that.
prev parent reply other threads:[~2014-10-19 15:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-19 1:48 Emacs deadlocks on sub-process reads and writes speech.free
2014-10-19 6:38 ` speech.free
2014-10-19 13:17 ` Eli Zaretskii
[not found] ` <mailman.11496.1413724706.1147.help-gnu-emacs@gnu.org>
2014-10-19 15:26 ` speech.free [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a91ed522-3d59-4d18-9970-4db6e56b53fa@googlegroups.com \
--to=speech.free@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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).