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.
Hello,
This PR adds an
edit_dirs
option that allows users to customize howMkdnEnter
will behave when following a link that points to a directory (e.g.[foo](../bar/)
).Before this PR,
:MkdnEnter
would prompt the user to pick a file name within the given directory:This default behavior is preserved with the new config option
edit_dirs = false
.If
edit_dirs
istrue
, then running:MkdnEnter
on the link[foo](../bar/)
is equivalent to running:edit <path>
where is the absolute version of../bar/
. This enables the user's default directory-browsing plugin (e.g. netrw or oil.nvim) to open the directory.Here's a screenshot after calling
:MkdnEnter
withedit_dirs = true
to edit../bar/
with netrw:If
edit_dirs
is a callback function, then running:MkdnEnter
on[foo](../bar/)
is equivalent to callingcallback(path)
wherepath
is the absolute version of../bar/
.As an example of usage with a callback: in my lua config I currently have
edit_dirs = require('mini.files').open
so that:MkdnEnter
will invoke themini.files
plugin: