From: Steinar Bang <sb@metis.no>
Subject: Silent, automatic conversion of line endings (Was: Sharing...)
Date: 10 Nov 1998 09:57:31 +0100 [thread overview]
Message-ID: <whemrc53ic.fsf_-_@viffer.oslo.metis.no> (raw)
In-Reply-To: Kurt Swanson's message of "Mon, 09 Nov 1998 15:14:13 GMT"
>>>>> Kurt Swanson <ksw@dna.lth.se>:
>> What about the file types, though? Maybe you have M$-ish CRLF
>> end-of-lines where Linux expects LF?
> Doesn't emacs take care of this silently and automatically?
*Too* silently! I messed up when doing a CVS import over an old
version from UNIX, but with the new version packaged on Win32.
I couldn't understand what was wrong, because the files looked fine in
Emacs, which has always told me that the file was a DOS file by
displaying the ^M characters or by putting a small "dos-mode" on the
status line.
What was more confusing than anything, was that the little bugger
(20.2 MBSK) *showed* the ^M characters in buffers that had both
UNIX and DOS line endings on different lines.
Arrrgh!
prev parent reply other threads:[~1998-11-10 8:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-09 14:41 Sharing GNUS between NT/Linux Jeremy Zawodny
1998-11-09 15:03 ` Kai.Grossjohann
[not found] ` <6fww5499vg.fsf@dna.lth.se>
1998-11-10 8:57 ` Steinar Bang [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=whemrc53ic.fsf_-_@viffer.oslo.metis.no \
--to=sb@metis.no \
/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 NNTP newsgroup(s).