Re: Lacking documentation of colored-completion-prefix

From	Michal Pesa <pesathem@gmail.com>
Newsgroups	gnu.bash.bug
Subject	Re: Lacking documentation of colored-completion-prefix
Date	2018-07-31 18:17 +0200
Message-ID	<mailman.4475.1533053858.1292.bug-bash@gnu.org> (permalink)
References	<ea255133-dacb-742b-828f-be0d12486d43@gmail.com> <c25f30b0-d745-7f55-b83e-468e1a41df23@case.edu> <05b133b9-6a94-1ad0-4df4-f44954ef45d8@gmail.com> <835fffbf-3770-6a51-d7d6-b232d0fe3b00@case.edu>

Show all headers | View raw

That's exactly what I would welcome in the manual. Something as simple 
as: The socket color "so" of the LS_COLORS variable is used as the 
prefix color.

Regards.


On 7/31/2018 5:09 PM, Chet Ramey wrote:
> On 7/25/18 2:48 PM, Michal Pesa wrote:
>> It would be obvious then what color exactly needs to be change in the
>> LS_COLORS variable if a different color was desired.
> I don't see setting the color in stone as helping the user experience.
> It's the same color as sockets right now, since that's unlikely to be
> encountered during normal filename completion, but that could change.

Back to gnu.bash.bug | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Re: Lacking documentation of colored-completion-prefix Michal Pesa <pesathem@gmail.com> - 2018-07-31 18:17 +0200
  Re: Lacking documentation of colored-completion-prefix himat415@gmail.com - 2019-02-03 13:17 -0800

csiph-web