From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Clocktable creates superfluous columns Date: Sun, 05 Mar 2017 18:10:12 +0100 Message-ID: <87k2837iq3.fsf@nicolasgoaziou.fr> References: <87h93r1ty8.fsf@nicolasgoaziou.fr> <87r32fzfq4.fsf@Rainer.invalid> <87zih38jq7.fsf@nicolasgoaziou.fr> <87fuiui33m.fsf@Rainer.invalid> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37052) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ckZfl-0003LE-9Q for emacs-orgmode@gnu.org; Sun, 05 Mar 2017 12:10:18 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ckZfk-0006uI-90 for emacs-orgmode@gnu.org; Sun, 05 Mar 2017 12:10:17 -0500 Received: from relay4-d.mail.gandi.net ([2001:4b98:c:538::196]:55112) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ckZfk-0006tt-2a for emacs-orgmode@gnu.org; Sun, 05 Mar 2017 12:10:16 -0500 In-Reply-To: <87fuiui33m.fsf@Rainer.invalid> (Achim Gratz's message of "Fri, 03 Mar 2017 20:15:25 +0100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Achim Gratz Cc: emacs-orgmode@gnu.org Hello, Achim Gratz writes: > Nicolas Goaziou writes: >> I'm a bit surprised that was the case. When fixing the clocktable, >> I also wondered what was the expected behaviour in that case, did some >> quick tests and came to the conclusion empty columns were fine. > > I already said that I can see the utility of that in some cases, it's > just a user-visible change that I found not documented. What I meant is that upon testing old revisions, empty columns were also left over. Hence my surprise, since our experiences differ. > I'll try to make some time for that. Thank you. > OTOH, if it's just a matter of implementing another customization > option and code to pick up on that, we may not even need to know when > it changed. Honestly I'm curious to know how it was done. AFAICT, it entails to compute deepest headline level across all files in scope. I don't think there was such code. Also, yet another customization may not be needed, as both behaviours sounds fine to me. Regards, -- Nicolas Goaziou