emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Michael Brand <michael.brand@alumni.ethz.ch>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: spreadsheet: column width behavior(s)
Date: Thu, 25 Mar 2010 20:53:40 +0100	[thread overview]
Message-ID: <4BABBF44.5020803@alumni.ethz.ch> (raw)

Hi Carsten, hi all

Are there reasons to only narrow but not to widen columns?

I would like the behavior `fixed width' like

| year | boss                          | facility management assistant  |
|      | <30>                          | <30>                           |
|------+-------------------------------+--------------------------------|
| 2009 | Alice                         | Bob                            |

but with the current implementation get

| year | boss  | facility management assistant |
|      | <30>  | <30>                          |
|------+-------+-------------------------------|
| 2009 | Alice | Bob                           |

which widens the column only if there is too less space left for the column 
content.

As a comparison I can imagine four variants:
<..40>   : `maximum width' (what <40> is today)
<30>     : `fixed width'
<20..>   : `minimum width' (no narrowing)
<20..40> : `width range' (minimum 20, up to 40, narrowing if even longer)

The most commonly used spreadsheet applications offer just one single variant 
out of the above four (right?) and it is `fixed width'. My vote for org-table 
would be the same: That it should support `fixed width' and that this is 
sufficient as the only variant. What is the opinion of other users?

- Michael

             reply	other threads:[~2010-03-25 19:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25 19:53 Michael Brand [this message]
2010-03-26 20:53 ` spreadsheet: column width behavior(s) Carsten Dominik
2010-03-27 13:11   ` Michael Brand
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=4BABBF44.5020803@alumni.ethz.ch \
    --to=michael.brand@alumni.ethz.ch \
    --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).