From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: shr.el - browse-url-url-encode-chars problem
Date: Tue, 05 Oct 2010 10:16:21 +0900 [thread overview]
Message-ID: <b4miq1he8wq.fsf@jpl.org> (raw)
In-Reply-To: <b4m1v85fp66.fsf@jpl.org>
Katsumi Yamaoka wrote:
> Lars Magne Ingebrigtsen wrote:
>> CHENG Gao <chenggao@cyberhut.org> writes:
>>> Guess shr.el need require browse-url.el or make
>>> browse-url-url-encode-chars autoload.
>> Yes, this has been fixed recently.
> Neither Emacs 22 nor XEmacs provides browse-url-url-encode-chars.
> I've introduced `shr-encode-url-chars' that's a copy of it.
Oops. I'll revert it later, since shr.el is for only Emacsen
having `libxml-parse-html-region' support.
How about excluding shr.el from the byte-compilation in `make'?
next prev parent reply other threads:[~2010-10-05 1:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 17:19 CHENG Gao
2010-10-04 17:25 ` Lars Magne Ingebrigtsen
2010-10-05 0:39 ` Katsumi Yamaoka
2010-10-05 1:16 ` Katsumi Yamaoka [this message]
2010-10-05 1:29 ` Katsumi Yamaoka
2010-10-05 16:41 ` 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=b4miq1he8wq.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@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).