From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: \201 *waugh*
Date: 28 Dec 2000 19:48:56 +0100 [thread overview]
Message-ID: <vafofxwjs9z.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m3zohgb9sz.fsf@quimbies.gnus.org>
On 28 Dec 2000, Lars Magne Ingebrigtsen wrote:
> Now -- I insert lots of stuff into a unibyte buffer. I then use
> w3-parse on the stuff in the buffer.
I wonder: does w3-parse want to see a sequence of bytes or a sequence
of characters in the buffer? Maybe it helps to see what url.el
deposits in url-working-buffer.
kai
--
~/.signature
next prev parent reply other threads:[~2000-12-28 18:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-28 19:55 Lars Magne Ingebrigtsen
2000-12-28 18:27 ` ShengHuo ZHU
2000-12-28 22:10 ` Lars Magne Ingebrigtsen
2000-12-29 6:07 ` ShengHuo ZHU
2000-12-28 18:48 ` Kai Großjohann [this message]
2000-12-28 22:12 ` Lars Magne Ingebrigtsen
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=vafofxwjs9z.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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).