From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Daniele Nicolodi <daniele@grinta.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [ANN] Changes to link syntax
Date: Mon, 11 Mar 2019 17:35:10 +0100 [thread overview]
Message-ID: <87sgvtqsht.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <3cac7a28-47ce-3e07-9c5b-282fd9761ef9@grinta.net> (Daniele Nicolodi's message of "Sun, 10 Mar 2019 17:00:11 -0600")
Hello,
Daniele Nicolodi <daniele@grinta.net> writes:
> On 10/03/2019 11:19, Nicolas Goaziou wrote:
>> 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~.
>
> Aren't those two sentences slightly contradictory? If ~org-link-escape~
> has been renamed ~org-link-encode~ I think that the later should be
> mentioned in the first sentence.
The first paragraph is about the new `org-link-escape'. The second one
is about the old `org-link-escape', which has become `org-link-encode'.
Is that clearer?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2019-03-11 16:35 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 [this message]
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=87sgvtqsht.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=daniele@grinta.net \
--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).