Re: [O] How to show the complete syntax tree

2014-07-14 Thread Charles Berry
Shiyuan  gmail.com> writes:

> 
> Hi,     The command I can find in the manual to show the syntax tree is
(org-element-parse-buffer). However, when the structure is output to the
buffer, by using the commands C-u M-: (org-element-parse-buffer), it seems
that only the part up to a certain depth is printed. 

Yes, as Nick explained there are variables that control this.

My eyes sometimes like this approach to viewing lisp objects:

#+BEGIN_SRC emacs-lisp
(pp-to-string (org-element-parse-buffer))
#+END_SRC

HTH,

Chuck






Re: [O] How to show the complete syntax tree

2014-07-14 Thread Nick Dokos
Shiyuan  writes:

> Hi, 
> The command I can find in the manual to show the syntax tree is
> (org-element-parse-buffer). However, when the structure is output to
> the buffer, by using the commands C-u M-: (org-element-parse-buffer),
> it seems that only the part up to a certain depth is printed.
>

C-h v print-length RET
C-h v print-level RET
C-h v eval-expression-print-length RET
C-h v eval-expression-print-level RET

-- 
Nick




Re: [O] How to show the complete syntax tree

2014-07-14 Thread Thorsten Jolitz
Shiyuan  writes:

> [...]
> For example, if the current org buffer has the following content: 
>
> #+TITLE: Hello World
> Hello World!
> * HEADLINE 1
> ** Sub-topic 
> + ItemA
> + ItemB
> - Item1
> - Item2
> *** Sub-Sub-topic
> \begin{equation}
> \label{eq:test}
> Bx=b
> \end{equation}
> [...]

Following up in outorg, I evaluate this in the *outorg-edit-buffer*:

#+begin_src emacs-lisp :results raw
(org-element-parse-buffer 'object)
#+end_src

#+results:

(org-data nil (headline (:raw-value --text follows this line-- :begin 1
:end 1604 [...]
> For example, if the current org buffer has the following content: 
>
> #+TITLE: Hello World
> Hello World!
> * HEADLINE 1
> ** Sub-topic 
> + ItemA
> + ItemB
> - Item1
> - Item2
>  (bold (:begin 533 :end 537 :contents-begin 534 :contents-end 535
>  :post-blank 1 :parent #3) *) Sub-Sub-topic
>  (latex-fragment (:value \begin{equation} :begin 553 :end 569
>  :post-blank 0 :parent #3))
>  (latex-fragment (:value \label{eq:test} :begin 572 :end 587
>  :post-blank 0 :parent #3))
> Bx=b
>  (latex-fragment (:value \end{equation} :begin 597 :end 611
>  :post-blank 0 :parent #3))
[...]

-- 
cheers,
Thorsten




[O] How to show the complete syntax tree

2014-07-13 Thread Shiyuan
Hi,
The command I can find in the manual to show the syntax tree is
(org-element-parse-buffer). However, when the structure is output to the
buffer, by using the commands C-u M-: (org-element-parse-buffer), it seems
that only the part up to a certain depth is printed.

For example, if the current org buffer has the following content:

#+TITLE: Hello World
Hello World!
* HEADLINE 1
** Sub-topic
+ ItemA
+ ItemB
- Item1
- Item2
*** Sub-Sub-topic
\begin{equation}
\label{eq:test}
Bx=b
\end{equation}

When apply C-u M-: (org-element-parse-buffer),  the sub-sub-topic level is
completely omitted in the printout:

(org-data nil (section (:begin 1 :end 35 :contents-begin 1 :contents-end 35
:post-blank 0 :parent #0) (keyword (:key "TITLE" :value "Hello World"
:begin 1 :end 22 :post-blank 0 :post-affiliated 1 ...)) (paragraph (:begin
22 :end 35 :contents-begin 22 :contents-end 35 :post-blank 0
:post-affiliated 22 ...) #("Hello World!
" 0 13 ...))) (headline (:raw-value "HEADLINE 1" :begin 35 :end 174
:pre-blank 0 :contents-begin 48 :contents-end 173 ...) (headline
(:raw-value "Sub-topic" :begin 48 :end 173 :pre-blank 0 :contents-begin 62
:contents-end 173 ...) (section ... ...) (headline ... ...

What's the recommended way to show the syntax tree? Thanks.

Shiyuan