From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: spreadsheet: column width behavior(s) Date: Sat, 27 Mar 2010 16:15:01 +0100 Message-ID: <056252B3-42C3-4DFE-A4FE-774F57C235D6@gmail.com> References: <4BABBF44.5020803@alumni.ethz.ch> <1E0F2C3A-5F85-42BA-9232-3CB3DE4CDAFB@gmail.com> <4BAE040A.8080906@alumni.ethz.ch> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NvXjB-0001Yw-PY for emacs-orgmode@gnu.org; Sat, 27 Mar 2010 11:15:09 -0400 Received: from [140.186.70.92] (port=59548 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NvXj9-0001XA-1r for emacs-orgmode@gnu.org; Sat, 27 Mar 2010 11:15:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1NvXj6-0002ZG-1C for emacs-orgmode@gnu.org; Sat, 27 Mar 2010 11:15:05 -0400 Received: from ey-out-1920.google.com ([74.125.78.149]:25378) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1NvXj5-0002Z0-Ss for emacs-orgmode@gnu.org; Sat, 27 Mar 2010 11:15:03 -0400 Received: by ey-out-1920.google.com with SMTP id 4so910893eyg.34 for ; Sat, 27 Mar 2010 08:15:03 -0700 (PDT) In-Reply-To: <4BAE040A.8080906@alumni.ethz.ch> 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 Brand Cc: Org Mode On Mar 27, 2010, at 2:11 PM, Michael Brand wrote: >>> Are there reasons to only narrow but not to widen columns? >> I think this is really the only thing that makes sense. Why would >> you want it any wider, given the limited amount of screen real >> estate we have here? I don't think it would be difficult to make >> it behave the way you request, but I don't think I would ever >> use widening fields. When would you want to use this? > > I see, there _are_ reasons for `maximum width' (and other variants > would be only additional if ever). > > The variant `fixed width' can be useful for the following timetable. > Here it is achieved with the field content > `<= widen' > in the last row. > > several columns with the same width: > > |-------+-----------+-----------+-----------+-----------+-----------| > | | Mon | Tue | Wed | Thu | Fri | > |-------+-----------+-----------+-----------+-----------+-----------| > | 8:15 | Math | Compute=> | - | Math | Compute=> | > | 13:15 | - | Math | Compute=> | - | Math | > |-------+-----------+-----------+-----------+-----------+-----------| > | / | <9> | <9> | <9> | <9> | <9> | > | / | <= => | <= => | <= => | <= => | <= => | > > instead of: > > |-------+------+--------------+--------------+------+--------------| > | | Mon | Tue | Wed | Thu | Fri | > |-------+------+--------------+--------------+------+--------------| > | 8:15 | Math | Computer S=> | - | Math | Computer S=> | > | 13:15 | - | Math | Computer S=> | - | Math | > |-------+------+--------------+--------------+------+--------------| > | / | | <12> | <12> | | <12> | > > or even: > > | Mon | 8:15 | Math | > | Tue | 8:15 | Computer Science | > | Tue | 13:15 | Math | > | Wed | 13:15 | Computer Science | > | Thu | 8:15 | Math | > | Fri | 8:15 | Computer Science | > | Fri | 13:15 | Math | Yes, thinking more about it, I do agree that a fixed width makes a lot of sense as the application of . It does now work like this. Thanks! - Carsten