bug: babel: Export of temporary buffers fails

bug: babel: Export of temporary buffers fails

[Puneeth]

Hello,

Export of temporary buffers with babel src blocks fails.

Line 118 of ob-exp.el has

(set-buffer (get-file-buffer org-current-export-file))

But the value of org-current-exp-file is nil for a temporary buffer.

The following commit brought in that change.

commit efdf78172d9f7c0070c781d136a9b49a2a56fcc4
Author: Eric Schulte <schulte.eric@gmail.com>
Date:   Sat Sep 18 19:01:49 2010 -0600

    ob-exp: resolving code block parameters in the original file on export

    * lisp/ob-exp.el (org-babel-exp-src-blocks): now switching back to the
      original file before resolving code block parameters to ensure
      headline and buffer wide parameters are taken into consideration
      when only a narrowed portion of the file is exported


HTH,

Puneeth

Re: bug: babel: Export of temporary buffers fails

[Eric Schulte]

Hi Puneeth,

I believe that export is only allowed from buffers visiting files, when
I tried to reproduce your problem exporting from a buffer without a file
name I get the following error message

  (error "Need a file name to be able to export")

which is thrown by org-latex, org-docbook, or org-html on attempted
export.

Unless I'm missing something, it is not a problem that Babel expects
org-current-export-file to have a value.

Best -- Eric

Puneeth <punchagan@gmail.com> writes:

> Hello,
>
> Export of temporary buffers with babel src blocks fails.
>
> Line 118 of ob-exp.el has
>
> (set-buffer (get-file-buffer org-current-export-file))
>
> But the value of org-current-exp-file is nil for a temporary buffer.
>
> The following commit brought in that change.
>
> commit efdf78172d9f7c0070c781d136a9b49a2a56fcc4
> Author: Eric Schulte <schulte.eric@gmail.com>
> Date:   Sat Sep 18 19:01:49 2010 -0600
>
>     ob-exp: resolving code block parameters in the original file on export
>
>     * lisp/ob-exp.el (org-babel-exp-src-blocks): now switching back to the
>       original file before resolving code block parameters to ensure
>       headline and buffer wide parameters are taken into consideration
>       when only a narrowed portion of the file is exported
>
>
> HTH,
>
> Puneeth
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: bug: babel: Export of temporary buffers fails

[Sebastian Rose]

"Eric Schulte" <schulte.eric@gmail.com> writes:
> Hi Puneeth,
>
> I believe that export is only allowed from buffers visiting files, when
> I tried to reproduce your problem exporting from a buffer without a file
> name I get the following error message
>
>   (error "Need a file name to be able to export")
>
> which is thrown by org-latex, org-docbook, or org-html on attempted
> export.
>
> Unless I'm missing something, it is not a problem that Babel expects
> org-current-export-file to have a value.
>
> Best -- Eric
>
> Puneeth <punchagan@gmail.com> writes:
>
>> Hello,
>>
>> Export of temporary buffers with babel src blocks fails.
>>
>> Line 118 of ob-exp.el has
>>
>> (set-buffer (get-file-buffer org-current-export-file))
>>
>> But the value of org-current-exp-file is nil for a temporary buffer.
>>
>> The following commit brought in that change.
>>
>> commit efdf78172d9f7c0070c781d136a9b49a2a56fcc4
>> Author: Eric Schulte <schulte.eric@gmail.com>
>> Date:   Sat Sep 18 19:01:49 2010 -0600
>>
>>     ob-exp: resolving code block parameters in the original file on export
>>
>>     * lisp/ob-exp.el (org-babel-exp-src-blocks): now switching back to the
>>       original file before resolving code block parameters to ensure
>>       headline and buffer wide parameters are taken into consideration
>>       when only a narrowed portion of the file is exported


Usually an Org file NAME.org is exported to NAME.html, NAME.txt and so
forth.


You can still export to a temporary buffer (`A' instead of `a', `H'
instead of `h') ...


HTH


   Sebastian

Re: bug: babel: Export of temporary buffers fails

[Puneeth]

Hi Eric,
>
> You can still export to a temporary buffer (`A' instead of `a', `H'
> instead of `h') ...

Yes. And this fails when there is an org-babel src block in the buffer.

-- Puneeth

Re: bug: babel: Export of temporary buffers fails

[Eric Schulte]

Puneeth <punchagan@gmail.com> writes:

> Hi Eric,
>>
>> You can still export to a temporary buffer (`A' instead of `a', `H'
>> instead of `h') ...
>
> Yes. And this fails when there is an org-babel src block in the buffer.
>
> -- Puneeth

Hi Puneeth,

I've just tried exporting an org-mode buffer containing babel code
blocks to a temporary file using C-c C-e H, and it worked without
problem.  Could you send me an example org-mode file that throws the
error your described?

Thanks -- Eric

Re: bug: babel: Export of temporary buffers fails

[Puneeth]

Hi Eric,

On Mon, Oct 4, 2010 at 6:43 PM, Eric Schulte <schulte.eric@gmail.com>
> I've just tried exporting an org-mode buffer containing babel code
> blocks to a temporary file using C-c C-e H, and it worked without
> problem.  Could you send me an example org-mode file that throws the
> error your described?

Have you exported from a temporary buffer? or a buffer visiting a file?

To reproduce the error that I get,

1. Switch to scratch buffer (or a new temporary buffer)
2. M-x org-mode to change the mode to Org-mode
3. Yank the following text into it
-----------------------------------------
* Hello World
  #+begin_src python
  print "Hello, World"
  #+end_src
-----------------------------------------
4. C-c C-e H

You should get the error
set-buffer: Wrong type argument: stringp, nil

HTH,
Puneeth

Re: bug: babel: Export of temporary buffers fails

[Eric Schulte]

Ok,

Thanks for your persistence in explaining this to me.  I've just pushed
up a change which should fix this issue.

Best -- Eric

Puneeth <punchagan@gmail.com> writes:

> Hi Eric,
>
> On Mon, Oct 4, 2010 at 6:43 PM, Eric Schulte <schulte.eric@gmail.com>
>> I've just tried exporting an org-mode buffer containing babel code
>> blocks to a temporary file using C-c C-e H, and it worked without
>> problem.  Could you send me an example org-mode file that throws the
>> error your described?
>
> Have you exported from a temporary buffer? or a buffer visiting a file?
>
> To reproduce the error that I get,
>
> 1. Switch to scratch buffer (or a new temporary buffer)
> 2. M-x org-mode to change the mode to Org-mode
> 3. Yank the following text into it
> -----------------------------------------
> * Hello World
>   #+begin_src python
>   print "Hello, World"
>   #+end_src
> -----------------------------------------
> 4. C-c C-e H
>
> You should get the error
> set-buffer: Wrong type argument: stringp, nil
>
> HTH,
> Puneeth

Re: bug: babel: Export of temporary buffers fails

[Puneeth]

Eric,

On Mon, Oct 4, 2010 at 8:09 PM, Eric Schulte <schulte.eric@gmail.com> wrote:
> Ok,
>
> Thanks for your persistence in explaining this to me.  I've just pushed
> up a change which should fix this issue.

Thanks for the fix. :)

I had my reasons for being persistent. org2blog [a client for posting
to Wordpress from Org-mode] uses temporary buffers when posting
subtrees.

-- Puneeth

Re: bug: babel: Export of temporary buffers fails

[Hsiu-Khuern Tang]

Hi Eric,


Are you also seeing the problem reported at
http://thread.gmane.org/gmane.emacs.orgmode/30855?  I checked out the
latest git version and that problem still exists.


I don't know how closely it is related to the problem in this thread,
but it was caused by the same commit
(efdf78172d9f7c0070c781d136a9b49a2a56fcc4) -- hoping you can shed some
light on this.  Thanks!


-- 
Best,
Hsiu-Khuern.


On Mon, Oct 4, 2010 at 7:39 AM, Eric Schulte <schulte.eric@gmail.com> wrote:
> Ok,
>
> Thanks for your persistence in explaining this to me.  I've just pushed
> up a change which should fix this issue.
>
> Best -- Eric
>
> Puneeth <punchagan@gmail.com> writes:
>
>> Hi Eric,
>>
>> On Mon, Oct 4, 2010 at 6:43 PM, Eric Schulte <schulte.eric@gmail.com>
>>> I've just tried exporting an org-mode buffer containing babel code
>>> blocks to a temporary file using C-c C-e H, and it worked without
>>> problem.  Could you send me an example org-mode file that throws the
>>> error your described?
>>
>> Have you exported from a temporary buffer? or a buffer visiting a file?
>>
>> To reproduce the error that I get,
>>
>> 1. Switch to scratch buffer (or a new temporary buffer)
>> 2. M-x org-mode to change the mode to Org-mode
>> 3. Yank the following text into it
>> -----------------------------------------
>> * Hello World
>>   #+begin_src python
>>   print "Hello, World"
>>   #+end_src
>> -----------------------------------------
>> 4. C-c C-e H
>>
>> You should get the error
>> set-buffer: Wrong type argument: stringp, nil
>>
>> HTH,
>> Puneeth
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>

Re: bug: babel: Export of temporary buffers fails

[Eric Schulte]

Hi,

This issue is fixed in the "combined-testing" branch of the repository,
I hope to merge that branch into the master branch soon.

If anyone is interested, some of my thoughts on this commit which has
caused these couple of recent problems...  It seems that by using
org-links to find the location of a headline in an Org-mode file during
export I have introduced a handful of little bugs in the export process.
I think these have now been fixed but the fixes are a little bit hacky,
however I think that relying on org-mode links for finding these
headlines is still preferable to implementing a Babel-specific method of
linking back to the original export file.

Best -- Eric

Hsiu-Khuern Tang <tangoh@gmail.com> writes:

> Hi Eric,
>
>
> Are you also seeing the problem reported at
> http://thread.gmane.org/gmane.emacs.orgmode/30855?  I checked out the
> latest git version and that problem still exists.
>
>
> I don't know how closely it is related to the problem in this thread,
> but it was caused by the same commit
> (efdf78172d9f7c0070c781d136a9b49a2a56fcc4) -- hoping you can shed some
> light on this.  Thanks!