From: Yu <firstname.lastname@example.org>
To: org-mode mailing list <email@example.com>
Subject: [BUG]? Constant-definition-lines in tables get exported.
Date: Fri, 17 Feb 2012 13:13:16 +0100 [thread overview]
Message-ID: <CANtbJLFjV5TpdwwQj0eohW6dKHUDbrppC2KjU6WWKz-D2qozcg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1302 bytes --]
org-mode tables currently allow defining table-local constants in lines
marked with "$" (as described in the "Tables > Advanced Features" section
of the manual).
However, when exporting (to LaTeX), these lines are included in the output
-- and a cannot find a possibility to re-exclude them.
Using #+CONSTANTS: is no adequate replacement, as the table-local constants
help to avoid accidentially defining a constant twice, maybe with different
values. Also the local character allows to use shorter names, which are
better understandable in the context, but maybe not at all outside.
An example table from my work:
| | site | N | E/N[eV] | E_surf[meV/A²] |
| * | on-top-1 | 32 | -7.2062959 | 138.89 |
| * | bridge-2 | 32 | -7.2063544 | 138.85 |
| * | bridge-3 | 32 | -7.2064131 | 138.81 |
| $ | e_bulk=-8.30623 | | | |
| $ | e_bulk_zn=-1.26671 | | | |
| $ | A_int=25.34335655 | | | |
My org-mode is a yesterday's pull from the git-repository.
kind regards, Yu
[-- Attachment #2: Type: text/html, Size: 2377 bytes --]
next reply other threads:[~2012-02-17 12:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 12:13 Yu [this message]
2012-02-22 8:36 ` [BUG]? Constant-definition-lines in tables get exported Nicolas Goaziou
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).