From: Tim Cross <email@example.com> To: firstname.lastname@example.org Subject: Re: URLs with brackets not recognised Date: Thu, 13 May 2021 12:21:01 +1000 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> Rudolf Adamkovič <email@example.com> writes: > Maxim Nikulin <firstname.lastname@example.org> writes: > >> 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. > > I disagree. URLs are well-specified. Per RFC 3986, the characters > allowed in a URL are [A-Za-z0-9\-._~!$&'()*+,;=:@\/?]. Org mode should > implement proper URL detection, not asking its users "to give it some > hints" and using "a kind of heuristics". A string either is a valid URL > per the relevant RFCs or it is not. > Limitations with plain text links are documented in the manual, with an explanation of why you need to use the org link insertion commands to created a valid link which escapes the problematic characters. As this is defined and documented behaviour, I don't see how it can be considered a bug. You might consider it a frustrating or even unnecessary limitation, but not a bug. I'm sure a patch which improves org handling of plain urls would be considered. However, previous attempts at such enhancements have either resulted in significant performance impact or unexpected and unwanted side effects. In short, this is a non-trivial problem to solve. As the need for such use cases in plain text links is a small use case and as you can have those links using org link syntax, it would be very hard to justify a patch which may have adverse performance impact for all users. This change could be considered a feature enhancement, but it is not a bug. -- Tim Cross
next prev parent reply other threads:[~2021-05-13 2:34 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-12 7:32 Colin Baxter 2021-05-12 10:38 ` Nick Savage 2021-05-12 11:58 ` Maxim Nikulin 2021-05-12 13:32 ` Colin Baxter 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 [this message] 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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: URLs with brackets not recognised' \ /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
Code repositories for project(s) associated with this 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).