[vim/vim] Vim cannot write *.vba files (#2694)
Bastien Orivel
Vim says: E382: Cannot write, 'buftype' option is set when you try to write a .vba file.
Steps to reproduce:
- vim toto.vba
- :wq
The problems seems to be coming from this line: https://github.com/vim/vim/blob/946acdac5b4e334f816e78f7876bde9d97b3d96a/runtime/plugin/vimballPlugin.vim#L31 as commenting it out "fixes" the bug.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
Christian Brabandt
Oh, I am surprised this has been finally noted. .vba files where initially used as vimball files to distribute vim plugins and it has been later switched to .vmb format.
cc @cecamp
perhaps its time to drop support for the old .vba vimball format and only use .vmb, since vba could be legitimite files after all.
To workaround it, if you need to write a legimitate .vba file, simply set the buftype option to empty: :set bt=
Niklas Saari
This issue seems to still happen. I was wondering, why I could not save files in .vba type.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Christian Brabandt
if you do not intend to use vimballs, you can also disable it by setting
let g:loaded_vimballPlugin=1
in your .vimrc. Then it shouldn't happen.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Niklas Saari
if you do not intend to use vimballs, you can also disable it by setting
let g:loaded_vimballPlugin=1in your .vimrc. Then it shouldn't happen.
Seems to solve issue in my case. Thank you.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Brandon Wallace
came here because I just encountered this. Luckily for me it was a one-time need and only cost me some minutes of googling to figure out how to workaround it 🙄 .
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
dkearns
I was just updating the Visual Basic file type detection and was going to add support for *.vba files.
Unfortunately, there's some Vimball functionality triggered with BufEnter autocommands which I don't think can reasonably be disabled as it stands.
It seems to me that the easiest solution might be to make a dedicated filetype for Vimballs. Then the autocommands can use FileType instead.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Christian Brabandt
Yes, probably should get vimball as an own filetype. And possibly also get rid of .vba as extension for vimball. It's been long gone and nowadays vimballs use the .vmb extension anyhow.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Gary Johnson
> Yes, probably should get vimball as an own filetype. And possibly also get rid
> of .vba as extension for vimball. It's been long gone and nowadays vimballs use
> the .vmb extension anyhow.
extension.
The first line of a .vba file could be inspected to determine
whether it was a vimball.
Regards,
Gary
vim-dev ML
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Christian Brabandt
On Mi, 23 Aug 2023, Gary Johnson wrote:
> All of the vimballs I have from Chip Campbell use the .vba
> extension.
>
> The first line of a .vba file could be inspected to determine
> whether it was a vimball.
http://www.drchip.org/astronaut/vim/index.html
I also checked the documentation for the vimball:
,----
| 33 : Apr 02, 2011 * Gave priority to *.vmb over *.vba
| * Changed silent! to sil! (shorter)
| * Safed |'swf'| setting (during vimball extraction,
| its now turned off)
`----
Oh well ...
Best,
Christian
--
I am the wandering glitch -- catch me if you can.
vim-dev ML
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
dkearns
On 2023-08-19, Christian Brabandt wrote: Yes, probably should get vimball as an own filetype. And possibly also get rid of .vba as extension for vimball. It's been long gone and nowadays vimballs use the .vmb extension anyhow.
All of the vimballs I have from Chip Campbell use the .vba extension. The first line of a .vba file could be inspected to determine whether it was a vimball.
Yes, that's what I've done for now, in the simplest way possible.
Creating a separate filetype has other advantages but, of course, only works when filetype support is enabled. I might still do that in a separate PR.
Thanks.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you commented.
Christian Brabandt
Closed #2694 as completed via f97f6bb.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you commented.