Resolves #9875
https://github.com/vim/vim/pull/11290
(1 file)
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
I actually think there is never a point in "filetype detect" to try figure out the filetype for a directory.
Or we should just set filetype to "directory".
How about that? Would that break anything?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Actually, it appears "filetype detect" already rejects directories. In the netrw plugin it uses a buffer to display the directory contents, but that buffer is not a directory itself.
Hmm, I have trouble reproducing the original problem. How do you get the filetype to be something else than "netrw"?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
I guess this is related to #9099 which is easy to reproduce.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
OK, I'll include it. Let me close the other issues and leave this one open for Charles.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
I’ve reproduced this using :Explore and entering a directory under a .vim or .com and then bubbling back up to the parent directory, that corresponds to setting ft={vim,dcl} respectively - while it should be netrw.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
Anything you need from me to push this forward @cecamp ?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
@brammool While resolving the merge conflicts I saw that 3c053a1 was merged into master yesterday.
Which includes the gist of this patch.
Should we then close this PR?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
I tested out 3c053a1 and what’s on main and it works as expected.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
Closed #11290.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()