From: Jan Vroonhof <vroonhof@math.ethz.ch>
Subject: Re: 0x0a converted to 0x0d when saving attachments
Date: 03 Oct 1999 23:39:00 +0200 [thread overview]
Message-ID: <by4sg8nmyz.fsf@bolzano.math.ethz.ch> (raw)
In-Reply-To: Stainless Steel Rat's message of "Sun, 03 Oct 1999 16:53:25 GMT"
Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
> Hmm... I seem to recall that. This is one of FSF Emacs 20's stupidities:
> it assumes that if no coding system is set it *must* perform a conversion,
> which is just plain wrong.
I think you'll find that this is not limited to FSF Emacs. I think in
itself the idea that not specifying a coding system leads to
auto-detection is sound however the autodetection should be _much_
more conservative and for _non-files_ (or at least internet sockets)
the default should be 'binary.
> Of course, this caused XEmacs 20 to break because on "illegal" messages
> becaue no-conversion means something totally different. What a pain.
The joys of two teams, at least one of them manifestly not trying to
be compatible[1], working to implement the same manifestly
undocumented or even undefined API.
Jan
Footnotes:
[1] Note the careful positioning of 'not' in this sentence.
next prev parent reply other threads:[~1999-10-03 21:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-01 19:24 Mike Fabian
1999-10-01 20:22 ` Shenghuo ZHU
1999-10-01 21:50 ` Mike Fabian
1999-10-02 1:49 ` Shenghuo ZHU
1999-10-02 11:40 ` Mike Fabian
1999-10-02 17:51 ` Shenghuo ZHU
1999-10-03 14:37 ` Stainless Steel Rat
1999-10-03 15:43 ` Jan Vroonhof
1999-10-03 16:51 ` Stainless Steel Rat
1999-10-03 21:39 ` Jan Vroonhof [this message]
[not found] ` <byiu4oo3et.fsf@bolz <by4sg8nmyz.fsf@bolzano.math.ethz.ch>
1999-10-04 16:13 ` Stainless Steel Rat
1999-10-04 20:12 ` François Pinard
1999-10-05 11:42 ` Kai Großjohann
1999-10-05 13:42 ` Mike Fabian
1999-10-05 14:25 ` François Pinard
1999-10-05 17:13 ` Michael Welsh Duggan
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=by4sg8nmyz.fsf@bolzano.math.ethz.ch \
--to=vroonhof@math.ethz.ch \
/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 NNTP newsgroup(s).