um
I rebooted (cold) and it went away
never mind
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscri
is anyone else getting this?
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Grou
2018-04-19 15:45 GMT+03:00 Bram Moolenaar :
>
> Christ van Willegen wrote:
>
>> On Thu, Apr 19, 2018 at 12:12 PM, Bram Moolenaar wrote:
>> >
>> > Nikolay Pavlov wrote:
>> >
>> >> 2018-04-19 0:01 GMT+03:00 Bram Moolenaar :
>> >> >
>> >> > Patch 8.0.1735 (after 8.0.1723 and 8.0.1730)
>> >> > Problem
On 19-Apr.-2018 06:58, Bram Moolenaar wrote:
Yeah, at least the configure check works. But clearly this change will
mean you can no longer compile Vim. So let's not allow for flexible
array members. It's a nice feature, pity we can't use it.
I'll make a patch to revert this, please check tha
Patch 8.0.1737
Problem:fchown() used when it is not supported.
Solution: Add #ifdef.
Files: src/fileio.c
*** ../vim-8.0.1736/src/fileio.c2018-04-08 13:07:18.742034802 +0200
--- src/fileio.c2018-04-19 21:10:26.438281314 +0200
***
*** 712,719
Christian wrote:
> > Bram,
> > can you please include the following change in the next runtime update?
>
> Here is another small doc patch. This might explain the following behaviour:
>
> ./vim --clean '-c :e foobar' -c ':au WinEnter echom "Entering Window
> for buffer ". expand("")'
>
> The
Guillaume -
> We have updated the syntax file for the neomuttrc filetype. I've
> attached the whole runtime/syntax/neomuttrc.vim file as I had to send
> the whole files the first time (and this is the first update). If a
> patch is preferred for update, say so and I will send one.
I'll include i
Patch 8.0.1736
Problem:Check for C99 features is incomplete.
Solution: Use AC_PROG_CC_C99 and when C99 isn't fully supported check the
features we need. (James McCoy, closes #2820)
Files: src/configure.ac, src/auto/configure
*** ../vim-8.0.1735/src/configure.ac2018-04-
> I don't think so. Have you tried the method mentioned at
> :h :echo-redraw?
I read it just now - thank you for pointing it out. So, the proposed solution
should be like this?
autocmd TabEnter * redraw | echo "Hi"
The message still doesn't seem to show.
--
--
You received this message f
Christ van Willegen wrote:
> On Thu, Apr 19, 2018 at 12:12 PM, Bram Moolenaar wrote:
> >
> > Nikolay Pavlov wrote:
> >
> >> 2018-04-19 0:01 GMT+03:00 Bram Moolenaar :
> >> >
> >> > Patch 8.0.1735 (after 8.0.1723 and 8.0.1730)
> >> > Problem:Flexible array member feature not supported by HP-U
On Thu, Apr 19, 2018 at 02:11:45PM +0200, Dominique Pellé wrote:
> I'm with Bram here. We'll end up having b_str[] on Linux & macOS
> and b_str[1] on more exotic platforms (e.g. HPUX compiler). There might
> subtle differences in behavior somewhere as a result, and since we
> mostly test on platfo
Christ van Willegen wrote:
> Hi,
>
> On Thu, Apr 19, 2018 at 12:12 PM, Bram Moolenaar wrote:
>>
>> Nikolay Pavlov wrote:
>>
>>> 2018-04-19 0:01 GMT+03:00 Bram Moolenaar :
>>> >
>>> > Patch 8.0.1735 (after 8.0.1723 and 8.0.1730)
>>> > Problem:Flexible array member feature not supported by HP-
Hi,
On Thu, Apr 19, 2018 at 12:12 PM, Bram Moolenaar wrote:
>
> Nikolay Pavlov wrote:
>
>> 2018-04-19 0:01 GMT+03:00 Bram Moolenaar :
>> >
>> > Patch 8.0.1735 (after 8.0.1723 and 8.0.1730)
>> > Problem:Flexible array member feature not supported by HP-UX. (John
>> > Marriott)
>> >
Nikolay Pavlov wrote:
> 2018-04-19 0:01 GMT+03:00 Bram Moolenaar :
> >
> > Patch 8.0.1735 (after 8.0.1723 and 8.0.1730)
> > Problem:Flexible array member feature not supported by HP-UX. (John
> > Marriott)
> > Solution: Do not use the flexible array member feature of C99.
> > Fi
On Mi, 18 Apr 2018, Christian Brabandt wrote:
> Bram,
> can you please include the following change in the next runtime update?
Here is another small doc patch. This might explain the following behaviour:
./vim --clean '-c :e foobar' -c ':au WinEnter echom "Entering Window
for buffer ". expan
On Do, 19 Apr 2018, dosimple wrote:
> Should it be considered as a bug?
I don't think so. Have you tried the method mentioned at
:h :echo-redraw?
Best,
Christian
--
Solang einer noch kein System hat und die Wahrheiten ungeordnet in
seinem Kopfe liegenlässet, so lange liebt [er] schwerlich die
Should it be considered as a bug?
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google
17 matches
Mail list logo
