From: Jan Vroonhof <vroonhof@math.ethz.ch>
Subject: Re: pop server access?
Date: 04 Nov 1998 19:00:08 +0100 [thread overview]
Message-ID: <byzpa79w47.fsf@bolzano.math.ethz.ch> (raw)
In-Reply-To: Stainless Steel Rat's message of "Wed, 04 Nov 1998 15:54:37 GMT"
Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
> I dunnow which is worse, FSF Emacs for being st00pid, or XEmacs for being
> st00pid in a diametrically opposed fashion.
[I think in this case FSF for being a changing target to stay
compatible with and ignoring the prior mule implementation in Xemacs.
However it does't really matter.]
Sigh, it just that
there is
binary -- Fully transparant
raw-text -- just EOL conversion
These work in both Emacsen.
On FSF Emacs no-conversion == binary and the documentation talks about
no-conversion in that context.
On FSF XEmacs no-conversion == raw-text and the documentation talks about
no-conversion in that context (minibuffer also shows the raw text
coding system as NoConv).
So if we could just get both .texi files to just talk about binary and
raw-text and let no-conversion die that would be very nice.
Jan
P.S. To add to your pain there is also EOL conversion in non-mule
Emacsen (for DOS/Win support).
next prev parent reply other threads:[~1998-11-04 18:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-20 10:53 Norbert Koch
1998-10-20 17:57 ` Lars Magne Ingebrigtsen
1998-10-22 5:21 ` Norbert Koch
[not found] ` <x7yaq8gpp8.fsf@peorth.gweep.net>
1998-10-23 4:39 ` Norbert Koch
[not found] ` <x7emry3jcc.fsf@peorth.gweep.net>
1998-10-25 11:54 ` Norbert Koch
[not found] ` <x7zpak5fgp.fsf@peorth.gweep.net>
1998-10-26 6:02 ` Norbert Koch
[not found] ` <x7btmyyk3x.fsf@peorth.gweep.net>
1998-10-27 13:18 ` Norbert Koch
1998-11-04 7:47 ` Shenghuo ZHU
[not found] ` <x7u30fpi7v.fsf@peorth.gweep.net>
1998-11-04 18:00 ` Jan Vroonhof [this message]
[not found] ` <x790ia3thq.fsf@peorth.gweep.net>
1998-10-22 7:14 ` Urban Engberg
1998-10-22 7:22 ` Urban Engberg
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=byzpa79w47.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).