not sure if that's vorax issue, but maybe you can point me what can I check.
I have extracted vorax-2.8.zip under: .vim/bundle/vorax (using pathogen with call pathogen#runtime_append_all_bundles() )
when I now edit new file: $ vi a.sql Error detected while processing /home/chris/Dropbox-cris/Dropbox/dot_files/.vim/bundle/vorax/plugin/vorax.v im: line 30: NameError: uninitialized constant VERSION
then "a.sql" [New File] Error detected while processing /home/chris/Dropbox-cris/Dropbox/dot_files/.vim/bundle/vorax/autoload/vorax .vim line 24: LoadError: Failed to load the ANTLR3 runtime library (version 1.7.4):
Would appreciate any pointers how to get rid off these messages. Vorax works fine any way.
Vorax 2.X is kind of desupported in favor of Vorax 3. I don't use it myself. The problem you describe seems related to some library loading issue, but it's hard to say exactly why. Do you have ANTLR3 ruby gem installed?
I am trying to setup vorax3 now. I have installed antlr3 into ruby as
gem and it starts fine. But none of my connections exist.
Is it possible to migrate connections from previous versions?
The file exists ~/_vorax_connections
when I run: VoraxOutputWindowToggle
I get some error messages:
Error detected while processing function
vorax#ToggleOutputWindow..148..144..153..vorax#CreateCommonKeyMappings:
line 5:
E225: global mapping already exists for ,d
line 15:
E225: global mapping already exists for ,d
when i press enter I get a new empty horizontal window (instead of
expected vertical with filled connections)
What can I check?
thanks,
Chris
On Fri, Oct 12, 2012 at 9:57 AM, talek <alexandru.t...@gmail.com> wrote:
>> Hi Chris,
> Vorax 2.X is kind of desupported in favor of Vorax 3. I don't use it myself.
> The problem you describe seems related to some library loading issue, but
> it's hard to say exactly why. Do you have ANTLR3 ruby gem installed?
> Nope, the connections manager, and Vorax 3 in general, is not backward > compatible! Lot of changes behind... Please have a look on the following > links:
but while trying to connect with:
:VoraxConnect username/pwd@db
Vim gets killed:
Vim: Caught deadly signal ABRT
VIm: Finished
Aborted
Now I need to do some work, so went back to vorax 2.8, but will give
definitely a try, if you have some suggestions what to check else,
would appreciate it.
thanks,
Chris
On Fri, Oct 12, 2012 at 10:21 AM, talek <alexandru.t...@gmail.com> wrote:
>> Nope, the connections manager, and Vorax 3 in general, is not backward
>> compatible! Lot of changes behind... Please have a look on the following
>> links:
On Fri, Oct 12, 2012 at 10:53 AM, chris <ch...@goxp.de> wrote:
> I followed the instructions,
> but while trying to connect with:
> :VoraxConnect username/pwd@db
> Vim gets killed:
> Vim: Caught deadly signal ABRT
> VIm: Finished
> Aborted
> Now I need to do some work, so went back to vorax 2.8, but will give
> definitely a try, if you have some suggestions what to check else,
> would appreciate it.
> thanks,
> Chris
> On Fri, Oct 12, 2012 at 10:21 AM, talek <alexandru.t...@gmail.com> wrote:
>>> Nope, the connections manager, and Vorax 3 in general, is not backward
>>> compatible! Lot of changes behind... Please have a look on the following
>>> links:
