emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Org Mode List <emacs-orgmode@gnu.org>
Subject: [ANN] Changes to link syntax
Date: Sun, 10 Mar 2019 18:19:24 +0100	[thread overview]
Message-ID: <87sgvusl43.fsf@nicolasgoaziou.fr> (raw)

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,

-- 
Nicolas Goaziou

next             reply	other threads:[~2019-03-10 17:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-10 17:19 Nicolas Goaziou [this message]
2019-03-10 20:02 ` [ANN] Changes to link syntax 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
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=87sgvusl43.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --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

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