On 2015-03-11, Christian Brabandt wrote:
> Am 2015-03-10 23:40, schrieb Gary Johnson:
> >On 2015-03-10, Bram Moolenaar wrote:
> >>Using 0 CTRL-D is a bit weird, a leftover from old times. Since we
> >>don't know if CTRL-D is going to be typed or not we can't avoid
> >>triggering CursorHoldI. Perh
> https://gist.github.com/h-east/ffabb0cdd589a5f9acd2
I'm concerned that it makes ":+tabmove" behavior be different from
":.+1tabmove".
I understand that ":+" of ":+tabmove" is a range expression,
and ":+" means ":.+1"; i.e. (current-tab-number)+1.
I also understand "[X]tabmove" ("X" is direct
> * ":.bnext" == go next buffer,
> * ":+bnext" == go 2nd next buffer, same as ":.+1bnext".
> * ":.wincmd r" == go next window
> * ":+wincmd r" == go 2nd next window, same as ":.+1wincmd r"
>
> Thus it can be said that present ":[.-+]tabmove" behaviors have consistency,
> at least, as long as othe
Hi Donald!
On Di, 10 Mär 2015, Donald Allen wrote:
> On Mon, Mar 9, 2015 at 11:05 AM, Christian Brabandt
> wrote:
> > Am 2015-03-09 15:49, schrieb Donald Allen:
> >
> >> It turns out that the behavior I described in my original post
> >> (shrinking the inner pane rather than displaying more tex
Comment #8 on issue 91 by chrisbr...@googlemail.com: File->Open does not
update window content correctly - Appeared first in v7-3-638
https://code.google.com/p/vim/issues/detail?id=91
The problem with this approach is, it will make Vim a whole lot slower,
since what it really does it always
Hello all.
A while back, the mingw Makefile was split into two: Make_ming.mak and
Make_cyg_ming.mak. The first of the two files has definitions for
CFLAGS and WINRES_FLAGS; Make_cyg_ming.mak is then included and those
two make variables are reinitialized (just below "end of choices"). In
e
