Skip to content
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

Correctly handle ~-expansion #127

Open
tom-seddon opened this issue Apr 23, 2023 · 0 comments
Open

Correctly handle ~-expansion #127

tom-seddon opened this issue Apr 23, 2023 · 0 comments

Comments

@tom-seddon
Copy link
Owner

tom-seddon commented Apr 23, 2023

Shouldn't the shell do this for you? But clearly it doesn't in beeblink's case. I'm sure this used to work. Or maybe it never has, and I somehow never noticed/never got round to adding an issue.

See nodejs/node#684 - looks like Node won't change this.

There's a helper function that's been there for ages but never used, so maybe I did notice this at some point:

export function getTildeExpanded(pathString: string): string {
- this would do as a first pass.

https://www.npmjs.com/package/untildify? Looks like it might not handle the ~USER syntax, so little current advantage to using this. Does this even matter?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant