[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Incompatible changes regarding link

From: Kiwon Um
Subject: Re: Incompatible changes regarding link
Date: Fri, 6 Dec 2019 22:45:11 +0100

On Fri, Dec 6, 2019 at 10:10 PM Nicolas Goaziou <address@hidden> wrote:
> Kiwon Um <address@hidden> 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.

I understand Org-mode has its syntax. I am not saying Org-mode should
be able to do everything we want. As you already agreed, I'm just not
sure whether it's the best. In my opinion, one of the great advantages
of Org-mode is that we can do a lot of things with plain texts, and
here I am just little bit unhappy with using hidden characters to
escape something, particularly in a plane text file.

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

Right, that seems to be the only option for now. I may use zero width
spaces or other parentheses around links.
Thank you for your time again.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]