Igor

One way to solve this is to figure out what python version is the vim runtime using ```lua :py3 print(sys.path) ``` This output: ``` ['/usr/local/opt/[email protected]/Frameworks/Python.framework/Versions/3.9/lib/python39.zip', '/usr/local/opt/[email protected]/Frameworks/Python.framewor k/Versions/3.9/lib/python3.9', '/usr/local/opt/[email protected]/Frameworks/Python.framework/Versions/3.9/lib/python3.9/lib-dynload', '/usr/local/op t/[email protected]/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages',...

Had the same issue switching to the **latest** `vue-syntax-highlighting` no longer breaks the syntax highlighting.

Hey @mrkn When I run your command in IRB console that uses ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-linux] I get the following segmentation fault ``` root@97b43330976b:/app# irb irb(main):001:0> require 'pycall'...

Adding it to both the engine's Gemfile and .gemspec didn't solve it. Still it gives the NameError: uninitialized constant. Using (ruby 2.0.0p576 & Rails 4.0.5)

``` bash 469 open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3 469 open("/lib64/libc.so.6", O_RDONLY|O_CLOEXEC) = 3 469 open("/usr/lib64/locale/locale-archive", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) 469 open("/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 3 469 open("/usr/lib64/locale/en_US/LC_IDENTIFICATION",...

I did strace -o strace.log -f -s 1000 -e open /usr/bin/linuxband Here's the strace.log http://pastebin.com/NUrejtJP

Here's with -v verbose=all arguments http://pastebin.com/KRbeLGn3

I have installed pygtk-2.24.0-x86_64-1 pygtksourceview-2.10.1-x86_64-1_SBo python-2.7.4-x86_64-1 packages bash-4.2$ python Gives me: Python 2.7.4 (default, Apr 7 2013, 11:58:11) Maybe an environment variable setting. Weird because I could run the version...

the /usr/bin/env doesn\t show me anthing regarding python, though it seems to be installed on the system. I'm using Slackware 14.1 Current 64

I've edited the /usr/bin/linuxband #!/usr/bin/env python -> #!/usr/bin/python Also had to fix the ^M line ending formatting issue with the dos2unix utili on that script. And now the application can...