emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tom Gillespie <tgbugs@gmail.com>
To: Tim Cross <theophilusx@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Syntax Proposal: Multi-line Table Cells/Text Wrapping
Date: Wed, 31 Mar 2021 23:15:14 -0700	[thread overview]
Message-ID: <CA+G3_PO_RQ1gFkMRn-NCdjdiFW9xokuKz-GYSN_YU6oRFAmWTw@mail.gmail.com> (raw)
In-Reply-To: <87czvw85ym.fsf@gmail.com>

Tim,
   Your concerns are well founded. Essentially any cosmetic extension
to the org table syntax will be an unmaintainable, bug ridden
nightmare and would be an eternal burden on any attempts to formalize
correct behavior. I have a draft of a grammar for a significant
portion of Org syntax (forthcoming), and getting tables right was
quite hard, despite their seeming simplicity. Any surface syntax level
additions would require updating an unknown number of parts of the
codebase to accommodate the change, since every part of org implements
its own parser (e.g. there is already a bug in the interaction between
tables and #+macro: commands containing the pipe character that
org-export implements incorrectly). Relatively speaking, the potential
approaches discussed in Timothy's previous proposal are much more
likely to be tractable. Best,
Tom


      parent reply	other threads:[~2021-04-01  6:16 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17 20:29 Syntax Proposal: Multi-line Table Cells/Text Wrapping Atlas Cove
2021-03-17 21:02 ` Daniele Nicolodi
2021-03-17 22:07 ` Juan Manuel Macías
2021-03-18 13:38   ` Atlas Cove
2021-03-18 14:04     ` Daniele Nicolodi
2021-03-18 15:15     ` Juan Manuel Macías
2021-03-18 14:19 ` Maxim Nikulin
2021-03-18 14:26 ` Timothy
2021-03-18 14:31   ` Atlas Cove
2021-03-18 21:58     ` Tim Cross
2021-03-18 22:41       ` Juan Manuel Macías
2021-03-19  8:08         ` tomas
2021-03-19  8:44           ` Juan Manuel Macías
2021-03-19  8:53             ` tomas
2021-03-19  9:22               ` Juan Manuel Macías
2021-03-19 10:14                 ` tomas
2021-03-19 10:53                   ` Juan Manuel Macías
2021-03-19 11:08                     ` Juan Manuel Macías
2021-03-19 13:43                     ` tomas
2021-03-19 15:07                       ` Juan Manuel Macías
2021-03-20 22:49         ` Samuel Wales
2021-03-21  8:43           ` Juan Manuel Macías
2021-03-19  2:27       ` Timothy
2021-03-19  3:50         ` Tim Cross
2021-03-19  4:02           ` Timothy
2021-03-19 13:33       ` Eric S Fraga
2021-03-19 21:33         ` Tim Cross
2021-03-20  9:19           ` Eric S Fraga
2021-03-20 10:40           ` Juan Manuel Macías
2021-03-20 13:41         ` Andreas Eder
2021-03-20 22:06           ` Tim Cross
2021-03-22 10:54             ` Eric S Fraga
2021-04-01  6:15       ` Tom Gillespie [this message]

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=CA+G3_PO_RQ1gFkMRn-NCdjdiFW9xokuKz-GYSN_YU6oRFAmWTw@mail.gmail.com \
    --to=tgbugs@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=theophilusx@gmail.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
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).