From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id CEjiJ58W+l5OFQAA0tVLHw (envelope-from ) for ; Mon, 29 Jun 2020 16:28:15 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id WJ25I58W+l5fWgAAbx9fmQ (envelope-from ) for ; Mon, 29 Jun 2020 16:28:15 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id EA8D39401AE for ; Mon, 29 Jun 2020 16:28:14 +0000 (UTC) Received: from localhost ([::1]:35044 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jpwdg-0004MP-Ii for larch@yhetil.org; Mon, 29 Jun 2020 12:28:12 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:52004) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jpwd2-00041u-R7 for emacs-orgmode@gnu.org; Mon, 29 Jun 2020 12:27:32 -0400 Received: from latitanza.investici.org ([82.94.249.234]:57935) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jpwcz-00055G-GY for emacs-orgmode@gnu.org; Mon, 29 Jun 2020 12:27:32 -0400 Received: from mx3.investici.org (unknown [127.0.0.1]) by latitanza.investici.org (Postfix) with ESMTP id CD3501201C0; Mon, 29 Jun 2020 16:27:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anche.no; s=stigmate; t=1593448045; bh=Dc4yyMCYmusYM2yvAF14bL8Y0fwB44WTo+u7Ycp+5K0=; h=Subject:To:References:From:Date:In-Reply-To:From; b=uP3KhpmBUfOwHwEe/W+ta8NIUAs7SRBAL86EJBaDTahYluwbq5bCGjNPeGYXL1jlt rNymRpIqDzxh0e0iPswVs5Ne/Nh/iox3I24szdnQufa2MSbqjpOXSu3aT7xIeXDqxo yAHmK7IEfHCopbqVawAjt4DRhyjDcnjsKHTNUq1s= Received: from [82.94.249.234] (mx3.investici.org [82.94.249.234]) (Authenticated sender: mariotomo@inventati.org) by localhost (Postfix) with ESMTPSA id C4215120171; Mon, 29 Jun 2020 16:27:24 +0000 (UTC) Subject: Re: [PATCH] allow for multiline headers To: emacs-orgmode@gnu.org References: <87wo4bhpkx.fsf@nicolasgoaziou.fr> <87tuzeehk2.fsf@nicolasgoaziou.fr> <87a715e9ju.fsf@nicolasgoaziou.fr> <3e6ee551-4ef7-7d96-93dc-19a4973e1af8@anche.no> <871rm5vslh.fsf@nicolasgoaziou.fr> <381d1495-7d26-6105-6a29-d6f001f7004d@anche.no> <874kquwzjp.fsf@nicolasgoaziou.fr> <87366em3xf.fsf@nicolasgoaziou.fr> From: Mario Frasca Message-ID: Date: Mon, 29 Jun 2020 11:26:45 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0 MIME-Version: 1.0 In-Reply-To: <87366em3xf.fsf@nicolasgoaziou.fr> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Received-SPF: pass client-ip=82.94.249.234; envelope-from=mario@anche.no; helo=latitanza.investici.org X-detected-operating-system: by eggs.gnu.org: First seen = 2020/06/29 12:27:26 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] [fuzzy] X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=_AUTOLEARN X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=anche.no header.s=stigmate header.b=uP3KhpmB; dmarc=none; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Spam-Score: -1.21 X-TUID: b5hdHHezSRfQ Hi Nicolas, sorry for not explaining it clearly.  see, I'm considering from the point of view of a user, who organizes a table in terms of logical units, like a header, one or more body blocks, and a summary line.  these concepts are not yet all supported by the org-table code, and again, I'm not considering what the code implements, just looking at the table from the user's point of view. 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))) 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))) 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? cheers, Mario On 29/06/2020 07:50, Nicolas Goaziou wrote: > Hello, > > Mario Frasca writes: > >> not only this … it could also be like (:header HEADER :body BODY :body >> BODY), that is, repeating block. > I'm not sure about what you mean. > >> I don't know, just doubting how to be more general. >> >> in practice, I'm thinking of the case when I have a header, a body, >> and a summary, and I'm only interested in the header and body, not the >> summary. >> >> just scattered thoughts … who fills in? > There is no such thing as a "table summary" in Org syntax. > > Regards,