From: Piet van Oostrum <piet@cs.uu.nl>
Subject: Re: Another issue with thingatpt
Date: Fri, 29 Dec 2006 22:23:55 +0100 [thread overview]
Message-ID: <m28xgqtmz8.fsf@ordesa.lan> (raw)
In-Reply-To: <17810.55182.483602.421178@rgrjr.dyndns.org>
>>>>> Bob Rogers <rogers-emacs@rgrjr.dyndns.org> (BR) wrote:
>BR> From: Werner LEMBERG <wl@gnu.org>
>BR> Date: Wed, 27 Dec 2006 11:50:42 +0100 (CET)
>BR> Here's another problematic URL:
>BR> http://mousai.kanji.zinbun.kyoto-u.ac.jp/ids-find?components=&U+20207;
>BR> thingatpt ignores the final `;'.
>BR> Werner
>BR> According to RFC3986 (aka STD066), this is wrong; ";" is legitimate
>BR> anywhere in a path or query part, including the end. So are "." and
>BR> ",", but thing-at-point-url-path-regexp also refuses to match these
>BR> characters at the end of the string. Doing (ffap-string-at-point 'url)
>BR> drops these characters plus ":", "!", and (questionably) "?".
>BR> It may not be possible to find a tradeoff between RFC compliance and
>BR> parsing dwimmery that would satisfy everybody. Since stripping off
>BR> trailing punctuation is useful behavior (ISTR it's worked this way for a
>BR> while now), I would recommend against changing it now. However, a case
>BR> could be made for making thing-at-point and ffap-string-at-point
>BR> consistent. Perhaps "!:;.," would be best? This is just the union of
>BR> the two sets but without the dubious inclusion of "?".
The way to reconcile these would be to customize it, I think. For example
have a string variable that contains the punctuation characters to be
included at the end. Or a regexp.
By the way, thing-at-point-url-path-regexp also disallows : inside a url.
These would be necessary to accept IPv6 IP addresses.
--
Piet van Oostrum <piet@cs.uu.nl>
URL: http://www.cs.uu.nl/~piet [PGP 8DAE142BE17999C4]
Private email: piet@vanoostrum.org
next prev parent reply other threads:[~2006-12-29 21:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <003001c727be$349c5a80$0203a8c0@HomeNetbbb0>
[not found] ` <20061225.094150.13771816.wl@gnu.org>
[not found] ` <htx7iwdn717.fsf@urania.kanji.zinbun.kyoto-u.ac.jp>
2006-12-27 10:50 ` Another issue with thingatpt Werner LEMBERG
2006-12-27 20:29 ` Bob Rogers
2006-12-28 6:39 ` Werner LEMBERG
2006-12-29 21:23 ` Piet van Oostrum [this message]
2006-12-31 3:08 ` Bob Rogers
2006-12-31 9:25 ` Andreas Roehler
2006-12-31 17:24 ` Bob Rogers
2007-01-02 13:34 ` Andreas Roehler
2007-01-03 14:50 ` Andreas Roehler
2006-12-31 20:07 ` Piet van Oostrum
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=m28xgqtmz8.fsf@ordesa.lan \
--to=piet@cs.uu.nl \
/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.