From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Eddward DeVilla" Subject: Re: Re: Table questions Date: Tue, 19 Dec 2006 16:28:51 -0600 Message-ID: References: <1oac1qih6j.fsf@bass.biostat.umn.edu> <1x3b7bbzco.fsf@bass.biostat.umn.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GwnSD-0008QG-It for emacs-orgmode@gnu.org; Tue, 19 Dec 2006 17:28:57 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GwnS9-0008Nh-Pz for emacs-orgmode@gnu.org; Tue, 19 Dec 2006 17:28:57 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GwnS9-0008NP-Hz for emacs-orgmode@gnu.org; Tue, 19 Dec 2006 17:28:53 -0500 Received: from [66.249.92.169] (helo=ug-out-1314.google.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GwnS8-0006xC-Ac for emacs-orgmode@gnu.org; Tue, 19 Dec 2006 17:28:52 -0500 Received: by ug-out-1314.google.com with SMTP id j3so2332457ugf for ; Tue, 19 Dec 2006 14:28:51 -0800 (PST) In-Reply-To: <1x3b7bbzco.fsf@bass.biostat.umn.edu> Content-Disposition: inline List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Michael Cc: emacs-orgmode@gnu.org On 12/19/06, Michael wrote: > On 18 Dec 2006, Carsten Dominik wrote: > > > On Dec 14, 2006, at 17:19, Michael wrote: > > You cannot, at least currently. I am not sure how well this would > > work, because the table editor makes it very easy to swap rows, columns, > > to add and delete columns, and such references would become invalid > > unless one would carefully track these changes. > > I agree that you probably don't want to exactly replace the full power of > Excel. But this simple feature makes it possible to keep track of simple > data. I won't mind having to redo the formula after row swapping etc., > which I think won't happen so often for a given table anyway. I know I use column swapping a lot. I haven't got formulas down yet, but if I where to use them in a table where I'm liable to column swap, I'd probably use named columns. (That's supported, right?) Row swapping would be trickier, but I don't do that much unless I'm sorting based on a field, and if I'm sorting, I don't think I'd do much more than ask for "$named_column one row up". The ability to ask for a named column in a row relative to the current one might be reasonably safe without having to change formulas. Swapping rows could still bite the user if he didn't plan things out right. Edd