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: Myles English <mylesenglish@gmail.com>,
	Emacs-orgmode <Emacs-orgmode@gnu.org>
Subject: Re: links to attachments don't export anymore
Date: Fri, 22 Nov 2013 11:35:10 +0100	[thread overview]
Message-ID: <ywodzjowg1wh@de.bosch.com> (raw)
In-Reply-To: <ywodeh6c50cq@de.bosch.com> (Thomas Holst's message of "Tue, 19 Nov 2013 08:15:01 +0100")

Hi Nicolas,

· Thomas Holst <thomas.holst@de.bosch.com> wrote:
> 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.

sorry for the late answer. I could only test it today.

For me the problem still persists.

Here is my way to produce it.

- start emacs (Win7)
  : start C:\Programme\gnu\emacs-24.3\bin\emacs.exe -Q --eval "(load-file \"testing.el\")"

- testing.el

  #+begin_src emacs_lisp
    (add-to-list 'load-path "~/git/org-mode/lisp")
    (add-to-list 'load-path "~/git/site-lisp")
    ;; pfad zu contib/lisp
    (add-to-list 'load-path "~/git/org-mode/contrib/lisp")
    (add-to-list 'load-path "~/git/org-mode/contrib/babel/lisp")

    (require 'org-install)
    (require 'ox)
    (require 'ox-latex)
    (require 'org-attach)

    (setq org-link-abbrev-alist '(("att" . org-attach-expand-link)))

    (find-file "testing.org")

- testing.org

  #+begin_src org
    #+OPTIONS:   H:3 num:t toc:nil \n:nil @:t ::t |:t ^:{} -:t f:t *:t <:t
    #+OPTIONS:   TeX:dvipng LaTeX:t skip:nil d:t todo:t pri:nil tags:nil

    * Attachment                                                                           :ATTACH:
      :Attachments: overview.png
      :ID:       1eb9cb02-4011-4720-932b-2934e99827d0

      With org-version:
      #+BEGIN_SRC emacs-lisp :exports results
        (org-version nil t)

      : Org-mode version 8.0.7 (release_8.0.7 @ path-to/org-mode/lisp/)

      an attachment link


      gets exported as:


The link gets exportet as:

Org-mode version 8.0.7 (release_8.0.7 @ path-to/org-mode/lisp/)


Org-mode version 8.2.3c (release_8.2.3c-251-gbb97f5 @ path-to/git/org-mode/lisp/)


So obviously the sub path to the attachment is missing in the link

Thanks for looking into this.
Bis neulich ...

  parent reply	other threads:[~2013-11-22 10:35 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
2013-11-19 14:21           ` Myles English
2013-11-22 10:35           ` Thomas Holst [this message]
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:

  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=ywodzjowg1wh@de.bosch.com \
    --to=thomas.holst@de.bosch.com \
    --cc=Emacs-orgmode@gnu.org \
    --cc=mylesenglish@gmail.com \
    --cc=n.goaziou@gmail.com \


* 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


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).