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: Tue, 22 Dec 2020 09:55:40 -0500 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Bastien <email@example.com> writes:
> Hi Nick,
> Nick Dokos <firstname.lastname@example.org> writes:
>> Consider an Org mode file with a table.el table (which I made by
>> first constructing an Org mode table and then usind `C-c ~' to
>> convert it):
> Would it be so bad if org-mode decides to stop supporting table.el tables?
> 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?
I don't use table.el tables. The only reason I submitted the bug
report was because I was trying to investigate this Emacs SE question:
In the process, I discovered that the LaTeX file was broken and traced
it back to org-element. Note that the manual says:
"Org mode recognizes such tables and exports them properly."
(info "(org) Cooperation")
So there are three roads ahead as I see it:
- Fix the bug in org-element and make sure that table.el tables are
- Do not fix the bug. Instead, tear out table.el support from Org mode
code and fix the manual to say so.
- Do not fix the bug (and do nothing else).
I presume the third choice is distasteful to everybody, but that's
going to be the default choice unless somebody volunteers to do either
of the other two.
Either of the first two choices requires work. From my POV, it does
not matter which of the two is done: if somebody volunteers to do
either, I am not going to object (and I suspect, almost nobody else
will either: if the second course is chosen, there may be some table.el
users who would object to losing it, but if so, they should volunteer
to fix the bug).
My 0.02 kopek.
"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-22 14:56 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
2020-12-22 5:04 ` Tom Gillespie
2020-12-22 14:55 ` Nick Dokos [this message]
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).