From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julius Dittmar Subject: Re: Feature request: shrink according to alignment (was Re: Org table columns without width cookies get shrunk on TAB) Date: Mon, 19 Feb 2018 12:29:30 +0100 Message-ID: <97d48f48-a6b4-eaf6-5f31-8e38525b25a6@gmx.de> References: <87po5638ea.fsf@gmail.com> <87o9kqicys.fsf@nicolasgoaziou.fr> <8a0b873e-e9ea-2070-d276-702939e99511@gmx.de> <87bmgll2rh.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53693) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1enjda-0001ht-LB for emacs-orgmode@gnu.org; Mon, 19 Feb 2018 06:29:40 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1enjdV-0003P9-MY for emacs-orgmode@gnu.org; Mon, 19 Feb 2018 06:29:38 -0500 Received: from mout.gmx.net ([212.227.15.19]:60627) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1enjdV-0003NV-Ce for emacs-orgmode@gnu.org; Mon, 19 Feb 2018 06:29:33 -0500 Received: from [192.168.175.209] ([87.139.53.30]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MRXzM-1fByct1MbY-00SdCN for ; Mon, 19 Feb 2018 12:29:31 +0100 In-Reply-To: <87bmgll2rh.fsf@nicolasgoaziou.fr> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org Am 19.02.2018 um 10:58 schrieb Nicolas Goaziou: > Julius Dittmar writes: >> I think what the OP really would like is something like this: remove >> leading whitespace until everything can be displayed or no more leading >> whitespace remains, then truncate at the end if necessary. That way as >> much meaningful contents as possible is displayed. At least that's what >> I would wish in this situation. > > I understand the idea, but the implementation seems tricky. It means Org > may sometimes have to hide characters on both sides of a field. and > sometimes not. It doesn't sound visually appealing. > > I may be wide off the mark, tho. Do you have some specifications in > mind, or at least some examples? Up to the moment I read the original post I wasn't even aware any table cell width restricting syntax exists, so I don't have any full-fledged examples. Not even half-working ones. What I think this was about: Assume, the following table is set up for right-aligned output (that's one of the things I don't know how to do, but that's fine with me): | a very long entry which enforces a long table cell | | a moderately long entry | | a short entry | Assume further that this table is to be displayed showing only 19 characters. As I understand the original post, the outcome at the moment would be something like : | a very long entr... | | ... | | ... | What I would prefer is: | a very long entr... | | a moderately lon... | | a short entry | This does not really mean cutting on both ends, at least not more than org already does. Org already does add or subtract leading or trailing whitespace as needed. The change I'd love would spell something like "first remove all whitespace, then cut (at the end) to length if needed, and then add whitespace to archieve the defined alignment". Regards, Julius