emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rainer M Krug <r.m.krug@gmail.com>
To: e.fraga@ucl.ac.uk
Cc: Eric S Fraga <ucecesf@ucl.ac.uk>, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [babel] Error with source block and variable on export - bug?
Date: Sat, 04 Sep 2010 17:05:37 +0200	[thread overview]
Message-ID: <4C826041.6020000@gmail.com> (raw)
In-Reply-To: <8739tqpvep.wl%ucecesf@ucl.ac.uk>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/09/10 19:51, Eric S Fraga wrote:
> On Fri, 03 Sep 2010 09:05:24 -0600, "Eric Schulte" <schulte.eric@gmail.com> wrote:
>>
>> Rainer M Krug <r.m.krug@gmail.com> writes:
>>
>>> On 03/09/10 16:32, Rainer M Krug wrote:
>>>> On 03/09/10 15:40, Eric Schulte wrote:
>>>>> Hi Rainer,
>>>>
>>>>> As part of the export process Org-mode copies the contents of the
>>>>> Org-mode file to a temporary buffer in which the business of exportation
>>>>> is performed.  This temporary buffer is not associated with any file so
>>>>> (buffer-file-name) returns nil, which is causing the problem you are
>>>>> experiencing.  I think the best solution would be to replace the call to
>>>>> (buffer-file-name) with the actual name of the file, e.g.
>>>>
>>>>> #+begin_src sh :var file=(vc-working-revision "~/src/babel-dev/scraps.org") :exports results
>>>>>   echo $file Revision
>>>>> #+end_src
>>>>
>>>> Hi Eric
>>>>
>>>> thanks a lot for the clarification - that makes perfect sense. I will do
>>>> as suggested.
>>>
>>> Thanks - it is working now.
>>> But it is a little bit awkward to have the file name (incl. path)
>>> somewhere in the document - can create some problems when renaming the
>>> file or saving it somewhere else).
>>> Is it possible to define it as a kind of variable (property?) in the
>>> headers of the file and reference it in the org file later?
>>>
>>
>> Oh,
>>
>> I've just remembered that during export Org-mode saves this file-name
>> information in the temporary variable `org-current-export-file'.
>>
>> So the following will work, even though it relies upon undocumented
>> internals of Org-mode which could change at some point.
>>
>> #+begin_src sh :var file=(vc-working-revision (or (buffer-file-name) org-current-export-file)) :exports results
>>   echo $file Revision
>> #+end_src
>>
>> Cheers -- Eric
> 
> And this works very well with an inline src snippet (tested with git
> and RCS).  Very nice!

Thanks a lot Eric F. - that inline syntax was also something I was
looking for - I'll put it into my document on Monday morning.

Cheers,

Rainer

> 
> ,----
> | * revision control
> |   The version of this file is 
> |    src_emacs-lisp{(vc-working-revision (or (buffer-file-name) org-current-: export-file))}.
> `----
> 
> Thanks!


- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Natural Sciences Building
Office Suite 2039
Stellenbosch University
Main Campus, Merriman Avenue
Stellenbosch
South Africa

Tel:        +33 - (0)9 53 10 27 44
Cell:       +27 - (0)8 39 47 90 42
Fax (SA):   +27 - (0)8 65 16 27 82
Fax (D) :   +49 - (0)3 21 21 25 22 44
Fax (FR):   +33 - (0)9 58 10 27 44
email:      Rainer@krugs.de

Skype:      RMkrug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkyCYEEACgkQoYgNqgF2egpyawCfddO7cMpDcy0TC4qKTUziRbJ9
GAsAn0l89S6NuEDxzq1lNkE21sW6HWaI
=meaV
-----END PGP SIGNATURE-----

      reply	other threads:[~2010-09-04 15:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-03  9:00 [babel] Error with source block and variable on export - bug? Rainer M Krug
2010-09-03 13:40 ` Eric Schulte
2010-09-03 14:32   ` Rainer M Krug
2010-09-03 14:48     ` Rainer M Krug
2010-09-03 15:05       ` Eric Schulte
2010-09-03 17:51         ` Eric S Fraga
2010-09-04 15:05           ` Rainer M Krug [this message]

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=4C826041.6020000@gmail.com \
    --to=r.m.krug@gmail.com \
    --cc=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=ucecesf@ucl.ac.uk \
    /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).