From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: link recognition in orgmode Date: Wed, 06 Sep 2017 12:44:41 +0200 Message-ID: <87fuc014yu.fsf@nicolasgoaziou.fr> References: <8760cwna12.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36812) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dpXpB-00055c-BE for emacs-orgmode@gnu.org; Wed, 06 Sep 2017 06:44:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dpXp6-0002Ou-NE for emacs-orgmode@gnu.org; Wed, 06 Sep 2017 06:44:49 -0400 Received: from relay2-d.mail.gandi.net ([217.70.183.194]:60923) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dpXp6-0002OD-Gs for emacs-orgmode@gnu.org; Wed, 06 Sep 2017 06:44:44 -0400 In-Reply-To: (John Kitchin's message of "Tue, 05 Sep 2017 20:29:34 -0700") 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: John Kitchin Cc: "emacs-orgmode@gnu.org" Hello, John Kitchin writes: > The reason this came up is related to restructured text in a src block > docstring. For example, using > http://sphinxcontrib-bibtex.readthedocs.io/en/latest/usage.html#roles-and-directives, > one can write: "See :cite:`1987:nelson` for an introduction to > non-standard analysis." and the cite: appears to be recognized as part > of a link with `1987:nelson` as the path. In this case I would not > expect that to be interpreted as a link. The backticks in the path are > a little problematic for org-ref since they are not part of the actual > key. In this particular case, this is a problem of the fontification engine. It shouldn't fontify Org elements in a src block, or any other verbatim context. More precisely, `org-activate-links' does not check if match is within such a context. Ideally, fontification should use the parser, which doesn't fail in this case. This is on my long TODO list; unfortunately, it has no NEXT keyword yet. Regards, -- Nicolas Goaziou