From: Hong Xu <hong@topbug.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 24694@debbugs.gnu.org
Subject: bug#24694: Document url--allow-chars for external use?
Date: Fri, 4 Oct 2019 12:31:27 -0700 [thread overview]
Message-ID: <7137f36f-983f-2e78-ebdc-4b2e277410a1@topbug.net> (raw)
In-Reply-To: <87oa0vtk3y.fsf@topbug.net>
On 12/1/16 1:28 PM, Hong Xu wrote:
>
> On 2016-10-14 Fri 12:02 GMT-0800, Eli Zaretskii <eliz@gnu.org> wrote:
>
>>> From: Hong Xu <hong@topbug.net>
>>> Date: Fri, 14 Oct 2016 11:24:52 -0700
>>>
>>> Currently url-hexify-string has an optional argument allowed-chars,
>>> which is a long vector. However, it is more natural to specify a list of
>>> characters. Internally, the default value of allowed-chars is specified
>>> by converting a list of chars to such a vector by using an internal
>>> function url--allow-chars. I would like to suggest to document
>>> url--allow-chars for external use, thus we can improve the interface of
>>> the url-hexify-string function.
>>>
>>> I can draft the document change, if you agree with me.
>>
>> Isn't it better to teach url-hexify-string to accept lists as well?
>
> The patch is attached.
>
> Make url-hexify-string accept a list of allowed chars.
>
> * url-util.el (url-hexify-string): Accept a list of allowed chars.
> * url.texi (URI Encoding): Update url-hexify-string doc and index improvements.
>
It's been a few years... I'm wondering whether this patch is still interesting?
next prev parent reply other threads:[~2019-10-04 19:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 18:24 bug#24694: Document url--allow-chars for external use? Hong Xu
2016-10-14 19:02 ` Eli Zaretskii
2016-10-14 19:36 ` Hong Xu
2016-12-01 21:28 ` Hong Xu
2019-10-04 19:31 ` Hong Xu [this message]
2019-10-11 12:38 ` Eli Zaretskii
2019-10-11 14:32 ` Robert Pluim
2019-10-12 2:21 ` Hong Xu
2019-10-12 9:11 ` Eli Zaretskii
2019-10-12 18:23 ` Hong Xu
2019-10-14 4:47 ` Lars 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=7137f36f-983f-2e78-ebdc-4b2e277410a1@topbug.net \
--to=hong@topbug.net \
--cc=24694@debbugs.gnu.org \
--cc=eliz@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.