emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Michael Brand <michael.brand@alumni.ethz.ch>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: spreadsheet: column width behavior(s)
Date: Sat, 27 Mar 2010 14:11:38 +0100	[thread overview]
Message-ID: <4BAE040A.8080906@alumni.ethz.ch> (raw)
In-Reply-To: <1E0F2C3A-5F85-42BA-9232-3CB3DE4CDAFB@gmail.com>

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

  reply	other threads:[~2010-03-27 13:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25 19:53 spreadsheet: column width behavior(s) Michael Brand
2010-03-26 20:53 ` Carsten Dominik
2010-03-27 13:11   ` Michael Brand [this message]
2010-03-27 15:15     ` Carsten Dominik
2010-03-27 17:15       ` Michael Brand
2010-03-27 17:27         ` Carsten Dominik
2010-03-27 18:05 ` Samuel Wales
2010-03-28 12:40   ` Carsten Dominik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BAE040A.8080906@alumni.ethz.ch \
    --to=michael.brand@alumni.ethz.ch \
    --cc=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).