David Fishburn wrote:
> I have a script which builds Vim for me.
>
> Right now, it is only installing console Vim and not the GUI.
>
> uname -a
> Linux ubuntu-virtualbox 4.2.0-42-generic #49~14.04.1-Ubuntu SMP Wed Jun 29
> 20:22:11 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
>
> It is a VM, I am not e
P.S. On Linux, unlike on Windows, a single executable can run both as
a GUI or as a console application, so if you build a gui-enabled vim,
and install the correct symlinks (e.g. "pushd /usr/local/bin; ln -sv
vim gvim; popd) you will be able to run the same executable in the
console by calling it v
On Thu, Sep 8, 2016 at 6:09 AM, David Fishburn wrote:
> I have a script which builds Vim for me.
>
> Right now, it is only installing console Vim and not the GUI.
>
> uname -a
> Linux ubuntu-virtualbox 4.2.0-42-generic #49~14.04.1-Ubuntu SMP Wed Jun 29
> 20:22:11 UTC 2016 x86_64 x86_64 x86_64 GNU/
I have a script which builds Vim for me.
Right now, it is only installing console Vim and not the GUI.
uname -a
Linux ubuntu-virtualbox 4.2.0-42-generic #49~14.04.1-Ubuntu SMP Wed Jun 29
20:22:11 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
It is a VM, I am not even certain what my Window manager is.
On Wed, Sep 7, 2016 at 9:24 PM, Josef Fortier
wrote:
> I'm attempting to use DBI with SQLite and am seeing an error:
> ...
> I've tested with a simple perl connection with the same connection string
> (driver=SQLite:dbname=db.sq3) which works.
>
> Looking at the help, I see examples for mysql, or
I'm attempting to use DBI with SQLite and am seeing an error:
Can't call method "execute" on an undefined value at (eval 8) line 939.
Looking at line 939 (in autoload/dbext_dbi.vim
I've tried a few variations of this config
let g:dbext_default_profile_sqlite =
\ 'type=DBI'
\ . ':driv
On 2016-09-06 17:15:35 +, Nicola said:
Hi,
sometimes, switching colorschemes seems to "corrupt" some colors and I am
trying to figure out if there's a way around it.
For example, if I start Vim with syntax on and the default color scheme to
edit my vimrc, then `:hi vimCommand` outputs:
Hi,
In my attempt to execute (pure) VimL functions in the background (*) (which is
quite difficult without thread-safety), I was thinking of executing my function
on a second/remote vim server.
I know I could play with --remote-send and --remote-expr, but could I use job
or channels instead?
