should we hide the user/group block when permission set to attribute in windows

[Jaehaks]

Version

• latest

version

v1.1.1

What OS are you seeing the problem on?

Windows

installation

scoop install lsd

term

windows terminal : cmd.exe

ls-colors

no

What happened?

if I set permission = rwx in config.yaml, 
It has delay to show result under any other lsd command
like lsd -al, lsd, etc.. except of lsd --version.
Delay is about 3~4s.

What expected?

there are not much delay between permission settings

What else?

No response

[Jaehaks]

Plus, If I set permission = attribute, it works so fast but it dose not show user/group name . It shows just "?" characters

[zwpaper]

Hi @Jaehaks thanks for the report, this is known and as a workaround for the windows users, please check #911, and #200

as for the questioned user and group, please use config.yaml to hide the user and group blocks.

but for user ux, maybe we should hide the user/group by default for windows users?

[zwpaper]

let me change the title and we can discuss the hiding user/group, leave the performance to #378

/retitle should we hide the user/group block when permission set to attribute in windows

[yorah]

but for user ux, maybe we should hide the user/group by default for windows users?

Took me some time to find the relevant issue when investigating those question marks. Hiding uiser/group block when permission is set to attribute (which is the default on windows) seem like the right thing to do from an ux perspective.