On Di, 21 Aug 2018, Oleksii Vilchanskyi wrote:
> However, if I try wrapping it in a function, E127 occurs:
> > set nocompatible
> > filetype plugin indent on
> > syntax on
> >
> > augroup vimrc
> > autocmd!
> > autocmd BufWritePost testvimrc call s:ReloadRC("testvimrc")
> > augroup END
On Tue, Aug 21, 2018 at 12:22 PM, Oleksii Vilchanskyi
wrote:
> Hello,
>
> * What I want:
>
> Be able to do :w after editing $MYVIRC and have vim source the new
> version of config. Basically, just execute `source %` automatically.
>
> * What I have tried (all examples are launched with `vim -u tes
Hello,
* What I want:
Be able to do :w after editing $MYVIRC and have vim source the new
version of config. Basically, just execute `source %` automatically.
* What I have tried (all examples are launched with `vim -u testvimrc`):
So, this works without any error, as supposed:
> set nocompatibl
On Tuesday 21 August 2018 20:31,
rob put forth the proposition:
> I'm going to have to grok this.
>
> It will take a bit of time.
>
> Thanks
>
> --rob
> On 08/21/2018 07:48 PM, Tony Mechelynck wrote:
> > On Wed, Aug 22, 2018 at 12:26 AM, rob wrote:
> > > Hi. I'm interested in getting code foldin
I'm going to have to grok this.
It will take a bit of time.
Thanks
--rob
On 08/21/2018 07:48 PM, Tony Mechelynck wrote:
On Wed, Aug 22, 2018 at 12:26 AM, rob wrote:
Hi. I'm interested in getting code folding to work. I'm getting a message
on Ubuntu 16.04 amd64 that lua has to be compiled
On Wed, Aug 22, 2018 at 12:26 AM, rob wrote:
> Hi. I'm interested in getting code folding to work. I'm getting a message
> on Ubuntu 16.04 amd64 that lua has to be compiled in for a macro to work.
>
> How do I get lua to be compiled into the make process?
>
> --rob
You can get folding without l
Hi. I'm interested in getting code folding to work. I'm getting a
message on Ubuntu 16.04 amd64 that lua has to be compiled in for a macro
to work.
How do I get lua to be compiled into the make process?
--rob
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type
On Tue, Aug 21, 2018 at 4:36 PM, Tim Chase wrote:
[...]
> Indeed, I often work on FreeBSD & OpenBSD boxes where nvi is the
> default vi instead of vim. I find myself missing a couple things
> like text objects, folding, multiple windows, and expression
> evaluation (whether as a register or as a
On 2018-08-21 03:58, Tony Mechelynck wrote:
> Just to see what it meant, I tried a Small Vim (instead of my usual
> Big) with Motif GUI (instead of my usual GTK2), and it taught me
> I've been living in luxury.
Indeed, I often work on FreeBSD & OpenBSD boxes where nvi is the
default vi instead of
