zsh-workers
 help / color / mirror / code / Atom feed
From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Sebastian Gniazdowski <sgniazdowski@gmail.com>
Cc: Bart Schaefer <schaefer@brasslantern.com>,
	 zsugabubus <zsugabubus@national.shitposting.agency>,
	 "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: Funky list-colors
Date: Thu, 5 Dec 2019 12:19:45 +0100	[thread overview]
Message-ID: <CAN=4vMrj2GUWP4=YtZncJGOWmCyD8wZCNwDUs+s00NgDC35jYw@mail.gmail.com> (raw)
In-Reply-To: <CAKc7PVDzpYUhR7TdoitmiHqvWVH20qGtruA6MhAsYqf2-8Kr5A@mail.gmail.com>

On Thu, Dec 5, 2019 at 12:08 PM Sebastian Gniazdowski
<sgniazdowski@gmail.com> wrote:
> This seems a less powerful than the hacky printable-LS_COLORS idea,
> which I overall like. From experience, such things often result in
> unpredictable and highly surprising + valuable solutions. Maybe it's
> worth opening this door? In a most optimistic scenario, the code would
> have to do a few isprints…

I don't think it's generally possible to figure out by how much the
cursor will move when you write a given string to TTY. If it was
possible, there would be no need for %{...%}.

An alternative would be to add another flag that says that list-colors
should be percent-expanded. Or add a new parameter that is just like
list-colors but gets percent-expanded. Unlike with raw strings,
computing the length of a string that undergoes percent-expansion is a
solved prompt.

Roman.

  reply	other threads:[~2019-12-05 11:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-29 12:21 zsugabubus
2019-11-29 16:06 ` Bart Schaefer
2019-11-29 17:23   ` zsugabubus
2019-11-29 19:22     ` Bart Schaefer
2019-11-29 20:37       ` zsugabubus
2019-12-04 23:27         ` Bart Schaefer
2019-12-05  7:44           ` Oliver Kiddle
2019-12-05 11:07           ` Sebastian Gniazdowski
2019-12-05 11:19             ` Roman Perepelitsa [this message]
2019-12-05 17:40             ` Oliver Kiddle
2019-12-07 20:58           ` zsugabubus
2019-12-07 21:42             ` Oliver Kiddle

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

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

  git send-email \
    --in-reply-to='CAN=4vMrj2GUWP4=YtZncJGOWmCyD8wZCNwDUs+s00NgDC35jYw@mail.gmail.com' \
    --to=roman.perepelitsa@gmail.com \
    --cc=schaefer@brasslantern.com \
    --cc=sgniazdowski@gmail.com \
    --cc=zsh-workers@zsh.org \
    --cc=zsugabubus@national.shitposting.agency \
    /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.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).