From: stardiviner <numbchild@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [ANN] Changes to link syntax
Date: Fri, 15 Mar 2019 13:23:02 +0800 [thread overview]
Message-ID: <87h8c490eh.fsf@gmail.com> (raw)
In-Reply-To: <87sgvusl43.fsf@nicolasgoaziou.fr>
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Hello,
>
> I finally pushed changed about escape syntax in bracket links. Here is
> the excerpt from ORG-NEWS:
>
> Org used to percent-encode sensitive characters in the URI part of the
> bracket links.
>
> Now, escaping mechanism uses the usual backslash character, according
> to the following rules, applied in order:
>
> 1. All consecutive =\= characters at the end of the link must be
> escaped;
> 2. Any =]= character at the very end of the link must be escaped;
> 3. Any =]= character followed by either =[= or =]= must be escaped;
> 4. Other =]= and =\= characters need not be escaped.
>
> When in doubt, use the function ~org-link-escape~ in order to turn
> a link string into its properly escaped form.
>
> The old ~org-link-escape~ and ~org-link-unescape~ functions have
> been renamed into ~org-link-encode~ and ~org-link-decode~.
>
> I added a checker in "org-lint.el" to detect old percent-encoding escape
> syntax in links.
>
> Internally, I also moved all link related code from "org.el" to "ol.el",
> and renamed libraries defining a new link type with "ol-" prefix. (e.g.
> "org-bbdb.el" to "ol-bbdb.el"), much like "ox-" prefix.
>
> Feedback is welcome.
>
> Regards,
Hi, @Nicolas, will you release a method to update all existing Org file links?
(Sorry for second time asking this, you have not mentioned it, so I asked again,
it's important for me, or people who want to upgrade to new link syntax).
I don't know which special escaped characters need to be converted.
If someone already has command to do this. Can you share it?
I'm still using a separate local branch which before this commit, so all my Org
file links still can work temporarily.
--
[ stardiviner ]
I try to make every word tell the meaning what I want to express.
Blog: https://stardiviner.github.io/
IRC(freenode): stardiviner, Matrix: stardiviner
GPG: F09F650D7D674819892591401B5DF1C95AE89AC3
next prev parent reply other threads:[~2019-03-15 5:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-10 17:19 [ANN] Changes to link syntax Nicolas Goaziou
2019-03-10 20:02 ` Samuel Wales
2019-03-10 22:13 ` Amin Bandali
2019-03-12 13:44 ` Nicolas Goaziou
2019-03-10 23:00 ` Daniele Nicolodi
2019-03-11 16:35 ` Nicolas Goaziou
2019-03-11 17:06 ` Eric S Fraga
2019-03-11 17:31 ` Daniele Nicolodi
2019-03-11 17:27 ` Marco Wahl
2019-03-11 18:00 ` Diego Zamboni
2019-03-11 23:07 ` Nicolas Goaziou
2019-03-12 5:42 ` Diego Zamboni
2019-03-15 5:23 ` stardiviner [this message]
2019-03-15 10:55 ` Nicolas Goaziou
2019-03-18 1:04 ` stardiviner
2019-03-18 21:33 ` Nicolas Goaziou
2019-03-19 8:06 ` stardiviner
2019-03-15 11:55 ` Nicolas Goaziou
2019-03-26 9:08 ` stardiviner
2019-03-27 2:00 ` stardiviner
2019-04-02 21:16 ` Nicolas Goaziou
2019-04-07 11:20 ` stardiviner
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=87h8c490eh.fsf@gmail.com \
--to=numbchild@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).