From: "Eli Zaretskii" <eliz@elta.co.il>
Cc: emacs-devel@gnu.org
Subject: Re: Issues with Windows gcc -mno-cygwin (Mingw)
Date: Thu, 20 Mar 2003 06:30:17 +0200 [thread overview]
Message-ID: <2950-Thu20Mar2003063017+0200-eliz@elta.co.il> (raw)
In-Reply-To: <m3r893ylvu.fsf@cicero.benny.turtle-trading.net> (message from Benjamin Riefenstahl on 20 Mar 2003 00:31:01 +0100)
> From: Benjamin Riefenstahl <Benjamin.Riefenstahl@epost.de>
> Date: 20 Mar 2003 00:31:01 +0100
>
> > > From: Benjamin Riefenstahl <Benjamin.Riefenstahl@epost.de>
> > > - Problem with _fmode
>
> > Is this change only for the unexec phase, or for the entire Emacs
> > operation?
>
> For the entire operation. Emacs doesn't use O_BINARY directly to load
> files.
Oh yes, it does--at least in the DOS_NT versions. Grep the C sources
for _BINARY, and you will see it yourself.
So the only issue with binary I/O I'm aware of is with standard input
and output handles. That's why the code in emacs.c does what it does.
Note that switching stdin/stdout to binary mode might not be necessary
in the MinGW build; the DOS port does that because otherwise control
characters such as C-c and C-z are interpreted by the OS instead of
being passed directly to the application.
next prev parent reply other threads:[~2003-03-20 4:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-18 17:14 Issues with Windows gcc -mno-cygwin (Mingw) Benjamin Riefenstahl
2003-03-18 17:54 ` Eli Zaretskii
2003-03-19 23:31 ` Benjamin Riefenstahl
2003-03-20 4:30 ` Eli Zaretskii [this message]
2003-03-20 8:29 ` Jason Rumney
2003-03-20 16:21 ` Benjamin Riefenstahl
2003-03-18 18:26 ` Jason Rumney
2003-03-19 23:36 ` Benjamin Riefenstahl
-- strict thread matches above, loose matches on Subject: below --
2003-03-19 7:39 David PONCE
2003-03-19 8:41 ` Jason Rumney
2003-03-19 23:44 ` Benjamin Riefenstahl
2003-03-19 23:40 ` Benjamin Riefenstahl
2003-03-19 9:29 David PONCE
2003-05-14 7:27 David PONCE
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=2950-Thu20Mar2003063017+0200-eliz@elta.co.il \
--to=eliz@elta.co.il \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.