From: "Jörg Hagmann" <joerg.hagmann@unibas.ch>
To: emacs-orgmode@gnu.org
Subject: Re: Latex: exporting a tree
Date: Wed, 15 Dec 2010 11:04:34 +0100 [thread overview]
Message-ID: <4D0892B2.2020908@unibas.ch> (raw)
In-Reply-To: <4D023DDC.5080008@unibas.ch>
Third attempt to get your attention:
- If you export the (new) minimal example below to latex (C-cC-e l), it
works.
- If you only export a tree (Subtree in the example; C-cC-e 1 l), the
first table ends at the horizontal line and everything between it and
the next node (Subsubtree) is eliminated. The second (identical) table
is exported correctly.
- If you remove the asterisk(s) in the first table, it works.
This problem crept in in the last days or weeks before 7.4.
It may not be a problem for most of you, but I happen to have a number
of files where columns are automatically displayed as tables preceding
the first subnode (#+BEGIN: columnview ...). An alternative would be to
display %ITEM in column-view without the asterisks.
Emacs 23.2.1 on OS X 10.6.5
Org-mode version 7.4 (release_7.4.24.g48b11.dirty)
Thanks, Jörg
-------New minimal example------------
* Subtree
| One | Two | Three |
|--------+------+-------|
| * Test | text | text |
| ** One | text | text |
Some text
** Subsubtree
| One | Two | Three |
|--------+------+-------|
| * Test | text | text |
| ** One | text | text |
--------End of new minimal example---------------------
On 12/10/10 3:49 PM, Jörg Hagmann wrote:
> I checked the problem below with the latest (7.4 alias "7.3") version
> and it is still there.
> Could somebody look into that?
> Emacs 23.2 on OS X 10.6.5
>
> Thanks, Jörg
>> With today's pull, exporting a subtree to latex (C-cC-e 1 l)
>> truncates a table at the horizontal line and eliminates the text
>> between the table and the next heading. It works when exporting the
>> whole file (C-cC-e l).
>>
>> -------Minimal example--------------
>> * Test
>> :PROPERTIES:
>> :COLUMNS: %15ITEM(Lecture) %number %Date %hours{+} %status{X/}
>> :status_ALL: "[ ]" "[X]"
>> :END:
>>
>> #+BEGIN: columnview :hlines 1 :id local :maxlevel 2
>> | Lecture | number | Date | hours | status |
>> |---------+----------+------------------------------+-------+--------|
>> | * Test | | | 2 | [0/1] |
>> | ** One | 16.1.7.1 | [2010-12-13 Mon 10:15-12:00] | 2 | [ ] |
>> #+END:
>>
>> Some text
>>
>> ** One
>> :PROPERTIES:
>> :Date: [2010-12-13 Mon 10:15-12:00]
>> :hours: 2
>> :number: 16.1.7.1
>> :status: [ ]
>> :END:
>> ---------End of minimal example---------------
next prev parent reply other threads:[~2010-12-15 10:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 9:02 Latex: exporting a tree Jörg Hagmann
2010-12-10 14:49 ` Jörg Hagmann
2010-12-15 10:04 ` Jörg Hagmann [this message]
2010-12-15 11:41 ` Carsten Dominik
2010-12-15 12:13 ` Nicolas Goaziou
2010-12-15 13:48 ` Carsten Dominik
2010-12-15 18:15 ` Nicolas Goaziou
2010-12-15 22:12 ` Carsten Dominik
2010-12-19 0:15 ` Nicolas Goaziou
2011-01-26 10:07 ` [Accepted] " Carsten Dominik
2010-12-15 11:45 ` BUG " Giovanni Ridolfi
2010-12-15 11:53 ` Giovanni Ridolfi
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=4D0892B2.2020908@unibas.ch \
--to=joerg.hagmann@unibas.ch \
--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).