From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony E. Bennett Subject: Re: org-open-line inconsistent treatment of marking characters '#' and '*' Date: Sun, 13 Jan 2019 10:12:35 -0500 Message-ID: References: <87h8eeyx6a.fsf@nicolasgoaziou.fr> <87pnt0yfpx.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([209.51.188.92]:50094) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gihRM-0004Dc-I1 for emacs-orgmode@gnu.org; Sun, 13 Jan 2019 10:12:45 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gihRL-00062W-Qr for emacs-orgmode@gnu.org; Sun, 13 Jan 2019 10:12:44 -0500 Received: from [195.159.176.226] (port=59891 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gihRL-000622-K5 for emacs-orgmode@gnu.org; Sun, 13 Jan 2019 10:12:43 -0500 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1gihPC-0000du-4t for emacs-orgmode@gnu.org; Sun, 13 Jan 2019 16:10:30 +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: emacs-orgmode@gnu.org Nicolas Goaziou writes: > Hello, > > Tony E. Bennett writes: > >> How would org verify column 1 is a special column beyond just checking for >> [#*$] which it does already ? > > It would require to check every row. For example, there is no special > column in the following table > > | * | cell | > | 1 | cell | Is 'special first _column_' really an org concept? Recalc seems to only look at each row individually. This table: | * | 7 | 11 | | | 1 | 8 | 11 | | | * | 9 | 11 | | #+TBLFM: $4=$2*$3 Then 'C-u C-c *' gives: | * | 7 | 11 | 77 | | 1 | 8 | 11 | | | * | 9 | 11 | 99 | #+TBLFM: $4=$2*$3 The '1' in @2 did not interfere at all with special recalc of @1 & 3. > However, that would be too long, so maybe not copying anything over the > next row would be the way to go. I hope not as the current behavior is very convenient and with little risk of unintended or unwanted behavior. thanks -- --tony