From: "Eli Zaretskii" <eliz@gnu.org>
Subject: Re: How files should be saved, concerning type of line breaks
Date: Sat, 25 Sep 2004 18:29:21 +0200 [thread overview]
Message-ID: <01c4a31c$Blat.v2.2.2$f551b140@zahav.net.il> (raw)
In-Reply-To: <cj22pp$ckq$1@news.island.liu.se> (mikas493_no_spam@student.liu.se)
> From: "William Payne" <mikas493_no_spam@student.liu.se>
> Date: Fri, 24 Sep 2004 23:15:55 +0200
>
> Why do I want this? Well, when on Windows, I use a CVS version of Emacs that
> I compiled myself. Thus, being made for Windows, Emacs saves new files (or
> should I say buffers being written to disk) using windows style line breaks.
> However, I also use Cygwin which is set to work with *nix-style line breaks,
> that's why I want to change the default behaviour of Emacs.
>
> How do I solve this?
Look up the description of the untranslated-filesystem feature
described in the node "Text and Binary" of the Emacs manual.
prev parent reply other threads:[~2004-09-25 16:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-24 21:15 How files should be saved, concerning type of line breaks William Payne
2004-09-25 16:29 ` Eli Zaretskii [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='01c4a31c$Blat.v2.2.2$f551b140@zahav.net.il' \
--to=eliz@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).