From: "Loris Bennett" <loris.bennett@fu-berlin.de>
To: emacs-orgmode@gnu.org
Subject: Re: Breaking up long #+TBLFM line?
Date: Tue, 26 Jan 2016 08:48:57 +0100 [thread overview]
Message-ID: <87powoeq6u.fsf@hornfels.zedat.fu-berlin.de> (raw)
In-Reply-To: 8737tlzhce.fsf@alphaville.usersys.redhat.com
Hi Nick,
Nick Dokos <ndokos@gmail.com> writes:
[snip: Loris' whinging and Karl's response (24 lines)]
>> However, I still don't like the long #+TBLFM, although it's not going to
>> kill me.
>>
>
> That's good, because I think you'll have to live with it :-)
>
> There is support for multiple TBLFM lines, but not in the way you want:
> they are alternatives, rather than cumulative - see
>
> (info "(org) Editing and debugging formulas")
>
> the section entitled "Using multiple #+TBLFM lines".
I was aware of this and have found it useful.
However, it seems a little inconsistent that some options, like
'#+OPTIONS' or '#+LATEX_HEADER', are cumulative whereas others, like
'#+TBLFM', are not. Is there a logic to this that I am overlooking? If
not, is there an overview of how the different options behave?
Cheers,
Loris
--
This signature is currently under construction.
next prev parent reply other threads:[~2016-01-26 7:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 8:18 Breaking up long #+TBLFM line? Loris Bennett
2016-01-25 14:51 ` Karl Voit
2016-01-25 15:59 ` Loris Bennett
2016-01-25 16:05 ` Loris Bennett
2016-01-25 17:42 ` Nick Dokos
2016-01-26 4:20 ` Samuel Wales
2016-01-26 14:55 ` table editor is off screen (was: Breaking up long #+TBLFM line?) Karl Voit
2016-01-26 23:34 ` table editor is off screen Nicolas Goaziou
2016-01-27 0:09 ` Samuel Wales
2016-01-26 7:48 ` Loris Bennett [this message]
2016-01-26 11:37 ` Breaking up long #+TBLFM line? Nicolas Goaziou
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=87powoeq6u.fsf@hornfels.zedat.fu-berlin.de \
--to=loris.bennett@fu-berlin.de \
--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).