macvim icon indicating copy to clipboard operation
macvim copied to clipboard

Big Sur / Can't open windows from finder properly, but works on terminal

Open VonbatenBach opened this issue 5 years ago • 3 comments

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: Screenshot 2020-11-15 at 15 57 11 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:

  1. I open a file from Finder - error pops out and actually nothing works (just like it was disconnected from anything that is installed and configured by .vimrc)
  2. When I open a file from terminal using mvim everything works as it should.

Expected behavior No such errors, consistency between opening from terminal and finder.

Environment (please complete the following information):

  • Vim version: VIM - Vi IMproved 8.2
  • MacVim version: MacVim 8.2.1719 (up to date)
  • OS: macOS Big Sur
  • Terminal: GUI, Terminal.app

Additional context It emerged after system update from Catalina to BigSur. I have MacVim installed from .dmg file.

VonbatenBach avatar Nov 15 '20 15:11 VonbatenBach

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.

ychin avatar Nov 30 '20 09:11 ychin

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 ?

ychin avatar Dec 12 '20 07:12 ychin

It looks the similar error: https://github.com/lervag/vimtex/issues/1764 Probably can fix it by updating vimtex.

ichizok avatar May 14 '21 22:05 ichizok