I'm trying to get vim to compile on my Mac running Mojave and it's
failing. I've grabbed the latest sources:
$ git reset --hard origin/master
HEAD is now at 4d5d0dfe9 patch 8.2.0579: Coverity warns for unused value
My configure command is:
./configure --disable-gui --enable-largefile --enable-
On Wed, Apr 15, 2020 at 08:22:27AM +0200, Christian Brabandt wrote:
> I am sympathetic to these arguments. We shouldn't add new options
> especially if they only affect a very tiny behaviour of Vim. Changing
> the core of vim certainly adds to the complexity of the different code
> paths so this
Tavis Ormandy wrote:
> On Tue, Apr 14, 2020 at 01:44:50PM -0700, Brian L. Matthews wrote:
> > > You don't need CTRL-W at all if you don't mind hitting more keys, but
> > > since we do have it and configurable behaviour, why not cover all the
> > > variations people could want?
> >
> > While thi
On Wed, Apr 15, 2020 at 08:06:14PM +0200, Bram Moolenaar wrote:
>
> To make CTRL-W delete all text until the start of the file:
> :set bs=7
>
> To make CTRL_W delete all text you ever wrote:
> :set bs=42
>
> Intermediate values TBD.
>
ITYM all the text you ever wrote *up to* the in
Brian Matthews wrote:
> I'm trying to get vim to compile on my Mac running Mojave and it's
> failing. I've grabbed the latest sources:
>
> $ git reset --hard origin/master
> HEAD is now at 4d5d0dfe9 patch 8.2.0579: Coverity warns for unused value
>
> My configure command is:
>
> ./configure
> On Wed, Apr 15, 2020 at 08:06:14PM +0200, Bram Moolenaar wrote:
> >
> > To make CTRL-W delete all text until the start of the file:
> > :set bs=7
> >
> > To make CTRL_W delete all text you ever wrote:
> > :set bs=42
> >
> > Intermediate values TBD.
> >
>
> ITYM all the text you eve
experts:
I just ran into a weird issue today...
when opening a log file in one of my server, It displays everything in one
line, joined by ^J (ascii code 10).
g ctrl-g gives:
Col 32004 of 468-5005640; Line 1 of 1; Word 20 of 144087; Byte 32004 of
469
when I copy the same file into my loc
On Mi, 15 Apr 2020, Tavis Ormandy wrote:
> On Wed, Apr 15, 2020 at 08:22:27AM +0200, Christian Brabandt wrote:
> > I am sympathetic to these arguments. We shouldn't add new options
> > especially if they only affect a very tiny behaviour of Vim. Changing
> > the core of vim certainly adds to t
