From mboxrd@z Thu Jan 1 00:00:00 1970 From: stardiviner Subject: Re: [ANN] Changes to link syntax Date: Fri, 15 Mar 2019 13:23:02 +0800 Message-ID: <87h8c490eh.fsf@gmail.com> References: <87sgvusl43.fsf@nicolasgoaziou.fr> Reply-To: numbchild@gmail.com Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([209.51.188.92]:59196) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h4fJJ-0003zh-RA for emacs-orgmode@gnu.org; Fri, 15 Mar 2019 01:23:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h4fJH-00041W-U2 for emacs-orgmode@gnu.org; Fri, 15 Mar 2019 01:23:13 -0400 Received: from [61.175.244.13] (port=15765 helo=dark.localdomain) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h4fJE-0003yF-GR for emacs-orgmode@gnu.org; Fri, 15 Mar 2019 01:23:10 -0400 In-reply-to: <87sgvusl43.fsf@nicolasgoaziou.fr> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org Nicolas Goaziou 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