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 t
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 unlike
On 7/25/18 12:34 PM, Michal Pesa wrote:
> Would it also be possible to add documentation for the characters denoting
> a file’s typein "visible-stats"?
They're basically the standard characters that `ls' has used forever.
If you'd like to submit a patch, I'll take a look at it.
Chet
--
``The ly
It would be obvious then what color exactly needs to be change in the
LS_COLORS variable if a different color was desired.
On 7/25/2018 8:44 PM, Chet Ramey wrote:
On 7/24/18 5:16 PM, Michal Pesa wrote:
Hello,
documentation for the readline variable "colored-completion-prefix" doesn't
state wh
On 7/24/18 5:16 PM, Michal Pesa wrote:
> Hello,
> documentation for the readline variable "colored-completion-prefix" doesn't
> state which part of the "LS_COLORS" is used.
Does it need to? I don't see that adding anything to the user experience.
The only real need is to specify that if LS_COLORS
Would it also be possible to add documentation for the characters
denoting a file’s typein "visible-stats"?
On 7/24/2018 11:16 PM, Michal Pesa wrote:
Hello,
documentation for the readline variable "colored-completion-prefix"
doesn't state which part of the "LS_COLORS" is used.
Thank you for
