From: Colin Baxter <m43cap@yandex.com>
To: Maxim Nikulin <manikulin@gmail.com>
Cc: , emacs-orgmode@gnu.org
Subject: Re: URLs with brackets not recognised
Date: Wed, 12 May 2021 14:32:59 +0100 [thread overview]
Message-ID: <87h7j82i2c.fsf@yandex.com> (raw)
In-Reply-To: <s7gftd$q9i$1@ciao.gmane.io> (Maxim Nikulin's message of "Wed, 12 May 2021 18:58:35 +0700")
>>>>> Maxim Nikulin <manikulin@gmail.com> writes:
> On 12/05/2021 17:38, Nick Savage wrote:
>> I can confirm this as a bug.
>> On 5/12/21 3:32 AM, Colin Baxter wrote:
>>> https://en.wikipedia.org/wiki/Cathedral_Basilica_of_St._John_the_Baptist_(Savannah,_Georgia)
> I do not think it is a bug. Plain text links detection is a kind
> of heuristics. It will be always possible to win competition with
> regexp. Consider it as a limitation requiring some hints from an
> intelligent user.
> Do the following links have the same problem?
> -
> <https://en.wikipedia.org/wiki/Cathedral_Basilica_of_St._John_the_Baptist_(Savannah,_Georgia)>
> -
> [[https://en.wikipedia.org/wiki/Cathedral_Basilica_of_St._John_the_Baptist_(Savannah,_Georgia)]]
> Support of parenthesis exists, but it is not perfect. Punctuation
> often should be outside of URL.
Point taken.
On the other hand, there has been a series of posts on emacs-devel asking
how emacs could be made more user-friendly. Perhaps therefore not
requiring a user to consider how to enter a URL might be useful.
Best wishes,
next prev parent reply other threads:[~2021-05-12 13:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 7:32 URLs with brackets not recognised Colin Baxter
2021-05-12 10:38 ` Nick Savage
2021-05-12 11:58 ` Maxim Nikulin
2021-05-12 13:32 ` Colin Baxter [this message]
2021-05-12 16:44 ` Colin Baxter
2021-05-12 20:06 ` Rudolf Adamkovič
2021-05-12 22:23 ` Tom Gillespie
2021-05-13 2:21 ` Tim Cross
2021-05-13 16:30 ` Maxim Nikulin
2021-05-13 1:25 ` Ihor Radchenko
2021-05-13 5:50 ` Colin Baxter
2021-05-15 9:06 ` Bastien
2021-05-15 9:29 ` Ihor Radchenko
2021-05-15 9:30 ` Ihor Radchenko
2021-05-15 9:47 ` 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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=87h7j82i2c.fsf@yandex.com \
--to=m43cap@yandex.com \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@gmail.com \
/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/org-mode.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).