Ok - Forgot to look at the syntax files I committed to vim.org. Got the
freebasic.vim update. Thanks to Michael Torrie!
Mark
--
--
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
A L time ago someone wrote to me to say that they wanted to
update the freebasic.vim file and I told them to put their name on top
of mine, make the update, and handle anyone's questions about the
changes. Well, I decided to put all of my stuff on GitHub so they can
be downloaded a
On 2016-01-20, James McCoy wrote:
> On Tue, Jan 19, 2016 at 10:52:07AM -0800, Gary Johnson wrote:
> > On 2016-01-19, Bram Moolenaar wrote:
> > > James McCoy wrote:
> >
> > > > Why does the behavior differ? Shouldn't it be consistent?
> > > >
> > > > Both Windows and UNIX asked you to have a file
Hi Christian,
On Wed, Jan 20, 2016 at 1:00 PM, Christian Brabandt wrote:
> Hi Yegappan!
>
> On Mi, 20 Jan 2016, Yegappan Lakshmanan wrote:
>
>> Hi all,
>>
>> A Vim window can use either the global argument list or a local argument
>> list. The argv() and argc() functions currently support only t
2016-01-21 4:26 GMT+03:00 Nikolay Aleksandrovich Pavlov :
>
>
> 2016-01-19 21:52 GMT+03:00 Gary Johnson :
>
>> On 2016-01-19, Bram Moolenaar wrote:
>> > James McCoy wrote:
>>
>> > > Why does the behavior differ? Shouldn't it be consistent?
>> > >
>> > > Both Windows and UNIX asked you to have a f
2016-01-19 21:52 GMT+03:00 Gary Johnson :
> On 2016-01-19, Bram Moolenaar wrote:
> > James McCoy wrote:
>
> > > Why does the behavior differ? Shouldn't it be consistent?
> > >
> > > Both Windows and UNIX asked you to have a file with a space in the
> name.
> > > In fact, :argedit's help calls out
On Tue, Jan 19, 2016 at 10:52:07AM -0800, Gary Johnson wrote:
> On 2016-01-19, Bram Moolenaar wrote:
> > James McCoy wrote:
>
> > > Why does the behavior differ? Shouldn't it be consistent?
> > >
> > > Both Windows and UNIX asked you to have a file with a space in the name.
> > > In fact, :arged
Ken Takata wrote:
> 2016/1/20 Wed 7:47:18 UTC+9 Ken Takata wrote:
> > Hi Bram,
> >
> > 2016/1/20 Wed 3:33:18 UTC+9 Bram Moolenaar wrote:
> > > Ken Takata wrote:
> > >
> > > > (The original thread was in vim_use:
> > > > https://groups.google.com/d/topic/vim_use/RLM8Vqa_aME/discussion )
> > > >
Kazunobu Kuriyama wrote:
> With this patch, I got the following warnings:
>
> ```
> clang -c .. -o objects/syntax.o syntax.c
> syntax.c:991:22: warning: declaration shadows a variable in the global
> scope [-Wshadow]
> save_chartab(char_u *chartab)
> ^
> ./globals.h:1015
Patch 7.4.1147
Problem:Conflict for "chartab". (Kazunobu Kuriyama)
Solution: Rename the global one to something less obvious. Move it into
src/chartab.c.
Files: src/macros.h, src/globals.h, src/charset.c, src/main.c,
src/option.c, src/screen.c, src/vim.h
*** .
Hirohito Higashi wrote:
> Hi Bram and Vimmers!
>
> 2016-1-20(Wed) 3:00:59 UTC+9 Bram Moolenaar:
> > Hirohito Higashi wrote:
> >
> > > > Sorry for the huge patch!
> > > >
> > > > Let me know if there is someone with an old compiler that can't handle
> > > > this ANSI style code. If not then I'
Ken Takata wrote:
> Hi Bram and mattn,
>
> 2016/1/3 Sun 4:27:00 UTC+9 Bram Moolenaar wrote:
> > Patch 7.4.1031
> > Problem:Can't build with Python interface using MingW.
> > Solution: Update the Makefile. (Yasuhiro Matsumoto)
> > Files: src/INSTALLpc.txt, src/Make_cyg_ming.mak
>
> Th
Patch 7.4.1146
Problem:Can't build with Python 3 interface using MingW.
Solution: Update the Makefile. (Yasuhiro Matsumoto, Ken Takata)
Files: src/Make_cyg_ming.mak
*** ../vim-7.4.1145/src/Make_cyg_ming.mak 2016-01-16 16:20:23.708823286
+0100
--- src/Make_cyg_ming.mak 201
Patch 7.4.1145
Problem:Default features are conservative.
Solution: Make the default feature set for most of todays systems "huge".
Files: src/feature.h, src/configure.in, src/auto/configure
*** ../vim-7.4.1144/src/feature.h 2015-12-31 19:06:56.028082124 +0100
--- src/feature.h
Hi Yegappan!
On Mi, 20 Jan 2016, Yegappan Lakshmanan wrote:
> Hi all,
>
> A Vim window can use either the global argument list or a local argument
> list. The argv() and argc() functions currently support only the
> argument list for the current window. You cannot use these functions to
> get t
Hi all,
A Vim window can use either the global argument list or a local argument
list. The argv() and argc() functions currently support only the
argument list for the current window. You cannot use these functions to
get the argument list for any window in any tab page.
I am proposing the follo
Christian Robinson wrote:
> > I only meant to suggest it as a temporary workaround; I'm aware that
> > it's not a good permanent solution.
> >
> > For what it's worth, I usually build the Big version.
>
> Actually, I should have just wrapped it in an ifdef and posted a
> patch, so here it is.
Patch 7.4.1144 (after 7.4.1143)
Problem:Can't build on several systems.
Solution: Include float.h. (Christian Robinson, closes #570 #571)
Files: src/ex_cmds.c
*** ../vim-7.4.1143/src/ex_cmds.c 2016-01-19 23:35:43.567530384 +0100
--- src/ex_cmds.c 2016-01-20 20:05:28.881104
On Wed, 20 Jan 2016, Christian J. Robinson wrote:
I only meant to suggest it as a temporary workaround; I'm aware that
it's not a good permanent solution.
For what it's worth, I usually build the Big version.
Actually, I should have just wrapped it in an ifdef and posted a
patch, so here i
On Wed, 20 Jan 2016, Tony Mechelynck wrote:
On Wed, Jan 20, 2016 at 6:08 PM, Christian J. Robinson
wrote:
I was able to get it to compile by adding this to the top of
ex_cmds.c:
#include
Including that unconditionally cannot be right, if only because some
Vim versions are built without
On Wed, Jan 20, 2016 at 6:08 PM, Christian J. Robinson
wrote:
> On Wed, 20 Jan 2016, Cesar Romani wrote:
>
>> I'm getting:
>>
>>
>> [...]
>> ex_cmds.c:560:48: error: 'DBL_MAX' undeclared (first use in this function)
>> nrs[lnum - eap->line1].st_u.value_flt = -DBL_MAX;
>>
On Wed, 20 Jan 2016, Cesar Romani wrote:
I'm getting:
[...]
ex_cmds.c:560:48: error: 'DBL_MAX' undeclared (first use in this function)
nrs[lnum - eap->line1].st_u.value_flt = -DBL_MAX;
^
ex_cmds.c:560:48: note: each undec
> mattn, did you just forget to include?
yep. thank you.
> Could you check the attached patch?
LGTM.
- mattn
--
--
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/mailli
I'm getting:
[...]
ex_cmds.c:560:48: error: 'DBL_MAX' undeclared (first use in this function)
nrs[lnum - eap->line1].st_u.value_flt = -DBL_MAX;
^
ex_cmds.c:560:48: note: each undeclared identifier is reported only once
f
Hi,
2016/1/20 Wed 7:47:18 UTC+9 Ken Takata wrote:
> Hi Bram,
>
> 2016/1/20 Wed 3:33:18 UTC+9 Bram Moolenaar wrote:
> > Ken Takata wrote:
> >
> > > (The original thread was in vim_use:
> > > https://groups.google.com/d/topic/vim_use/RLM8Vqa_aME/discussion )
> > >
> > > I have updated the patches
Hi Bram and mattn,
2016/1/3 Sun 4:27:00 UTC+9 Bram Moolenaar wrote:
> Patch 7.4.1031
> Problem:Can't build with Python interface using MingW.
> Solution: Update the Makefile. (Yasuhiro Matsumoto)
> Files: src/INSTALLpc.txt, src/Make_cyg_ming.mak
This patch is missing fixes for python3.
26 matches
Mail list logo
