From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Kiwon Um <um.kiwon@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Incompatible changes regarding link
Date: Fri, 06 Dec 2019 22:10:32 +0100 [thread overview]
Message-ID: <87blslw46v.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAKBDj42f=NOSrHaHpFww7q0hjjgWQ4crGWa+-T90pcYXxeA2iw@mail.gmail.com> (Kiwon Um's message of "Fri, 6 Dec 2019 21:55:24 +0100")
Kiwon Um <um.kiwon@gmail.com> writes:
> I didn't know what the issue in the past interpretation was, but I am
> just not sure whether it's a good idea to enforce that we must use
> such a special character, which we cannot directly see from the
> editor.
This is because you are using an ambiguous construct. There are things
you cannot do in Org (e.g., starting a line with "|" and expect it to be
something else than a table), yet, Org provides a syntax to work around
the problem. I agree this is not perfect.
>> > [[https://somewhere-to-url][[My Link]]] is not properly exported; the
>> > closing bracket "]" is not included in the exported link.
>>
>> This looks like a different problem. If you want to include the
>> brackets, you need to escape them, as explained in the ORG-NEWS
>> document, or in the manual:
>>
>> [[https://somewhere-to-url][\[My Link\]]]
>
> Unfortunately, this doesn't work either.
> [[https://www.youtube.com/][\[You Tube\]]] is exported as <a
> href="https://www.youtube.com/">\[You Tube\</a>]
Indeed! I forgot about that: the escaping mechanism is for the link
part. For the description part, you have to use a zero width space, too.
Note that `org-insert-link' (C-c C-l) does that automatically.
IIRC, square brackets were forbidden in descriptions (and changed into
curly brackets automatically) before that change.
next prev parent reply other threads:[~2019-12-06 21:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 15:35 Incompatible changes regarding link Kiwon Um
2019-12-06 20:33 ` Nicolas Goaziou
2019-12-06 20:55 ` Kiwon Um
2019-12-06 21:10 ` Nicolas Goaziou [this message]
2019-12-06 21:45 ` Kiwon Um
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=87blslw46v.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=um.kiwon@gmail.com \
/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).