Closed mopp closed 6 years ago
Thank you for the PR!
I think it can be replaced with :Vaffle %:h
. I have a concern that adding such command leads to an increase in similar commands. (e.g. :VaffleParent
, :VaffleRoot
, :VaffleNextSibling
, etc.)
What do you think about this?
Yes, you are right ;)
However, there are some commands which everyone would like to use many times.
So, The :VaffleCurrentBuffer
is a command like that, and these command should be defined in the plugin I think.
of cause, it is not so easy to determine the commands because it depends on individual usage.
The following is just my opinion.
Vaffle.vim is your plugin, then, you can reject this PR if you do not want.
Because we have a alternative way :Vaffle %:h
(and it is better to append the document)
Thank you for sharing your opinion! I partially agree with you but the concept — Vaffle is simple — is more important thing than that, sorry.
Objective
:VaffleCurrentBuffer
We can open a directory of a current buffer.
Drawbacks
None