emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Bastien <bastienguerry@googlemail.com>
Cc: Bernt Hansen <bernt@norang.ca>,
	emacs-orgmode@gnu.org, Tom Roche <Tom_Roche@pobox.com>
Subject: Re: Re: possible URI handling bug: verification and reporting?
Date: Mon, 3 Aug 2009 06:37:58 +0200	[thread overview]
Message-ID: <CCD54863-6F70-415F-9986-612FA12E0122@gmail.com> (raw)
In-Reply-To: <87y6q5iqt4.fsf@bzg.ath.cx>

On Jul 31, 2009, at 3:27 AM, Bastien wrote:

> Bernt Hansen <bernt@norang.ca> writes:
>> I think the parenthesis should be URL encoded to be a valid URL.
>> Change ( to %28 and ) to %29 and you get
>> http://dx.doi.org/10.1016/S1352-2310%2801%2900429-0
>> which works for me (at least it doesn't 404 anymore)
>> Gnus also stops the fontification at the ( so I don't think this is
>> org-mode specific.
> Org-mode explicitely excluded parentheses from `org-plain-link-re' so
> yes, it was org-mode specific.  And (browse-url-url-at-point) was not
> confused either by parentheses, so org-mode needed to be fixed (and
> perhaps Gnus needs too!)

The reason why Org (and probably GNUS) exclude parenthesis from
plain links it to make them good citizens in plain text.  Identifying
a plain link is a heuristic matter, and it seemed to me that
more often is a link the last thing in a pair of parenthesis than are
parenthesis part of a link.  To cover links with special characters,
Org has the <link> and [[link]] formats.

So I have reverted this change and will keep it this way unless
convinced/overruled by more discussion about the issue.

- Carsten

  reply	other threads:[~2009-08-03  4:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-30 21:36 possible URI handling bug: verification and reporting? Tom Roche
2009-07-30 21:54 ` Bernt Hansen
2009-07-31  1:27   ` Bastien
2009-08-03  4:37     ` Carsten Dominik [this message]
2009-07-31  1:25 ` Bastien

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:

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to=CCD54863-6F70-415F-9986-612FA12E0122@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=Tom_Roche@pobox.com \
    --cc=bastienguerry@googlemail.com \
    --cc=bernt@norang.ca \
    --cc=emacs-orgmode@gnu.org \


* 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


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).