From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Multi-line links Date: Sat, 26 Jul 2014 15:32:23 +0200 Message-ID: <87oawcnt3s.fsf@nicolasgoaziou.fr> References: <1404297563.12348.4.camel@glenalbyn> <1404308028.12348.7.camel@glenalbyn> <87egxz3q8m.fsf@nicolasgoaziou.fr> <1404663940.11764.1.camel@wirrsal> <87tx6uxp66.fsf@nicolasgoaziou.fr> <1406027525.16949.8.camel@gmx.de> 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]:49152) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XB24n-0000jR-5m for emacs-orgmode@gnu.org; Sat, 26 Jul 2014 09:32:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XB24f-0006KH-MV for emacs-orgmode@gnu.org; Sat, 26 Jul 2014 09:31:53 -0400 Received: from relay3-d.mail.gandi.net ([2001:4b98:c:538::195]:37874) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XB24f-00068n-GT for emacs-orgmode@gnu.org; Sat, 26 Jul 2014 09:31:45 -0400 In-Reply-To: <1406027525.16949.8.camel@gmx.de> (Tobias Getzner's message of "Tue, 22 Jul 2014 13:12:05 +0200") 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: Tobias Getzner Cc: emacs-orgmode@gnu.org Hello, Tobias Getzner writes: > 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 thi= s. My > original hope was that for someone familiar with the code, there > wouldn=E2=80=99t be many changes needed, In the long run, I'm pretty sure the project will benefit more if you bring in your own, temporary, inexperience and start hacking from there. > since multi-line descriptions seemed 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? I fixed it in maint. "org-element.el" used an inadequate regexp to analyze the path. Could you confirm it? Regards, --=20 Nicolas Goaziou