unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 24694@debbugs.gnu.org, Hong Xu <hong@topbug.net>
Subject: bug#24694: Document url--allow-chars for external use?
Date: Fri, 11 Oct 2019 16:32:35 +0200	[thread overview]
Message-ID: <m2o8yn4akc.fsf@gmail.com> (raw)
In-Reply-To: <83r23jpidw.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 11 Oct 2019 15:38:03 +0300")

>>>>> On Fri, 11 Oct 2019 15:38:03 +0300, Eli Zaretskii <eliz@gnu.org> said:

    >> From: Hong Xu <hong@topbug.net>
    >> Cc: 24694@debbugs.gnu.org
    >> Date: Fri, 4 Oct 2019 12:31:27 -0700
    >> 
    >> > 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?

    Eli> I think it is, yes.  Can you send a patch relative to the current
    Eli> master branch?

Api nit: if the first argument is going to be a list or a vector, you
could just keep one argument and check 'vectorp'.

Robert





  reply	other threads:[~2019-10-11 14:32 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
2019-10-11 12:38       ` Eli Zaretskii
2019-10-11 14:32         ` Robert Pluim [this message]
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2o8yn4akc.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=24694@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=hong@topbug.net \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).