Skip to content

fix(#3117): allow changing filename's casing #3118

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

Closed
wants to merge 0 commits into from

Conversation

ktnlvr
Copy link
Contributor

@ktnlvr ktnlvr commented Apr 28, 2025

Closes (#3117). Seems a little crude, but I don't think there is an easier way.

Copy link
Member

@alex-courtis alex-courtis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've tested the new code on linux and it executes as per the existing, for what that's worth.

  • Have you tested on powershell?

It's not worth checking errors from the fs_ functions; we cannot reasonably action any problems, matching existing code. Checkting nil returns is sufficient.

As this is behind a feature flag, I'm happy to merge it. If there are any issues we'll revert it and call on you to make a fix, as we lack the OS and knowledge to do so.

Copy link
Member

@alex-courtis alex-courtis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've tested the new code on linux and it executes as per the existing, for what that's worth.

  • Have you tested on powershell?
  • Are there any other test cases e.g. command.com?

It's not worth checking errors from the fs_ functions; we cannot reasonably action any problems, matching existing code. Checkting nil returns is sufficient.

As this is behind a feature flag, I'm happy to merge it. If there are any issues we'll revert it and call on you to make a fix, as we lack the OS and knowledge to do so.

@ktnlvr
Copy link
Contributor Author

ktnlvr commented May 1, 2025

Good call, breaks on Windows. Will look into it and fix.

@ktnlvr ktnlvr force-pushed the master branch 2 times, most recently from ec494af to 6503bd2 Compare May 15, 2025 14:18
@ktnlvr ktnlvr requested a review from alex-courtis May 15, 2025 14:20
Copy link
Member

@alex-courtis alex-courtis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, feature flag is in place and you have tested the windows variants.

Code style is failing; take a look at https://github.com/nvim-tree/nvim-tree.lua/blob/master/CONTRIBUTING.md#style

-- implementation of checking for existance is needed.
-- Same holds for WSL, since it can sometimes
-- access Windows files directly.
-- For more details see (#3117).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you.

@ktnlvr
Copy link
Contributor Author

ktnlvr commented May 24, 2025

Well that's interesting. Didn't know GitHub automagically closes the PR if the remote history is overwritten, the fixes to the Windows/Powershell issue are now gone. I'll fix it again in a moment.

@alex-courtis
Copy link
Member

Well that's interesting. Didn't know GitHub automagically closes the PR if the remote history is overwritten, the fixes to the Windows/Powershell issue are now gone. I'll fix it again in a moment.

Perhaps that's a "feature" for pull requests from a fork. I'll add you as a member so that you can push a branch for future PRs.

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

Successfully merging this pull request may close these issues.

2 participants