feat(config): add override_cwd option to control cwd behavior
#35
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I really like this plugin, but having it automatically override the current working directory has been inconvenient, as it affects other plugins and settings that rely on
vim.fn.getcwd(), such as LSPs and fuzzy finders.This PR adds a new configuration option:
override_cwd. By default, it is set totrueto preserve the existing behavior of changing working directory when opening dired.nvim. Setting it tofalseprevents dired from overriding the user’s cwd and instead uses the directory relative to the currently opened file, similar tonetrw.