From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Brand <michael.brand@alumni.ethz.ch>
Subject: Re: spreadsheet: column width behavior(s)
Date: Sat, 27 Mar 2010 14:11:38 +0100
Message-ID: <4BAE040A.8080906@alumni.ethz.ch>
References: <4BABBF44.5020803@alumni.ethz.ch>
	<1E0F2C3A-5F85-42BA-9232-3CB3DE4CDAFB@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NvVnl-0003v7-Tr
	for emacs-orgmode@gnu.org; Sat, 27 Mar 2010 09:11:45 -0400
Received: from [140.186.70.92] (port=33353 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NvVnk-0003ug-GU
	for emacs-orgmode@gnu.org; Sat, 27 Mar 2010 09:11:45 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <michael.brand@alumni.ethz.ch>) id 1NvVnj-0005ik-Bv
	for emacs-orgmode@gnu.org; Sat, 27 Mar 2010 09:11:44 -0400
Received: from mail05.solnet.ch ([212.101.4.139]:59601)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <michael.brand@alumni.ethz.ch>) id 1NvVnj-0005iE-5q
	for emacs-orgmode@gnu.org; Sat, 27 Mar 2010 09:11:43 -0400
In-Reply-To: <1E0F2C3A-5F85-42BA-9232-3CB3DE4CDAFB@gmail.com>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=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: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>

>> 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             |