Hello Nicolas, On Sun, 2014-07-06 at 09:23 +0200, Nicolas Goaziou wrote: > Tobias Getzner <tobias.getz...@gmx.de> writes: > > On Wed, 2014-07-02 at 12:39 +0200, Tobias Getzner wrote: > > One additional issue I’ve hit upon is that the link :path returned by > > org-mode is also truncated after a newline, while the :raw-link is > > correctly returned in full. > > Could you provide an example?
My original example also applies to this issue. [[citet:green1994hybridreasoningmodel, green1994generatingindirectanswers, green1992conversationalimplicaturesindirect]] Clicking on the first line in the above link, the returned :path will be just be «green1994hybridreasoningmodel,», i. e., the :path is truncated after the newline. The raw-path will be correct, however, i. e., «citet:green1994hybrid…,\ngreen1994generating…,\ngreen1992…». Apart from the truncation issue, the link itself can be triggered only via the first two lines, while the last line yields «no link found», despite the fact that the last line is syntax-highlighted and clickable. > Note that Org links do not allow newline characters in the "link" part. > Is it really an issue or a limitation? According to the syntax spec, newlines should be allowed both in the link path and in the description, but I realize the syntax spec is kind of after-the-fact. On the other hand, the implementation seems to already support n-line links for the arbitrary value of 2 (with the caveat that the :path value currently breaks). The reason why I consider it a limitation is cases like the one I initially outlined. An extension like org-ref might want to internally parse the link path, and it makes sense to allow newlines as separators here, so that the links remain legible and so one can have hard line-breaks at 80 cols. In particular, BibTeX-based links can become very long. If one prefers hard line-breaks, these links will impair the readability of the document. On the other hand, it’s an inconsistency that these links will be correctly syntax-highlighted and clickable on every line, with the handler then breaking on lines > 2 and with a truncated :path. Since link paths and descriptions cannot contain square brackets, would it be possible to rely just on these to terminate link parsing? In an earlier post of yours, you seem to have identified the relevant code responsible for this: http://lists.gnu.org/archive/html/emacs-orgmode/2011-03/msg00532.html If there is some strong reason for a hard-coded limit, would it be possible to expose the limit as a user-definable variable, and to fix the :path truncation issue? Best regards, Tobias
