From: Leif Strand <leif@geodynamics.org>
To: bug-gnu-emacs@gnu.org
Subject: bug#4924: Emacs No Longer Reads Mac Text Files
Date: Fri, 13 Nov 2009 17:38:22 -0800 [thread overview]
Message-ID: <4AFE0A0E.4050709@geodynamics.org> (raw)
Dear Emacs maintainers,
Why is it that my new version of Emacs (v23.1.50.1) no longer
understands Mac-format (CR) text files? It still reads DOS (CRLF) files
just fine. Why remove support for one but not the other?
It is impossible to imagine that Mac format text files were a
maintenance burden. What is the point of gleefully deleting working
code that was causing zero problems?
I see an upgrade to Emacs v21 in my future.
--Leif Strand
next reply other threads:[~2009-11-14 1:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-14 1:38 Leif Strand [this message]
2009-11-16 1:16 ` bug#4924: Emacs No Longer Reads Mac Text Files Kenichi Handa
[not found] ` <4B01B0FC.4090505@geodynamics.org>
2009-11-17 1:33 ` Kenichi Handa
2009-11-17 2:13 ` Leif Strand
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=4AFE0A0E.4050709@geodynamics.org \
--to=leif@geodynamics.org \
--cc=4924@emacsbugs.donarmstrong.com \
--cc=bug-gnu-emacs@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).