>
> Isn't your MinGW a bit old? Which version from which site do you use?
> Newer MinGW should have _stat64.
> I recommend MinGW-w64.
That's it. I recently installed a new MinGW version, but failed to update the
PATH environment variable, so that it still used the old MinGW environment.
--
Hi Bram & list,
Looking at test_history.vim, Test_History calls the History_Tests
function for a list of various strings.
for h in ['cmd', ':', '', 'search', '/', '?', 'expr', '=', 'input', '@',
'debug', '>']
call History_Tests(h)
endfor
Most of these are the valid history type names
If you mean that there is more space below capital-letter glyphs than
above them, this is normal: indeed, descenders (as with g, j, p, q) go
below the capitals' baseline, while ascenders (as in b, d, f, h, k, l,
t) hardly go above the capitals' top line.
Instead of comparing the blank space above
Ken Takata wrote:
> Hi,
>
> 2016/9/23 Fri 13:00:40 UTC+9 skywind3000 wrote:
> > Ken Takata wrote:
> > > Hi,
> > >
> > > 2016/9/23 Fri 4:46:48 UTC+9 skywind3000 wrote:
> > > > Yesterday, I started vim in GitBash (msys+mintty) by chance on windows.
> > > > and found that vim worked very well in
Am Donnerstag, 22. September 2016 08:40:47 UTC+2 schrieb LCD 47:
> On 21 September 2016, Markus Knecht wrote:
> > Hello,
> >
> > For a project I have to import some markings into vim and for that I'm
> > writing a plugin. These markings are in the form of:
> > line
Magnus Woldrich:
> >Thanks, very disappointted with cmd.exe
>
> Here you go: https://msys2.github.io/
After downloading msys2 and installing gcc, ncurses-devel ... with pacman,
I started to build latest vim inside msys2, and found these:
checking for tgetent in -ltinfo... (cached) no
checking
Addendum:
Looking into the code, I found that a possible location for this to happen
might be list_find_nr() in list.c.
I have to add that, revising my use of setpos(), I called the function like
this: setpos("'<", [0, 532, 83]), i.e. I left out the "off" list member.
As this did not result in
Hi,
Axel Bender schrieb am 22.09.2016 um 16:03:
> The following image shows an erratical behavior of setpos() that I
> cannot explain. When calling setpos("'<", ...), setpos("'>", ...) for
> that matter, the behavior is OK for the first calls to setpos().
> However, from a certain number of
Hi Markus!
On Fr, 23 Sep 2016, Markus Knecht wrote:
> Thanks, matchaddops seems to be exactly the functionality i need,
> sadly I get a failure that the function matchaddpos is unknown,
> probably I'm missing something obvious
You need to update your vim, or you can use a translate the
Addendum 2:
The problem also shows up when the setpos() is fed with the correct List (i.e.
four elements).
@Jürgen
It seems that this is the trigger, you're right. However, as I take it from the
docs, the mode - when entering operator-pending mode - should be charwise
Visual mode.
That said,
Hi,
2016/9/23 Fri 16:12:34 UTC+9 skywind3000 wrote:
> Ken Takata wrote:
> > Hi,
> >
> > 2016/9/23 Fri 13:00:40 UTC+9 skywind3000 wrote:
> > > Ken Takata wrote:
> > > > Hi,
> > > >
> > > > 2016/9/23 Fri 4:46:48 UTC+9 skywind3000 wrote:
> > > > > Yesterday, I started vim in GitBash (msys+mintty)
Am Donnerstag, 22. September 2016 08:40:47 UTC+2 schrieb LCD 47:
> On 21 September 2016, Markus Knecht wrote:
> > Hello,
> >
> > For a project I have to import some markings into vim and for that I'm
> > writing a plugin. These markings are in the form of:
> > line start,
> > coloumn start,
On Fri, Sep 23, 2016 at 12:41:56AM -0700, skywind3000 wrote:
> Magnus Woldrich:
> > >Thanks, very disappointted with cmd.exe
> >
> > Here you go: https://msys2.github.io/
>
> After downloading msys2 and installing gcc, ncurses-devel ... with pacman,
> I started to build latest vim inside msys2,
On 23 September 2016, Christian Brabandt wrote:
> Hi Markus!
>
> On Fr, 23 Sep 2016, Markus Knecht wrote:
>
> > Thanks, matchaddops seems to be exactly the functionality i need,
> > sadly I get a failure that the function matchaddpos is unknown,
> > probably I'm missing
14 matches
Mail list logo