From: Christian Moe <email@example.com>
To: Tom Gillespie <firstname.lastname@example.org>
Cc: org-mode-email <email@example.com>, TEC <firstname.lastname@example.org>
Subject: Re: Tables: missing multi-col/row syntax
Date: Wed, 04 Nov 2020 10:23:50 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
+1 for enabling table-cell merges in export. I imagine this would be a
tricky job for developers, but it would relieve me as a user of much
repeated fiddling with exported drafts.
+1 for doing it without adding clutter to the table syntax, but
specifying merges on a separate line like formulas, like Tom's
(amended here to use the established '..' rather than hyphen for range)
Though if we do add such a line, we might also think of a more general
solution that could over time be extended with additional formatting
options, e.g. something like
#+TBLSTYLE: @2..3$1='(:merge t)::@4$1='(:bgcolor yellow :color red)
But obviously that could open a can of worms, aka potentially endless
feature requests requiring different implementations for each backend.
Tom Gillespie writes:
> Any support for something like this would need to retain backward
> compatibility as well to avoid older versions reformatting the tables
> due to e.g. the presence of a double pipe. I also think that extending
> the table syntax in ways that makes it more complex than it already
> is, will be a non-starter. Thus, an alternate but more likely approach
> would be to allow specification of what cells to merge outside the
> table as is done for formulas. It is not elegant, but it would be a
> layer on top of existing syntax, and it would allow the fundamental
> structure of the table to remain the same -- rows of cells. For
> example #+TBLCELLMERGE: @2-3$1 or something like that. Thoughts?
> On Mon, Nov 2, 2020 at 1:37 PM TEC <firstname.lastname@example.org> wrote:
>> Hi all,
>> This is a pretty major 'feature request', but I think also an
>> When developing large tables, it can often be /necessary/ to start
>> multi-column/row cells for clarity, and sensible exporting
>> As far as I am aware, in Org does not currently have any
>> syntax. The only viable method seems to be re-implementing the
>> using export blocks in every backend you may want to export to (in
>> case, usually TeX + HTML). This is clumsy, difficult to work with,
>> could be avoided should org gain support for multi-col/row syntax.
>> I appreciate that this would constitute a major change both the
>> syntax and the codebase, but I believe such a change is warranted
>> by the
>> advantages it would provide.
>> Both how this can be implemented while minimising/eliminating the
>> of breaking well-formed current table elements, and what syntax
>> may be
>> both acceptable and seem sensible to use.
>> I would anticipate such a feature working by designating two
>> to indicate "add row" and "add column". For example "|" and "-".
>> characters would take affect when /immediately following/ (no
>> space) a
>> cell separator ("|"), and designate the dimensions of the top
>> right cell.
>> | a | b | c |
>> | a | - | | |
>> | - | b | . |
>> | . | | | c |
>> Would be interpreted just as any current table is.
>> | hello | there | you |
>> || two column | cell |
>> Contains a 2x1 cell.
>> | a little | test |
>> |- hello | hi |
>> | two row | you |
>> Contains a 1x2 cell. In a more complex example:
>> | a | b | c |
>> ||-- hi | a |
>> | two x | . |
>> | three | b |
>> | c | - | . |
>> Contains a 2x3 cell.
>> This is just the first syntax that comes to mind, but hopefully
>> general form of this idea seems viable.
>> All the best,
next prev parent reply other threads:[~2020-11-04 9:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 18:14 Tables: missing multi-col/row syntax TEC
2020-11-02 19:45 ` Tom Gillespie
2020-11-02 19:46 ` TEC
2020-11-04 9:23 ` Christian Moe [this message]
2020-11-04 9:28 ` TEC
2020-11-03 10:08 ` David Rogers
2020-11-03 10:35 ` TEC
2020-11-04 2:45 ` David Rogers
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).