From: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gnu-emacs-bug@gnu.org
Subject: Re: decode_eol and inconsistent EOL
Date: Mon, 29 Apr 2002 07:46:00 +0300 (IDT) [thread overview]
Message-ID: <Pine.SUN.3.91.1020429074505.22112A-100000@is> (raw)
In-Reply-To: <5l662eipi3.fsf@rum.cs.yale.edu>
On 26 Apr 2002, Stefan Monnier wrote:
> I think all that we really care about is that the load+save trip is safe
> and that the content of the Emacs buffer looks "as right as possible".
The second part is the issue here: it's open to interpretation.
next prev parent reply other threads:[~2002-04-29 4:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E170n3M-0000tW-00@fencepost.gnu.org>
2002-04-25 19:21 ` decode_eol and inconsistent EOL Eli Zaretskii
2002-04-26 13:00 ` Stefan Monnier
2002-04-26 14:37 ` Stefan Monnier
2002-04-29 4:46 ` Eli Zaretskii [this message]
2002-04-29 12:59 ` Stefan Monnier
2002-04-29 18:00 ` Eli Zaretskii
2002-04-29 18:11 ` Stefan Monnier
2002-04-29 19:08 ` 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=Pine.SUN.3.91.1020429074505.22112A-100000@is \
--to=eliz@is.elta.co.il \
--cc=gnu-emacs-bug@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).