From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juanma Barranquero'" <lekktu@gmail.com>
Cc: "'Stephen J. Turnbull'" <stephen@xemacs.org>,
emacs-devel@gnu.org, 'Jason Rumney' <jasonr@gnu.org>
Subject: RE: mode line eol char indication
Date: Thu, 1 Jan 2009 11:15:47 -0800 [thread overview]
Message-ID: <007a01c96c45$5ad74390$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <f7ccd24b0901011017o3c8e392t5eaa828003e16a07@mail.gmail.com>
> > So you are arguing that it is the system/platform name that
> > is more meaningful to users, not the eol characters. I'm OK with that.
>
> I'm not. \n, \r and \r\n (or ^J, etc) are exact: what they say is what
> the file contains. "Unix", "DOS" and "Mac" are just hints about the
> likely origin. Is not like it is impossible to create CRLF files under
> GNU/Linux, or LF files on Windows.
I think I already said that my preference too is to show the eol chars, and I
agree with your reason. This is about the buffer content, after all, not
necessarily about a platform.
I'm OK however with either approach - whichever most people prefer. But we
should stick to one of them. It makes little sense to have sometimes `(DOS)' and
sometimes `\', which mean the same thing.
next prev parent reply other threads:[~2009-01-01 19:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-31 22:50 mode line eol char indication Drew Adams
2009-01-01 1:20 ` Jason Rumney
2009-01-01 5:44 ` Drew Adams
2009-01-01 8:33 ` Stephen J. Turnbull
2009-01-01 8:39 ` Jason Rumney
2009-01-01 18:11 ` Drew Adams
2009-01-01 18:17 ` Juanma Barranquero
2009-01-01 19:14 ` David De La Harpe Golden
2009-01-01 19:25 ` Drew Adams
2009-01-02 3:44 ` Stefan Monnier
2009-01-01 19:15 ` Drew Adams [this message]
2009-01-01 18:11 ` Drew Adams
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='007a01c96c45$5ad74390$0200a8c0@us.oracle.com' \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=jasonr@gnu.org \
--cc=lekktu@gmail.com \
--cc=stephen@xemacs.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.