From: Dan Nicolaescu <dann@ics.uci.edu>
To: bug-gnu-emacs <bug-gnu-emacs@gnu.org>
Subject: bug#2136: cleanup: Fresume_tty and Fsuspend_tty
Date: Sat, 31 Jan 2009 10:46:45 -0800 (PST) [thread overview]
Message-ID: <200901311846.n0VIkjDJ011449@rodan.ics.uci.edu> (raw)
These functions should not have any #ifdef MSDOS or #ifdef subprocesses,
they cannot be used on such systems. That code is clearly untested anyway.
Or maybe the can just have an #ifndef MSDOS around the whole body that
makes them do nothing.
next reply other threads:[~2009-01-31 18:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-31 18:46 Dan Nicolaescu [this message]
2009-01-31 20:09 ` bug#2136: cleanup: Fresume_tty and Fsuspend_tty Eli Zaretskii
2009-01-31 20:14 ` Dan Nicolaescu
2009-01-31 20:40 ` Eli Zaretskii
2009-01-31 21:08 ` Eli Zaretskii
2013-02-06 19:08 ` Glenn Morris
2009-01-31 21:22 ` Dan Nicolaescu
2009-01-31 22:00 ` Eli Zaretskii
2009-02-01 3:43 ` Dan Nicolaescu
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=200901311846.n0VIkjDJ011449@rodan.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=2136@emacsbugs.donarmstrong.com \
--cc=bug-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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).