From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Mario Frasca <mario@anche.no>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] allow for multiline headers
Date: Sat, 13 Jun 2020 00:44:14 +0200 [thread overview]
Message-ID: <87wo4bhpkx.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <d9f86ea0-0ee6-0ff0-219a-e0dbc27e1896@anche.no> (Mario Frasca's message of "Fri, 12 Jun 2020 12:14:17 -0500")
Hello,
Mario Frasca <mario@anche.no> writes:
> (org-table-to-lisp): simplify code, changing a `while' to a
> `cl-loop', remove leading `hline' symbols from result, edit
> documentation to reflect change.
Please don't. Even if it has its uses, cl-loop is a complicated
non-Lispy beast, and introducing it somewhere is seldom
a simplification.
If you think cl-loop is more efficient in this function, please provide
benchmarks. But I really hope cl-loop (or cl-do, for that matter) is not
going to sprout everywhere.
Also, the first hline is used to determine where to end the header.
A table starting with a hline has no header. Therefore, I suggest to
avoid removing hlines at the beginning of a table, we would lose
information.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2020-06-12 22:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 17:14 [PATCH] allow for multiline headers Mario Frasca
2020-06-12 22:44 ` Nicolas Goaziou [this message]
2020-06-13 20:20 ` Mario Frasca
2020-06-13 21:20 ` Mario Frasca
2020-06-13 22:18 ` Nicolas Goaziou
2020-06-13 23:03 ` Mario Frasca
2020-06-14 19:23 ` Nicolas Goaziou
[not found] ` <3e6ee551-4ef7-7d96-93dc-19a4973e1af8@anche.no>
[not found] ` <871rm5vslh.fsf@nicolasgoaziou.fr>
2020-06-27 15:39 ` Mario Frasca
2020-06-28 23:17 ` Nicolas Goaziou
2020-06-29 0:27 ` Mario Frasca
2020-06-29 12:50 ` Nicolas Goaziou
2020-06-29 16:26 ` Mario Frasca
2020-06-29 18:36 ` Nicolas Goaziou
2020-06-29 22:01 ` Mario Frasca
2020-07-01 10:46 ` Nicolas Goaziou
2020-07-01 12:06 ` Mario Frasca
2020-07-04 8:58 ` Nicolas Goaziou
2020-07-04 13:47 ` Mario Frasca
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=87wo4bhpkx.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=mario@anche.no \
/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).