Hi,
Thanks for your reply.
On Wed, Nov 14, 2018 at 07:05 PM PST, tooth pik wrote:
> i get a similar error from gtk -- my vim is built with gtk3 and i've
> had that problem so
> long i've taken all offsets out of all my scripts and just move the
> window after it's
> painted
That's what I've
On Mi, 14 Nov 2018, Bram Moolenaar wrote:
>
> Christian Brabandt wrote:
>
> > > On Mi, 29 Aug 2018, Lifepillar wrote:
> > >
> > > > There's a meme (if it may be called so) circulating on Twitter
> > > > about using Fibonacci sequences for indentation. Just for fun,
> > > > I wanted to see if
On Mi, 14 Nov 2018, Tom M wrote:
> On Wednesday, November 14, 2018 at 10:23:52 PM UTC+1, Tom M wrote:
> >
> > Hi,
> >
> > I propose the following patch (please see the attachment) to fix issues of
> > John and Tony. It ads handling of 'showbreak' and 'linebreak' in visual
> > block
i get a similar error from gtk -- my vim is built with gtk3 and i've
had that problem so
long i've taken all offsets out of all my scripts and just move the
window after it's
painted
this is one of those problems where everyone points the finger at
everyone else...
my os is opensuse
On Wed, Nov
Hi Bram and Vimmers,
I attach a patch to this email.
Please confirm and include this.
eval.txt
- L2029: Remove space after `argc(`.
gui.txt
- L881: Remove extra white spaces.
if_perl.txt
- L48-L49: Indented and insert nreline. (This is proposal)
indent.txt
- L606, L611, L945: Marked up
On Wednesday, November 14, 2018 at 10:23:52 PM UTC+1, Tom M wrote:
>
> Hi,
>
> I propose the following patch (please see the attachment) to fix issues of
> John and Tony. It ads handling of 'showbreak' and 'linebreak' in visual block
> operations.
>
> Tom
Oooops, wrong attachment. Please see
Hi Tony,
On Wed, Nov 14, 2018 at 1:18 PM Tony Mechelynck
wrote:
>
> On Wed, Nov 14, 2018 at 9:34 PM Mun wrote:
> >
> > Hi all,
> >
> > I'm not sure when this started, but it was sometime after v8.1 patch
> > 119 . I'm on v8.1 patch 524 now, and when I start vim thusly (e.g.):
> > $ vim -u NONE
On Wednesday, October 24, 2018 at 3:42:38 PM UTC+2, Tony Mechelynck wrote:
> On Wed, Oct 24, 2018 at 1:57 PM John Little wrote:
> >
> > I noticed a problem today when editing a paragraph that was wrapped to
> > several lines on screen. To reproduce, use a file with a line with normal
> > prose
On Wed, Nov 14, 2018 at 9:34 PM Mun wrote:
>
> Hi all,
>
> I'm not sure when this started, but it was sometime after v8.1 patch
> 119 . I'm on v8.1 patch 524 now, and when I start vim thusly (e.g.):
> $ vim -u NONE -U NONE --noplugin -g -geometry 80x40+100 .vimrc
>
> I get the following error on
Christian wrote:
> while reading fold.c I noticed the following error.
>
> diff --git a/src/fold.c b/src/fold.c
> index bc79accb6..3d3a13127 100644
> --- a/src/fold.c
> +++ b/src/fold.c
> @@ -3219,7 +3219,7 @@ foldlevelIndent(fline_T *flp)
> flp->lvl = -1;
> }
> else
> -
Patch 8.1.0527
Problem:Using 'shiftwidth' from wrong buffer for folding.
Solution: Use "buf" instead of "curbuf". (Christian Brabandt)
Files: src/fold.c
*** ../vim-8.1.0526/src/fold.c 2017-09-16 19:50:08.0 +0200
--- src/fold.c 2018-11-14 21:40:01.495215394 +0100
Christian Brabandt wrote:
> > On Mi, 29 Aug 2018, Lifepillar wrote:
> >
> > > There's a meme (if it may be called so) circulating on Twitter
> > > about using Fibonacci sequences for indentation. Just for fun,
> > > I wanted to see if it could be implemented using the vartabs
> > > feature. I
Hi all,
I'm not sure when this started, but it was sometime after v8.1 patch
119 . I'm on v8.1 patch 524 now, and when I start vim thusly (e.g.):
$ vim -u NONE -U NONE --noplugin -g -geometry 80x40+100 .vimrc
I get the following error on my console (although, vim seems to work just fine):
On Do, 30 Aug 2018, Christian Brabandt wrote:
>
> On Mi, 29 Aug 2018, Lifepillar wrote:
>
> > There's a meme (if it may be called so) circulating on Twitter
> > about using Fibonacci sequences for indentation. Just for fun,
> > I wanted to see if it could be implemented using the vartabs
> >
Bram,
while reading fold.c I noticed the following error.
diff --git a/src/fold.c b/src/fold.c
index bc79accb6..3d3a13127 100644
--- a/src/fold.c
+++ b/src/fold.c
@@ -3219,7 +3219,7 @@ foldlevelIndent(fline_T *flp)
flp->lvl = -1;
}
else
- flp->lvl = get_indent_buf(buf,
CC Charles since the problem is caused by the syntax/vim.vim syntax script.
Hi,
since the last vim.vim runtime update, the following example from `:h
catch` is flagged as error (the `\)` part)
,
| :catch /^Vim\%((\a\+)\)\=:E123/ " catch error E123
`
I initially was confused about
16 matches
Mail list logo