-
-
Notifications
You must be signed in to change notification settings - Fork 437
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot lsd ~
on windows
#903
Comments
sound reasonable! /kind feature |
@zwpaper: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Although I agree It looks like there are two funny behaviours in pwsh (7.3.7, on windows):
Notably, tilde expansion works correctly on mac with pwsh 7.3.7 (case 1 here). Related:
Other programs that don't do tilde expansion for pwsh:
|
AFAIK tilde is not expanded for anything, |
then we may need more information to decide whether this should be implemented Maybe a vote? |
Oh yeah you're right, the cmdlets replace the tilde regardless of quotes, so it isn't really an expansion 👍 Other cmdlets like I opened a PR with powershell: PowerShell/PowerShell#20402 We could consider using the same logic as starship here, which uses dirs-next: Do you know any programs that implement tilde replacement? It seems uncommon, a few more examples that don't have it:
|
I'm preparing a PR for this support. Worth noting that this expansion is supported when looking for theme files |
lsd --version
:lsd 1.0.0
echo $TERM
: PowerShell 7echo $LS_COLORS
: -Expected behavior
The same as
ls $env:HOME
Actual behavior
Notes
It appears that
lsd
supports globs itself on windows, I would expect it to do the same for other common shell shorthands like~
that powershell doesn't expand itself.The text was updated successfully, but these errors were encountered: