From: dewar@gnat.com
To: jsturm@one-point.com, paullimjh@hotmail.com
Cc: gcc-help@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: Help : File does not end with newline
Date: Sun, 30 Sep 2001 10:02:00 -0000 [thread overview]
Message-ID: <20010930165842.2ACA6F2B7A@nile.gnat.com> (raw)
<<Not directly. But Windows does seem to have a plethora of broken editor
software. Try to open/save this file in another source code editor, such
as emacs or even Windows Notepad.
>>
Note that it is entirely within normal Windows standards for the last
character in the file to be 0x1A, you can even argue that this is the
standard format, so many editors in Windows put this character there,
but typical Unix software is not setup to properly handle this end
of file character on Windows, so perhaps that is the problem.
next reply other threads:[~2001-09-30 10:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-30 10:02 dewar [this message]
2001-09-30 14:47 ` Zack Weinberg
-- strict thread matches above, loose matches on Subject: below --
2001-09-30 17:44 Paul Lim
2001-09-30 18:21 ` Zack Weinberg
2001-09-30 9:26 Paul Lim
2001-09-30 9:44 ` Jeff Sturm
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=20010930165842.2ACA6F2B7A@nile.gnat.com \
--to=dewar@gnat.com \
--cc=gcc-help@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jsturm@one-point.com \
--cc=paullimjh@hotmail.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).