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

From: John Kitchin <johnrkitchin@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org, John Kitchin <johnrkitchin@gmail.com>
Subject: Re: question about org-element-map missing link in caption
Date: Tue, 27 Jan 2015 10:53:50 -0500	[thread overview]
Message-ID: <m24mrcrzht.fsf@gmail.com> (raw)
In-Reply-To: <87d26046yr.fsf@nicolasgoaziou.fr>

hmm... Is there any way to tell when a link in in an affiliate? so we
can tell when we cannot trust buffer positions?

Maybe even better fix the implementation to add the found buffer
positions to some affiliate position so they are correct? I could give
that a try if you can point me to the function it occurs in.

Thanks.


Nicolas Goaziou writes:

> John Kitchin <johnrkitchin@gmail.com> writes:
>
>> I tried it, and indeed the links in captions are found, but something is
>> still not right. The :begin properties of the links in the caption seem
>> to be relative to the point after the : in the caption. That isn't
>> obvious and makes it hard to store a marker to the link. Is that
>> expected behavior?
>
> This is an implementation detail. Parsing for secondary strings (e.g.,
> captions, some keywords like "TITLE") happens in a temporary buffer. You
> cannot trust buffer positions in this case.
>
>
> 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

next prev parent reply	other threads:[~2015-01-27 15:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-27  0:13 question about org-element-map missing link in caption John Kitchin
2015-01-27 11:03 ` Nicolas Goaziou
2015-01-27 13:48   ` John Kitchin
2015-01-27 14:46     ` Nicolas Goaziou
2015-01-27 15:53       ` John Kitchin [this message]
2015-01-27 21:35         ` Nicolas Goaziou
2015-01-27 22:05           ` John Kitchin

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=m24mrcrzht.fsf@gmail.com \
    --to=johnrkitchin@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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).