Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #14425 > unrolled thread

Re: Lacking documentation of colored-completion-prefix

Started byMichal Pesa <pesathem@gmail.com>
First post2018-07-31 18:17 +0200
Last post2019-02-03 13:17 -0800
Articles 2 — 2 participants

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  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

#14425 — Re: Lacking documentation of colored-completion-prefix

FromMichal Pesa <pesathem@gmail.com>
Date2018-07-31 18:17 +0200
SubjectRe: Lacking documentation of colored-completion-prefix
Message-ID<mailman.4475.1533053858.1292.bug-bash@gnu.org>
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.

[toc] | [next] | [standalone]


#15044

Fromhimat415@gmail.com
Date2019-02-03 13:17 -0800
Message-ID<2963e2ff-749f-4c9a-95c1-f612195492f7@googlegroups.com>
In reply to#14425
I agree, I had to find this thread just to figure this out in order to change my prefix highlighting color.

On Tuesday, July 31, 2018 at 12:17:39 PM UTC-4, Michal Pesa wrote:
> 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.

[toc] | [prev] | [standalone]


Back to top | Article view | gnu.bash.bug


csiph-web