emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>, emacs-orgmode@gnu.org
Subject: Re: [RFC] Shrink columns dynamically
Date: Tue, 11 Jul 2017 17:56:44 +0000	[thread overview]
Message-ID: <CAFyQvY3QM3+t-_TN9-p-GM3puFczA5EBej+i_dCkhfWHSh8SCQ@mail.gmail.com> (raw)
In-Reply-To: <877ezftb39.fsf@nicolasgoaziou.fr>


[-- Attachment #1.1: Type: text/plain, Size: 2238 bytes --]

On Tue, Jul 11, 2017 at 8:26 AM Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:

>
> I don't use column narrowing; I don't know what other users expect from
> it either.
>

I use column narrowing when I need to fit all columns of an org table in a
screen width (roughly 100 chars wide).

If I have a column called "Description" that can have 100's of characters
in a cell, I'd like to not push the other columns to the right outside the
screen.

- Having line truncation on hides the columns that go beyond the screen
width
- Disabling line truncation makes org tables difficult to read
- So the column width cookie is the best thing we have at the moment

[image: image.png]
The latter table without truncation enabled:
[image: image.png]

Are there some rules to decide what would be an acceptable narrowing
> (e.g., narrow columns larger than 10 characters by half or to 20
> characters, whichever is the smaller) or do users really need to decide
> piece-wise the number of characters needed?


In my use case above, I would do the narrowing just enough to have the
tables fit in my usual window widths.


> If the latter, would
> a numeric argument for the narrowing command be sufficient?


If the column widths do not get saved, it would get tedious to repeat those
narrowing steps each time the same Org file is opened.

Note that in
> this case, it may not be possible to narrow multiple columns at a time.
>

Narrowing multiple columns would be a necessity. That, plus doing so
automatically when an Org file is opened. See above screenshots to see my
typical use of column width cookies.


> Also, do we need to commands for that, or would cycling between
> expanded/narrowed by some factor (see above)/shrunk states be
> sufficient?


I typically just set it and forget it. If I need to remove the widening, I
comment out the "#+STARTUP: align" line and do revert-buffer.


> IOW, let's discuss about specifications.
>

1. Need to save the column narrowed state somehow individually for each
column, specific to a table in a document.
2. Alternative: Look at the window width and calculate the factor by which
all columns should be narrowed so that the whole table fits the window
(Sounds very complicated).
-- 

Kaushal Modi

[-- Attachment #1.2: Type: text/html, Size: 3726 bytes --]

[-- Attachment #2: image.png --]
[-- Type: image/png, Size: 41611 bytes --]

[-- Attachment #3: image.png --]
[-- Type: image/png, Size: 29641 bytes --]

  reply	other threads:[~2017-07-11 17:58 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-10 12:12 [RFC] Shrink columns dynamically Nicolas Goaziou
2017-07-10 14:36 ` Uwe Brauer
2017-07-10 14:43   ` Nicolas Goaziou
2017-07-10 19:47     ` Uwe Brauer
2017-07-10 20:14       ` Nick Dokos
2017-07-10 20:59       ` Nicolas Goaziou
2017-07-11  6:27         ` Uwe Brauer
2017-07-11  7:54           ` Nicolas Goaziou
2017-07-11  8:35             ` Uwe Brauer
2017-07-11 11:41               ` Nicolas Goaziou
2017-07-11 12:03                 ` Uwe Brauer
2017-07-11 12:24                   ` Nicolas Goaziou
2017-07-11 17:56                     ` Kaushal Modi [this message]
2017-07-11 19:09                       ` Nicolas Goaziou
2017-07-11 19:23                         ` Kaushal Modi
2017-07-12  7:22                           ` Colin Baxter
2017-07-12 10:17                             ` Nicolas Goaziou
2017-07-12 16:06                               ` Colin Baxter
2017-07-12 19:14                               ` Rick Frankel
2017-07-27 11:47                                 ` Nicolas Goaziou
     [not found]                             ` <158a779e34564ef98104c442384dadd3@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-07-12 16:10                               ` Eric S Fraga
2017-07-16 10:54                                 ` B.V. Raghav
2017-07-27 10:14                                   ` Nicolas Goaziou
2017-07-27 10:11                                 ` Nicolas Goaziou
2017-07-31 22:29                                   ` Adam Porter
2017-08-05 22:56                                     ` Nicolas Goaziou
     [not found]                                 ` <e59b6e794bff46c29380611204d00402@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-07-27 10:49                                   ` Eric S Fraga
2017-08-05 22:54                                     ` Nicolas Goaziou
2017-08-19 16:54                                       ` Nicolas Goaziou
2017-09-06 13:29                                         ` Nicolas Goaziou
2017-07-11 20:21                         ` Uwe Brauer
2017-07-11  9:32             ` Uwe Brauer
2017-07-10 22:11     ` Kaushal Modi
2017-07-11  6:16       ` Michael Brand
2017-07-11 11:18         ` Deleting org table columns during export (Was: [RFC] Shrink columns dynamically) Kaushal Modi
2017-07-11 16:43           ` Michael Brand
2017-07-11 11:47         ` [RFC] Shrink columns dynamically Nicolas Goaziou
2017-07-11 16:40           ` Michael Brand

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=CAFyQvY3QM3+t-_TN9-p-GM3puFczA5EBej+i_dCkhfWHSh8SCQ@mail.gmail.com \
    --to=kaushal.modi@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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).