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

On Windows file/folder search conflicts with free-cwd #12

Open
eugenesvk opened this issue Feb 16, 2021 · 0 comments
Open

On Windows file/folder search conflicts with free-cwd #12

eugenesvk opened this issue Feb 16, 2021 · 0 comments

Comments

@eugenesvk
Copy link

There is a nifty xontrib free-cwd that allows not to lock a current folder:

Windows only xontrib, to release the lock on the current directory whenever the prompt is shown. Enabling this will allow the other programs or Windows Explorer to delete or rename the current or parent directories. Internally, it is accomplished by temporarily resetting CWD to the root drive folder while waiting at the prompt. This only works with the prompt_toolkit backend and can cause cause issues if any extensions are enabled that hook the prompt and relies on os.getcwd()

However, this breaks fzf file/folder search within the current folder as the current folder is reset to root, so the fzf search also starts from root :(

Is there any way to marry the two by somehow getting the current folder value before it's reset?
If not, might be worth documenting this limitation

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