emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
* [Bug] Exporting subtree with code
@ 2011-09-13 11:56 Maximilian Matthé
  2011-09-13 11:59 ` Maximilian Matthé
  2011-09-13 14:58 ` Eric Schulte
  0 siblings, 2 replies; 6+ messages in thread
From: Maximilian Matthé @ 2011-09-13 11:56 UTC (permalink / raw)
  To: emacs-orgmode

Hi guys,

I found a bug (or I'm doing something wrong): See this org file:

****************************************

* 1
* 2
** 2.1
** 2.2
Exporting this subtree to latex (C-c C-e 1 d) raises
"wrong type argument: arrayp"

#+BEGIN_SRC python :results output :export results
print 1
print 2
#+END_SRC

#+results:
: 1
: 2

****************************************

I can export and process the whole file to latex und pdf with no errors,
but when I try to export the subtree 2.2 I get the given error. What's
going on here?

Regards, Max

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [Bug] Exporting subtree with code
  2011-09-13 11:56 [Bug] Exporting subtree with code Maximilian Matthé
@ 2011-09-13 11:59 ` Maximilian Matthé
  2011-09-13 14:58 ` Eric Schulte
  1 sibling, 0 replies; 6+ messages in thread
From: Maximilian Matthé @ 2011-09-13 11:59 UTC (permalink / raw)
  To: emacs-orgmode

Maxi.Matthe@googlemail.com (Maximilian Matthé) writes:

I'm using org-mode version 
Org-mode version 7.7 (release_7.7.280.gdbf0)

Thanks for your help!

> Hi guys,
>
> I found a bug (or I'm doing something wrong): See this org file:
>
> ****************************************
>
> * 1
> * 2
> ** 2.1
> ** 2.2
> Exporting this subtree to latex (C-c C-e 1 d) raises
> "wrong type argument: arrayp"
>
> #+BEGIN_SRC python :results output :export results
> print 1
> print 2
> #+END_SRC
>
> #+results:
> : 1
> : 2
>
> ****************************************
>
> I can export and process the whole file to latex und pdf with no errors,
> but when I try to export the subtree 2.2 I get the given error. What's
> going on here?
>
> Regards, Max

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [Bug] Exporting subtree with code
  2011-09-13 11:56 [Bug] Exporting subtree with code Maximilian Matthé
  2011-09-13 11:59 ` Maximilian Matthé
@ 2011-09-13 14:58 ` Eric Schulte
  2011-09-13 15:04   ` Maximilian Matthé
  1 sibling, 1 reply; 6+ messages in thread
From: Eric Schulte @ 2011-09-13 14:58 UTC (permalink / raw)
  To: Maximilian Matthé; +Cc: emacs-orgmode

Maxi.Matthe@googlemail.com (Maximilian Matthé) writes:

> Hi guys,
>
> I found a bug (or I'm doing something wrong): See this org file:
>
> ****************************************
>
> * 1
> * 2
> ** 2.1
> ** 2.2
> Exporting this subtree to latex (C-c C-e 1 d) raises
> "wrong type argument: arrayp"
>
> #+BEGIN_SRC python :results output :export results
> print 1
> print 2
> #+END_SRC
>
> #+results:
> : 1
> : 2
>
> ****************************************
>
> I can export and process the whole file to latex und pdf with no errors,
> but when I try to export the subtree 2.2 I get the given error. What's
> going on here?
>

I just pushed up a fix for this issue.  Thanks for reporting and please
let me know if the problem persists with the latest version of Org-mode
from git head.

Best -- Eric

>
> Regards, Max
>
>

-- 
Eric Schulte
http://cs.unm.edu/~eschulte/

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [Bug] Exporting subtree with code
  2011-09-13 14:58 ` Eric Schulte
@ 2011-09-13 15:04   ` Maximilian Matthé
  2011-09-13 15:36     ` Eric Schulte
  0 siblings, 1 reply; 6+ messages in thread
From: Maximilian Matthé @ 2011-09-13 15:04 UTC (permalink / raw)
  To: emacs-orgmode

[-- Attachment #1: Type: text/plain, Size: 1617 bytes --]

Eric Schulte <schulte.eric@gmail.com> writes:

> Maxi.Matthe@googlemail.com (Maximilian Matthé) writes:
>
>> Hi guys,
>>
>> I found a bug (or I'm doing something wrong): See this org file:
>>
>> ****************************************
>>
>> * 1
>> * 2
>> ** 2.1
>> ** 2.2
>> Exporting this subtree to latex (C-c C-e 1 d) raises
>> "wrong type argument: arrayp"
>>
>> #+BEGIN_SRC python :results output :export results
>> print 1
>> print 2
>> #+END_SRC
>>
>> #+results:
>> : 1
>> : 2
>>
>> ****************************************
>>
>> I can export and process the whole file to latex und pdf with no errors,
>> but when I try to export the subtree 2.2 I get the given error. What's
>> going on here?
>>
>
> I just pushed up a fix for this issue.  Thanks for reporting and please
> let me know if the problem persists with the latest version of Org-mode
> from git head.
>
> Best -- Eric
>

Hi,

I just pulled the new version, but now I get another error message,
here's the message lock

,----
| SUBTREE
| Export buffer: 
| Export subtree: 
| Mark set
| Exporting to PDF...
| Exporting to LaTeX...
| OVERVIEW
| Loading reftex...done
| Compiling label environment definitions...done
| Scanning entire document...
| Scanning file /home/mmatthe/temp/bla.tex
| Scanning section 1 ...
| Scanning section 2 ...
| Scanning document... done
| Applying style hooks... done
| Loading reftex...done
| org-babel-exp processing...
| Loading reftex...done
| org-babel-exp processing...
| org-babel-get-src-block-info: Wrong type argument: char-or-string-p, nil
`----
 I attach the file I'm using (it's the same).
Regards, Max


[-- Attachment #2: bla.org --]
[-- Type: application/octet-stream, Size: 181 bytes --]

* 1
* 2
** 2.1
** 2.2
Exporting this subtree raises
"wrong type argument: arrayp"

#+BEGIN_SRC python :results output :export results
print 1
print 2
#+END_SRC

#+results:
: 1
: 2


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [Bug] Exporting subtree with code
  2011-09-13 15:04   ` Maximilian Matthé
@ 2011-09-13 15:36     ` Eric Schulte
  2011-09-13 16:39       ` Maximilian Matthé
  0 siblings, 1 reply; 6+ messages in thread
From: Eric Schulte @ 2011-09-13 15:36 UTC (permalink / raw)
  To: Maximilian Matthé; +Cc: emacs-orgmode

>>
>> I just pushed up a fix for this issue.  Thanks for reporting and
>>please let me know if the problem persists with the latest version of
>>Org-mode from git head.
>>
>> Best -- Eric
>>
>
> Hi,
>
> I just pulled the new version, but now I get another error message,
> here's the message lock
>

I just pushed up another fix which should resolve this problem.

What is happening is that the latex export is processing the buffer
twice.  On the first pass through the code block is evaluated, its
results inserted, and its body removed.  On the second pass through the
code block processing is choking on a block with no body.  The
processing should now be robust to blocks with no bodies, however a
better fix would be to find out why the buffer is processed twice on
latex export and change that behavior.

Cheers -- Eric

-- 
Eric Schulte
http://cs.unm.edu/~eschulte/

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [Bug] Exporting subtree with code
  2011-09-13 15:36     ` Eric Schulte
@ 2011-09-13 16:39       ` Maximilian Matthé
  0 siblings, 0 replies; 6+ messages in thread
From: Maximilian Matthé @ 2011-09-13 16:39 UTC (permalink / raw)
  To: emacs-orgmode

Eric Schulte <schulte.eric@gmail.com> writes:


>>
>> Hi,
>>
>> I just pulled the new version, but now I get another error message,
>> here's the message lock
>>
>
> I just pushed up another fix which should resolve this problem.

> Cheers -- Eric

Thanks Eric, the error message is gone, I can now export the subtree
again :)

Regards, Max

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2011-09-13 16:39 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-09-13 11:56 [Bug] Exporting subtree with code Maximilian Matthé
2011-09-13 11:59 ` Maximilian Matthé
2011-09-13 14:58 ` Eric Schulte
2011-09-13 15:04   ` Maximilian Matthé
2011-09-13 15:36     ` Eric Schulte
2011-09-13 16:39       ` Maximilian Matthé

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