From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: emacs-orgmode@gnu.org
Subject: Re: [RFC] Shrink columns dynamically
Date: Tue, 11 Jul 2017 14:24:58 +0200 [thread overview]
Message-ID: <877ezftb39.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87fue3xjsl.fsf@mat.ucm.es> (Uwe Brauer's message of "Tue, 11 Jul 2017 12:03:22 +0000")
Uwe Brauer <oub@mat.ucm.es> writes:
> That would be great indeed. So please don't drop the branch but instead,
> if you have time, try that and I would be more than happy to test it and
> then hopefully narrowing based on cookies could be dropped.
I will as soon as I have an idea about the "that" I have to try.
I don't use column narrowing; I don't know what other users expect from
it either.
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? If the latter, would
a numeric argument for the narrowing command be sufficient? Note that in
this case, it may not be possible to narrow multiple columns at a time.
Also, do we need to commands for that, or would cycling between
expanded/narrowed by some factor (see above)/shrunk states be
sufficient? What about the command line to control multiple columns?
IOW, let's discuss about specifications.
Regards,
next prev parent reply other threads:[~2017-07-11 12:25 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 [this message]
2017-07-11 17:56 ` Kaushal Modi
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=877ezftb39.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--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).