From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: bug in calculation of line length again
Date: 24 Nov 1998 11:00:02 +0100 [thread overview]
Message-ID: <m33e79pg0t.fsf@sparky.gnus.org> (raw)
In-Reply-To: Shenghuo ZHU's message of "23 Nov 1998 14:37:10 -0500"
Shenghuo ZHU <zsh@cs.rochester.edu> writes:
> I do not really know whether it is or not. But it works for me. I
> would rather see meaningless 8-bit strings than strings containing
> lots of backslashes and numbers.
In this case, the user is "supposed" to see the backslashes and stuff,
because the buffer had been encoded before preparing to send it to the
world.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1998-11-24 10:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-23 8:02 Vladimir Volovich
1998-11-23 18:30 ` Shenghuo ZHU
1998-11-23 19:17 ` Vladimir Volovich
1998-11-23 19:37 ` Shenghuo ZHU
1998-11-24 10:00 ` Lars Magne Ingebrigtsen [this message]
1998-11-24 9:59 ` Lars Magne Ingebrigtsen
1998-11-24 13:49 ` Vladimir Volovich
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=m33e79pg0t.fsf@sparky.gnus.org \
--to=larsi@gnus.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.
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).