emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Tobias Getzner <tobias.getzner@gmx.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Multi-line links
Date: Sat, 26 Jul 2014 15:32:23 +0200	[thread overview]
Message-ID: <87oawcnt3s.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <1406027525.16949.8.camel@gmx.de> (Tobias Getzner's message of "Tue, 22 Jul 2014 13:12:05 +0200")

Hello,

Tobias Getzner <tobias.getzner@gmx.de> writes:

> I’m afraid given my nigh complete inexperience with elisp it is
> unlikely I’ll be able to provide a good, generic solution for this. My
> original hope was that for someone familiar with the code, there
> wouldn’t 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,

-- 
Nicolas Goaziou

next prev parent reply	other threads:[~2014-07-26 13:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-02 10:39 Multi-line links Tobias Getzner
2014-07-02 13:33 ` Tobias Getzner
2014-07-06  7:23   ` Nicolas Goaziou
2014-07-06 16:25     ` Tobias Getzner
2014-07-06 19:28       ` Nicolas Goaziou
2014-07-22 11:12         ` Tobias Getzner
2014-07-26 13:32           ` Nicolas Goaziou [this message]
2014-08-04 11:03             ` Tobias Getzner
2014-08-06 11:36               ` Nicolas Goaziou

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87oawcnt3s.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=tobias.getzner@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).