From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Kitchin Subject: Re: link recognition in orgmode Date: Tue, 05 Sep 2017 20:29:34 -0700 Message-ID: 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]:33227) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dpR2B-0002b5-PA for emacs-orgmode@gnu.org; Tue, 05 Sep 2017 23:29:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dpR27-0000Ov-MJ for emacs-orgmode@gnu.org; Tue, 05 Sep 2017 23:29:47 -0400 Received: from mail-pg0-x22f.google.com ([2607:f8b0:400e:c05::22f]:36756) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dpR27-0000Mx-FO for emacs-orgmode@gnu.org; Tue, 05 Sep 2017 23:29:43 -0400 Received: by mail-pg0-x22f.google.com with SMTP id m9so13034977pgd.3 for ; Tue, 05 Sep 2017 20:29:42 -0700 (PDT) In-reply-to: <8760cwna12.fsf@nicolasgoaziou.fr> 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: Nicolas Goaziou Cc: "emacs-orgmode@gnu.org" Nicolas Goaziou writes: > Hello, > > John Kitchin writes: > >> With this definition of a link in org-9: >> >> #+BEGIN_SRC emacs-lisp >> (org-link-set-parameters "test" :follow (lambda (path) (message "check"))) >> #+END_SRC >> >> #+RESULTS: >> >> Should both of these be "linkfied"? I would have expected the first one >> to be, but not the second one. It seems like the "test:rtree" parts of >> both of these are linkified. >> >> test:rtree :test:rtree > > It looks correct. `org-plain-link-re' regexp expects a word boundary > before the type. If you disagree, what do you suggest as allowed > characters before a plain link? I thought I knew the answer to that, which is I normally would say a space or a [, but... 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. However, it is pretty common (in my work) to put citations right after punctuation when they are superscripted, e.g. after a comma,cite:somekey or after the end of a sentence.cite:anotherkey. That is common because old LaTeX packages couldn't put them in the right place; it was up to you. It is a pain to switch to bracketed citations though, because brackets typically go before punctuations. I normally use bracketed links in this scenario, but I would expect plain links to work here (mostly because they always have), including all the other punctuations. Newer latex packages handle the citation placement for you and let you do what makes the most sense to me which is to put citations before a comma like cite:thirdkey, and before a period cite:fourthkey. That way the citations are in the sentence they belong to and the rest is just styling during export. So, in the end I am a little conflicted on the solution here. It seems specific to this particular markup conflict, which is links should not start with " :" or "^:". On the other hand, org-ref fails harmlessly for me (although in some setups it might lead to a traceback, e.g. https://github.com/jkitchin/org-ref/issues/492), and I am inclined to leave well enough alone and stick with the harmless fail (the fail is when you generate help on the link and it can't find the key in the bibtex file). Thoughts? > > Regards, -- Professor John Kitchin Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 @johnkitchin http://kitchingroup.cheme.cmu.edu