From: TEC <firstname.lastname@example.org> To: org-mode-email <email@example.com> Subject: Tables: missing multi-col/row syntax Date: Tue, 03 Nov 2020 02:14:33 +0800 Message-ID: <firstname.lastname@example.org> (raw) Hi all, This is a pretty major 'feature request', but I think also an important one. When developing large tables, it can often be /necessary/ to start using multi-column/row cells for clarity, and sensible exporting results. As far as I am aware, in Org does not currently have any multi-col/row syntax. The only viable method seems to be re-implementing the table using export blocks in every backend you may want to export to (in my case, usually TeX + HTML). This is clumsy, difficult to work with, and could be avoided should org gain support for multi-col/row syntax. I appreciate that this would constitute a major change both the Org's 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 chance 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 characters to indicate "add row" and "add column". For example "|" and "-". These characters would take affect when /immediately following/ (no space) a cell separator ("|"), and designate the dimensions of the top right cell. Example: | a | b | c | |---+---+---| | a | - | | | | - | b | . | | . | | | c | Would be interpreted just as any current table is. However, | 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 the general form of this idea seems viable. All the best, Timothy.
next reply other threads:[~2020-11-02 18:37 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-02 18:14 TEC [this message] 2020-11-02 19:45 ` Tom Gillespie 2020-11-02 19:46 ` TEC 2020-11-04 9:23 ` Christian Moe 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
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://orgmode.org * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ /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
Org-mode mailing list This inbox may be cloned and mirrored by anyone: git clone --mirror https://orgmode.org/list/0 list/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 list list/ https://orgmode.org/list \ firstname.lastname@example.org public-inbox-index list Example config snippet for mirrors. Newsgroups are available over NNTP: nntp://news.yhetil.org/yhetil.emacs.orgmode nntp://news.gmane.io/gmane.emacs.orgmode AGPL code for this site: git clone https://public-inbox.org/public-inbox.git