Open VonbatenBach opened 3 years ago
Hmm, I'm not sure why this manifests itself after upgrading to Big Sur. It looks maybe like a locale issue (what locale are you running on your machine?), and I'm guessing it's fixed in v8.2.1738 which will be covered in the next release (will be out soon).
Let's see if the next release will fix this and if it doesn't we can look closer into this.
That said, seems like it's throwing an error within the vimtex plugin? You may want to file an issue with them to see if there is a bug or error that leads to an array out of bounds error.
The new release is now out (https://github.com/macvim-dev/macvim/releases). Can you try it out and see if this is still an issue @VonbatenBach ?
It looks the similar error: https://github.com/lervag/vimtex/issues/1764 Probably can fix it by updating vimtex.
Describe the bug When I open a .tex file on MacVim from the Finder's level (just by clicking on a file), I get an error:
On the other hand, when I open the file form terminal, ie.
mvim <file_name>
it opens properly and every plugin works, as on MacOS Catalina. This strange behaviour emerged when I updated MacOS.To Reproduce As written above:
mvim
everything works as it should.Expected behavior No such errors, consistency between opening from terminal and finder.
Environment (please complete the following information):
Additional context It emerged after system update from Catalina to BigSur. I have MacVim installed from .dmg file.