emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Thomas Holst <thomas.holst@de.bosch.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: "Holst Thomas (DGS-EC/ESE4)" <Thomas.Holst@de.bosch.com>,
	Myles English <mylesenglish@gmail.com>,
	Emacs-orgmode <Emacs-orgmode@gnu.org>,
	Carsten Domink <carsten.dominik@gmail.com>
Subject: Re: links to attachments don't export anymore
Date: Tue, 19 Nov 2013 08:15:01 +0100	[thread overview]
Message-ID: <ywodeh6c50cq@de.bosch.com> (raw)
In-Reply-To: <87pppxo53m.fsf@gmail.com> (Nicolas Goaziou's message of "Mon, 18 Nov 2013 20:57:33 +0100")

Hi,

· Nicolas Goaziou <n.goaziou@gmail.com> wrote:

>> Actually, this could solved by widening the buffer before expanding the
>> link in `org-element-link-parser'.
>>
>> Though, I'm surprised that neither `org-id-get', `org-entry-get' nor, at
>> the most basic level, `org-entry-properties' remove narrowing before
>> computing their return value.
>>
>> Is there any reason for this? AFAICT, it would be better to wrap them
>> with a `org-with-wide-buffer' macro.
>
> Done for `org-entry-properties'. The regression should be fixed now.
>
> Thank you for the report.

Thanks for fixing it! I don't have time to test it today. But I will do
so tomorrow. I will report.

-- 
Bis neulich ...
  Thomas

  reply	other threads:[~2013-11-19  7:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-12 17:18 links to attachments don't export anymore Myles English
2013-11-14 14:44 ` Thomas Holst
2013-11-15 16:54   ` Nicolas Goaziou
2013-11-15 17:35     ` Nicolas Goaziou
2013-11-18 19:57       ` Nicolas Goaziou
2013-11-19  7:15         ` Thomas Holst [this message]
2013-11-19 14:21           ` Myles English
2013-11-22 10:35           ` Thomas Holst
2013-11-22 11:46             ` Nicolas Goaziou
2013-11-25  9:05               ` Thomas Holst

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=ywodeh6c50cq@de.bosch.com \
    --to=thomas.holst@de.bosch.com \
    --cc=Emacs-orgmode@gnu.org \
    --cc=carsten.dominik@gmail.com \
    --cc=mylesenglish@gmail.com \
    --cc=n.goaziou@gmail.com \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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).