From: Scott Otterson <scotto@u.washington.edu>
To: Carsten Dominik <dominik@science.uva.nl>
Cc: emacs-orgmode@gnu.org
Subject: Re: fancier and less fancy export
Date: Fri, 12 May 2006 10:08:43 -0700 [thread overview]
Message-ID: <4464C11B.5000202@u.washington.edu> (raw)
In-Reply-To: <4091309635d30af6eb6f8cbb4f62110e@science.uva.nl>
Carsten Dominik (05/12/2006 12:57 AM) wrote:
> In the next version, this is going to work as follows:
>
> The command org-export-copy-visible no longer exists.
>
> Instead there is a new command org-export-visible, bound to C-c C-x v.
> When using this command, you are prompted for another key, to specify
> the true export command. Org-mode will then make a temporary buffer
> containing the visible part of the current buffer only, and export this
> buffer to ascii, html, xoxo.
Thanks. This is perfect.
One thing I noticed, though, is that tables with the < > column width
limitation are exported without the width being collapsed, like so:
| purpose | run | words | EM | note | options |
|---------+-----+-------+-----+------------+------------+
| acfeat | 0 | | <3> | turns | |
| thresh | 1 | NA | 12 | turns | thrsh=10 |
| thresh | 56 | x | 0/0 improve | nolab/turns | thrsh=30 |
even if it was being displayed collapsed at the time of export
(collapsed by hitting a tab in a cell somewhere, for example).
Now that I think of it, it would be nice if table column widths were
collapsed at the first entry of a .org file. Without that first TAB, my
tables are unreadably mangled. On the other hand, I suppose that seing
them uncollapsed at first, is a good reminder of the content that will
be hidden after the first TAB.
Scott
next prev parent reply other threads:[~2006-05-12 17:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-08 16:43 fancier and less fancy export Scott Otterson
2006-05-08 17:07 ` Nic
2006-05-08 19:33 ` David O'Toole
2006-05-08 21:00 ` Carsten Dominik
2006-05-08 21:13 ` Nic
2006-05-12 7:57 ` Carsten Dominik
2006-05-12 17:08 ` Scott Otterson [this message]
2006-05-12 22:03 ` Carsten Dominik
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=4464C11B.5000202@u.washington.edu \
--to=scotto@u.washington.edu \
--cc=dominik@science.uva.nl \
--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).