From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Bug: turning on column view modifies file [9.0.7 (release_9.0.7-439-g2906e5 @ /home/tews/src/org-mode/lisp/)] Date: Mon, 22 May 2017 14:20:20 +0200 Message-ID: <87lgppf5h7.fsf@nicolasgoaziou.fr> References: <87fufxjeeq.fsf@cert.kernkonzept.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:58098) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dCmK7-00081x-9P for emacs-orgmode@gnu.org; Mon, 22 May 2017 08:20:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dCmK2-0001Kk-DO for emacs-orgmode@gnu.org; Mon, 22 May 2017 08:20:31 -0400 Received: from relay7-d.mail.gandi.net ([217.70.183.200]:35856) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dCmK2-0001KW-8R for emacs-orgmode@gnu.org; Mon, 22 May 2017 08:20:26 -0400 In-Reply-To: <87fufxjeeq.fsf@cert.kernkonzept.com> (Hendrik Tews's message of "Mon, 22 May 2017 13:53:49 +0200") 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: Hendrik Tews Cc: emacs-orgmode@gnu.org Hello, Hendrik Tews writes: > turning on column view might change the buffer, because it > sometimes stores computed values in properties. Is this really > intended? It is. But it only happens if the property already exists in the summarized node. > At least I could not find this behavior described in the > documentation. Would you want to suggest an improvement to the manual? > For instance, in the following buffer > > * a > :PROPERTIES: > :XX: > :END: > ** b > :PROPERTIES: > :XX: 2.0 > :END: > > #+COLUMNS: %6XX{+;%5.1f} %10ITEM(Task) > > turning on column view changes property XX on a. If you turn on > column view a second time (after saving, without undoing), the > buffer is changed again, this time it is an invisible change, > probably rewriting the value for XX on a. This is a bug. I fixed it in maint. Thank you. Regards, -- Nicolas Goaziou