From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tobias Getzner Subject: Re: Multi-line links Date: Tue, 22 Jul 2014 13:12:05 +0200 Message-ID: <1406027525.16949.8.camel@gmx.de> References: <1404297563.12348.4.camel@glenalbyn> <1404308028.12348.7.camel@glenalbyn> <87egxz3q8m.fsf@nicolasgoaziou.fr> <1404663940.11764.1.camel@wirrsal> <87tx6uxp66.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53232) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1X9XzT-0005W7-Uc for emacs-orgmode@gnu.org; Tue, 22 Jul 2014 07:12:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1X9XzN-0003Xo-Dr for emacs-orgmode@gnu.org; Tue, 22 Jul 2014 07:12:15 -0400 Received: from mout.gmx.net ([212.227.17.22]:51947) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1X9XzN-0003W4-3i for emacs-orgmode@gnu.org; Tue, 22 Jul 2014 07:12:09 -0400 In-Reply-To: <87tx6uxp66.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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Nicolas Goaziou Cc: emacs-orgmode@gnu.org Nicolas, thank you for reply. Due to some health issues I=E2=80=99m only responding now. On So, 2014-07-06 at 21:28 +0200, Nicolas Goaziou wrote: > Tobias Getzner writes: >=20 > > 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? >=20 > I don't think there is a strong reason for that limitation. >=20 > RFC 3986 (Appendix C) suggests how to handle multi-lines URI. We could > use it to handle such links. >=20 > Note that there is more than "org-element.el" to change though (e.g., > `org-make-link-regexps') and some parts of Org relying only on regexps > to extract the path, may not work properly with such links. >=20 > Do you want to work on such a patch? I=E2=80=99m afraid given my nigh complete inexperience with elisp it is unlikely I=E2=80=99ll be able to provide a good, generic solution for this.= My original hope was that for someone familiar with the code, there wouldn=E2=80=99t be many changes needed, since multi-line descriptions seem= ed to be working (though only for < 3 lines) and since the raw-path seemed to contain the needed line-breaks already. But if I understand you correctly, the complication is that the path parsing is the same across different link types, and so one cannot simply fix it up so that :path is equivalent to :raw-path, just with the link prefix stripped of? When I experimented with making multi-line BibTeX links work, I tried working around the issue of the path being truncated by using raw-path instead. But it seems that this breaks when doing export, since the handler seems to only be given the normal (truncated) path as an argument. Is there any way to make the exporter call the export handler with the raw-path as an argument, currently? Best regards, T.