From: "Eric Schulte" <schulte.eric@gmail.com>
To: R.M.Krug@gmail.com
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [babel] Error with source block and variable on export - bug?
Date: Fri, 03 Sep 2010 09:05:24 -0600 [thread overview]
Message-ID: <878w3iuatn.fsf@gmail.com> (raw)
In-Reply-To: <4C810AC4.2000304@gmail.com> (Rainer M. Krug's message of "Fri, 03 Sep 2010 16:48:36 +0200")
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
>
> Rainer
>
>>
>> Cheers,
>>
>> Rainer
>>
>>
>>> Cheers -- Eric
>>
>>> Rainer M Krug <r.m.krug@gmail.com> writes:
>>
>>>> Hi
>>>>
>>>> when I insert the following source block
>>>>
>>>> #+begin_src sh :exports results :var
>>>> ver=(vc-working-revision(buffer-file-name))
>>>> echo Revision $ver
>>>> #+end_src
>>>>
>>>> into a svn (probably other VCs as well) registered file and execute it
>>>> via C-c C-c, it gives me the revision:
>>>>
>>>> #+begin_src sh :exports results :var
>>>> ver=(vc-working-revision(buffer-file-name))
>>>> echo Revision $ver
>>>> #+end_src
>>>>
>>>> #+results:
>>>> : Revision 191
>>>>
>>>> So when exporting, I would expect that it also prints "Revision 191",
>>>> but I get an error:
>>>>
>>>> vc-file-getprop: Wrong type argument: stringp, nil
>>>>
>>>> Tangling the file with :var ver=(vc-working-revision(buffer-file-name))
>>>> as a header argument also works fine.
>>>>
>>>> As the evaluation works, I assume that is a bug somewhere?
>>>>
>>>> Cheers,
>>>>
>>>> Rainer
>>
>>
next prev parent reply other threads:[~2010-09-03 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 [this message]
2010-09-03 17:51 ` Eric S Fraga
2010-09-04 15:05 ` Rainer M Krug
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=878w3iuatn.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=R.M.Krug@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).