From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Incompatible changes regarding link Date: Fri, 06 Dec 2019 22:10:32 +0100 Message-ID: <87blslw46v.fsf@nicolasgoaziou.fr> References: <877e3979h1.fsf@gmail.com> <87o8wlw5wa.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:44019) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1idKs6-0003dH-1V for emacs-orgmode@gnu.org; Fri, 06 Dec 2019 16:10:43 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1idKs4-0003Is-C8 for emacs-orgmode@gnu.org; Fri, 06 Dec 2019 16:10:41 -0500 Received: from relay1-d.mail.gandi.net ([217.70.183.193]:54747) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1idKs4-00037v-4x for emacs-orgmode@gnu.org; Fri, 06 Dec 2019 16:10:40 -0500 In-Reply-To: (Kiwon Um's message of "Fri, 6 Dec 2019 21:55:24 +0100") 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: Kiwon Um Cc: emacs-orgmode@gnu.org Kiwon Um 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 href="https://www.youtube.com/">\[You Tube\] 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.