Open stivens13 opened 1 month ago
Even I'm facing the same issue.
get it, it should be because of the total-size
enabled, I will look deeper into it.
currently, you can try to set the total-size
to false
/kind bug /priority high
@zwpaper: The label(s) priority/high
cannot be applied, because the repository doesn't have them.
/priority high
lsd --version
: latest - 1.1.2installation
:brew install lsd
echo $TERM
: xterm-256colorecho $LS_COLORS
: empty No other environment variables present for eitherls
orlsd
lsd config content ~/.config/lsd/config.yml
``` # == Classic == # This is a shorthand to override some of the options to be backwards compatible # with `ls`. It affects the "color"->"when", "sorting"->"dir-grouping", "date" # and "icons"->"when" options. # Possible values: false, true classic: false # == Blocks == # This specifies the columns and their order when using the long and the tree # layout. # Possible values: permission, user, group, context, size, date, name, inode, links, git blocks: - permission - user - group - size - date - name # == Color == # This has various color options. (Will be expanded in the future.) color: # When to colorize the output. # When "classic" is set, this is set to "never". # Possible values: never, auto, always when: auto # How to colorize the output. # When "classic" is set, this is set to "no-color". # Possible values: default, custom # When "custom" is set, lsd will look in the config directory for `colors.yaml`. theme: default # == Date == # This specifies the date format for the date column. The freeform format # accepts a strftime like string. # When "classic" is set, this is set to "date". # Possible values: date, locale, relative, '+More on system:
Expected behavior
ls -l
,ls -Al
andls -al
run successfully in root,.ssh
, and user-createddev
dirs (Notecommand
is just to escapels
alias tolsd
in fish shell)Actual behavior
lsd -l
,lsd -Al
andlsd -al
fail withOperation not permitted (os error 1)
andPermission denied (os error 13)
in different directories but have mixed fail logic. (Tested inWarp
,iTerm2
and mac built-inTerminal
apps, infish
andzsh
shells) (RUST_BACKTRACE=1 lsd ...
produces same result)lsd -l
,lsd -Al
andlsd -al
fail in root dirlsd -al
fail in.ssh
anddev
directoresHowever,
lsd -l
andlsd -Al
do not fail in.ssh
anddev
dirsIn addition
Running
lsd
in iTerm and Terminal called access prompt on various resources like below, including Full Disk Access. Even after accepting all of them,lsd
still fails the same way as it does in Warp