emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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: Mon, 29 Jun 2020 20:36:46 +0200	[thread overview]
Message-ID: <87imf9lnwh.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <e4c47e8a-4fcc-7ecc-d4b3-37cfad7fac49@anche.no> (Mario Frasca's message of "Mon, 29 Jun 2020 11:26:45 -0500")

Mario Frasca <mario@anche.no> writes:

> again, my idea is that we're describing something new, and I'm
> wondering what lisp construct could be used to describe a table like
> this one:
>
> | h1 | h2 | h3 |
> |----+----+----|
> | 11 | 12 | 13 |
> | 21 | 22 | 23 |
> | 31 | 32 | 33 |
> |----+----+----|
> | a1 | a2 | a3 |
> | b1 | b2 | b3 |
> |----+----+----|
> |  5 |  8 |  9 |
>
> and my guess in the above case would be '(:header ("h1" "h2"
> "h3") :body ((11 12 13)(21 22 23)(31 32 33)) :body ((a1 a2 a3)(b1 b2
> b3)) :body ((5 8 9)))

These are called "row groups" in ox.el, but I don't think we should
parse them like the above. It is easy enough to get this kind of result
just walking through the table.

> with a option for collapsing all :body parts into one, like in
> '(:header ("h1" "h2" "h3") :body ((11 12 13)(21 22 23)(31 32 33)(a1 a2
> a3)(b1 b2 b3)(5 8 9)))
>
> with a option for separating the last row (if the one-but-last is
> a 'hline) as a summary, like in '(:header ("h1" "h2" "h3") :body ((11
> 12 13)(21 22 23)(31 32 33)) :body ((a1 a2 a3)(b1 b2 b3)) :summary (5
> 8 9))
>
> or using both options, like in '(:header ("h1" "h2" "h3") :body ((11
> 12 13)(21 22 23)(31 32 33)(a1 a2 a3)(b1 b2 b3)) :summary (5 8 9))
>
> your suggestion as a cons cell would only cover the first case, as in
> '(("h1" "h2" "h3") . ((11 12 13)(21 22 23)(31 32 33)(a1 a2 a3)(b1 b2
> b3)(5 8 9)))

You're missing `hline' symbols in the body. I didn't suggest to remove
them, except for the separator between the header and the body, and
trailing separators.

> in my very brief experience with org-tables, mostly from the point of
> view of org-plot, I think this (separating the bottom "summary" line)
> would be useful (I had to remove the "country summary" bottom line
> from a demographics histogram table).  for sure, if I follow your hint
> to use gnuplot code and refer to the table, then org-plot can stay as
> it is now.  in fact it would not need any maintenance, would it?

You can indeed extract a specific part of the table as an input of
a gnuplot code block. IMO, Org Plot should be very basic, and complexity
should go into Babel code blocks, which are more capable.

Regards,


  reply	other threads:[~2020-06-29 18:39 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
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 [this message]
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=87imf9lnwh.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).