From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: How to change line endings - where is it explained?
Date: Fri, 12 May 2006 20:57:24 +0300 [thread overview]
Message-ID: <uhd3v6s8r.fsf@gnu.org> (raw)
In-Reply-To: <44602D3B.3000309@student.lu.se> (message from Lennart Borgman on Tue, 09 May 2006 07:48:43 +0200)
> Date: Tue, 09 May 2006 07:48:43 +0200
> From: Lennart Borgman <lennart.borgman.073@student.lu.se>
> CC: emacs-devel@gnu.org
>
> > Yes, it is described in the node "Text and Binray".
> >
> > What did you try to look for it? Perhaps we need to improve the
> > indexing.
> >
> Thanks, yes I wonder why I missed that. A couple of small things perhaps:
>
> - The name of the node is a bit "C style".
> - I looked for "line endings".
> - I looked for "line end conversion".
> - I actually also searched for CRLF, but possibly only in the elisp
> manual since I wanted to do the conversion in code.
> - I was thinking about coding systems, but somehow I missed that you
> could use just 'unix or 'dos for the coding system in some operations.
> - I looked at the node "(emacs) Files" which says it tells everything
> about files.
> - I looked at `buffer-file-coding-system' etc.
I added some index entries that should make this search easier.
> Some suggestions:
>
> - A link to "(emacs) Coding Systems" in "(emacs) Files".
There is already such a link: see the node "Visiting".
> - Something about line endings too in "(emacs) Files", possibly in
> connection with the link above.
Ditto: "Visiting" already talks about EOLs.
> - "(emacs) Coding Systems" should mention 'dos, 'unix and 'mac.
It already does, please take a closer look.
> - "(elisp) Files" should mention line endings.
I added the references to code and EOL conversions to the appropriate
sections of files.texi.
> - `describe-coding-system' could somehow mention line endings.
Done.
next prev parent reply other threads:[~2006-05-12 17:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-08 22:45 How to change line endings - where is it explained? Lennart Borgman
2006-05-09 3:45 ` Eli Zaretskii
2006-05-09 5:48 ` Lennart Borgman
2006-05-12 17:57 ` Eli Zaretskii [this message]
2006-05-14 20:17 ` Lennart Borgman
2006-05-14 20:29 ` Eli Zaretskii
2006-05-14 21:00 ` Lennart Borgman
2006-05-15 3:14 ` Eli Zaretskii
2006-05-15 20:37 ` Richard Stallman
2006-05-09 5:51 ` Lennart Borgman
2006-05-09 19:35 ` Eli Zaretskii
2006-05-09 19:41 ` Lennart Borgman
2006-05-09 22:04 ` Luc Teirlinck
2006-05-10 3:36 ` Eli Zaretskii
2006-05-10 5:49 ` Lennart Borgman
2006-05-11 3:44 ` Richard Stallman
2006-05-11 18:29 ` Eli Zaretskii
2006-05-12 14:34 ` Eli Zaretskii
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=uhd3v6s8r.fsf@gnu.org \
--to=eliz@gnu.org \
--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 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).