You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just downloaded & installed the extension. Only glitch is "make" produced xmledit-1.9.1.vmb.
I glanced at the vimball source code, and it seems to support both extensions, but I can't quickly distinguish in what cases either would apply. (Microsoft has used .vba for MS Visual Basic scripts for years, so it makes sense Vimball would want a different file extension...)
I don't want to update the xmledit documention based on 5 minutes of glancing, but suggest updating README to indication either file extension works.
The text was updated successfully, but these errors were encountered:
I looked at the Makefile and It is making .vba files. This is the expected extension per the official docs
I don't understand how you got .vmb. In any case I doubt Vim cares as you usually install vimballs by just sourcing it in which case the extension is not important.
Why does the README need updating? It reads as it should based on .vba.
Also bear in mind that this plugin has not been maintained in quite some time. Unless I get a PR I'm not going to spend effort on it. Also any change will be out of sync with the one bundled with Vim itself as I am no longer active in the Vim development forums.
Just downloaded & installed the extension. Only glitch is "make" produced xmledit-1.9.1.vmb.
I glanced at the vimball source code, and it seems to support both extensions, but I can't quickly distinguish in what cases either would apply. (Microsoft has used .vba for MS Visual Basic scripts for years, so it makes sense Vimball would want a different file extension...)
I don't want to update the xmledit documention based on 5 minutes of glancing, but suggest updating README to indication either file extension works.
The text was updated successfully, but these errors were encountered: