From: Nick Dokos <email@example.com>
Subject: Re: Bug: org-element does not recognize table.el tables [9.4 (release_9.4-53-g23f941 @ /home/nick/elisp/org-mode/lisp/)]
Date: Mon, 21 Dec 2020 16:10:32 -0500 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Bastien <email@example.com> writes:
> Would it be so bad if org-mode decides to stop supporting table.el tables?
I don't use table.el tables so it's easy for me to say "Get rid of them" - but
there may be objections :-)
> I don't see the benefit of supporting both Org tables and tables.el tables,
> and it calls for confusion.
> What do you and everyone else think?
They do exist in a sort of twilight zone: not many people use them
AFAICT, but there is ostensible support and the manual says "Org mode
recognizes such tables and exports them properly", but the bug I sent
shows that that's not correct.
So: fix this bug now that it's been pointed out? Close it as "Will not
fix" with some guidance on what the user is supposed to do ("don't use
table.el tables" is probably the best advice)? Or decide to jettison
table.el support altogether? The first and the last involve real work,
the middle one not, but it's not particularly tasty.
Somebody else will have to make the decision: I'm fine with either of
the exreme ways, not so much with the middle option, but since I'm not
going to do the work, I am in no position to insist.
BTW, I ran into this while looking into this Emacs SE question:
"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler
next prev parent reply other threads:[~2020-12-21 21:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 21:12 Nick Dokos
2020-12-20 17:15 ` Bastien
2020-12-21 7:49 ` Jean Louis
2020-12-21 9:12 ` Bastien
2020-12-21 21:10 ` Nick Dokos [this message]
2020-12-22 5:04 ` Tom Gillespie
2020-12-22 14:55 ` Nick Dokos
2020-12-22 11:45 ` Nicolas Goaziou
2021-01-04 21:26 ` Nick Dokos
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).