From: Muchenxuan Tong <firstname.lastname@example.org> To: email@example.com Subject: Bug: Falsely identify Table formula as INVISIBLE target Date: Wed, 14 Mar 2012 16:49:29 +0800 [thread overview] Message-ID: <CANvjMgk8TkBH9yEnLUGtUvMJoqfhrtZ-ycSk=4+sPbFtHkMqDw@mail.gmail.com> (raw) [-- Attachment #1: Type: text/plain, Size: 400 bytes --] I use a formula like this in my org table: #+TBLFM: $>=vmean($<<..$>>);%.3f However, when I export the org table to a latex file, there appears a line in the tex file like this: <<..\$>>(INVISIBLE) If I use #+TBLFM: $>=vmean($2..$>>);%.3f, the problem will disappear. I think this is caused by the functions in org-exp.el falsely identifies the formula as INVISIBLE target. By: Muchenxuan Tong [-- Attachment #2: Type: text/html, Size: 1592 bytes --]
reply other threads:[~2012-03-14 8:50 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CANvjMgk8TkBH9yEnLUGtUvMJoqfhrtZ-ycSk=4+sPbFtHkMqDw@mail.gmail.com' \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Bug: Falsely identify Table formula as INVISIBLE target' \ /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
Code repositories for project(s) associated with this 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).