On May 16, 2014 1:58 PM, "Alex Efros" wrote:
>
> Hi!
>
> On Fri, May 16, 2014 at 12:53:17PM +0400, Nikolay Pavlov wrote:
> > On May 16, 2014 12:29 PM, "Alex Efros" wrote:
> > > > > fun s:Foo()
> > > > > endfun
> > > > > let g:Foo = function('s:Foo')
> > This change has nothing to do w
Hi!
On Fri, May 16, 2014 at 12:53:17PM +0400, Nikolay Pavlov wrote:
> On May 16, 2014 12:29 PM, "Alex Efros" wrote:
> > > > fun s:Foo()
> > > > endfun
> > > > let g:Foo = function('s:Foo')
> This change has nothing to do with the change that made function('s:...')
> work outside of th
On May 16, 2014 12:29 PM, "Alex Efros" wrote:
>
> Hi!
>
> On Fri, Apr 25, 2014 at 03:27:40PM +0200, Bram Moolenaar wrote:
> > > My guess right solution should be
> > > fun s:Foo()
> > > endfun
> > > let g:Foo = function('s:Foo')
> > > but I'm not 100% sure.
> >
> > That should be the r
Hi!
On Fri, Apr 25, 2014 at 03:27:40PM +0200, Bram Moolenaar wrote:
> > My guess right solution should be
> > fun s:Foo()
> > endfun
> > let g:Foo = function('s:Foo')
> > but I'm not 100% sure.
>
> That should be the right way. The more things are script-local the
> better. But chec
Nikolay Pavlov wrote:
> On Apr 25, 2014 6:22 PM, "Bram Moolenaar" wrote:
> >
> > Alex Efros wrote:
> >
> > > On Fri, Apr 25, 2014 at 03:27:40PM +0200, Bram Moolenaar wrote:
> > > > > My guess right solution should be
> > > > > fun s:Foo()
> > > > > endfun
> > > > > let g:Foo = functi
On Apr 25, 2014 7:40 PM, "Alex Efros" wrote:
>
> Hi!
>
> On Fri, Apr 25, 2014 at 07:34:16PM +0400, Nikolay Pavlov wrote:
> > because the fact that you received a funcref never means you can call it
>
> Why is that?
Funcref is a mere string. There is no guarantee that referenced function is
define
Hi!
On Fri, Apr 25, 2014 at 07:34:16PM +0400, Nikolay Pavlov wrote:
> because the fact that you received a funcref never means you can call it
Why is that?
--
WBR, Alex.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply belo
On Apr 25, 2014 2:52 AM, "Alex Efros" wrote:
>
> Hi!
>
> On Thu, Apr 24, 2014 at 12:43:01PM +0200, Bram Moolenaar wrote:
> > > Me, too. The following used to work:
> > >
> > > fun! Foo()
> > > endfun
> > > let g:Foo = function('Foo')
> > >
> > > After 7.4.264, I get:
> > > " E705: Vari
On Apr 25, 2014 6:22 PM, "Bram Moolenaar" wrote:
>
>
> Alex Efros wrote:
>
> > On Fri, Apr 25, 2014 at 03:27:40PM +0200, Bram Moolenaar wrote:
> > > > My guess right solution should be
> > > > fun s:Foo()
> > > > endfun
> > > > let g:Foo = function('s:Foo')
> > > > but I'm not 100% sur
Alex Efros wrote:
> On Fri, Apr 25, 2014 at 03:27:40PM +0200, Bram Moolenaar wrote:
> > > My guess right solution should be
> > > fun s:Foo()
> > > endfun
> > > let g:Foo = function('s:Foo')
> > > but I'm not 100% sure.
> >
> > That should be the right way. The more things are scrip
Hi!
On Fri, Apr 25, 2014 at 03:27:40PM +0200, Bram Moolenaar wrote:
> > My guess right solution should be
> > fun s:Foo()
> > endfun
> > let g:Foo = function('s:Foo')
> > but I'm not 100% sure.
>
> That should be the right way. The more things are script-local the
> better. But chec
Alex Efros wrote:
> On Thu, Apr 24, 2014 at 12:43:01PM +0200, Bram Moolenaar wrote:
> > > Me, too. The following used to work:
> > >
> > > fun! Foo()
> > > endfun
> > > let g:Foo = function('Foo')
> > >
> > > After 7.4.264, I get:
> > > " E705: Variable name conflicts with existing
Hi!
On Thu, Apr 24, 2014 at 12:43:01PM +0200, Bram Moolenaar wrote:
> > Me, too. The following used to work:
> >
> > fun! Foo()
> > endfun
> > let g:Foo = function('Foo')
> >
> > After 7.4.264, I get:
> > " E705: Variable name conflicts with existing function: g:Foo
>
> That is corr
> > E121: Undefined variable: g:vundle_last_status
> > E15: Invalid expression: 'error' == g:vundle_last_status
>
> These might be the result of another error, causing the variables not
> being set.
I've never had any problems before patch 260. since there was a discussion
going on that patch, I
Matteo Cavalleri wrote:
> > > Patch 7.4.264 (after 7.4.260)
> > > Problem:Can't define a function starting with "g:". Can't assign a
> > > funcref to a buffer-local variable.
> > > Solution: Skip "g:" at the start o
Ingo Karkat wrote:
> What I find inconsistent and strange is that though I can define
> g:Foo(), I cannot call it with that global-scoped name:
>
> fun g:Foo()
> return 42
> endfun
> echo Foo()
> 42
> echo g:Foo()
> E117: Unknown function: g:Foo
> E15: Invalid e
On 24-Apr-2014 12:43 +0200, Bram Moolenaar wrote:
> Ingo Karkat wrote:
>
>> Me, too. The following used to work:
>>
>> fun! Foo()
>> endfun
>> let g:Foo = function('Foo')
>>
>> After 7.4.264, I get:
>> " E705: Variable name conflicts with existing function: g:Foo
>
> That is correct.
Ingo Karkat wrote:
> Me, too. The following used to work:
>
> fun! Foo()
> endfun
> let g:Foo = function('Foo')
>
> After 7.4.264, I get:
> " E705: Variable name conflicts with existing function: g:Foo
That is correct. Previously Foo() and g:Foo were different names, which
is wron
On 23-Apr-2014 23:11 +0200, Matteo Cavalleri wrote:
>>> Patch 7.4.264 (after 7.4.260)
>>
>>> Problem:Can't define a function starting with "g:". Can't assign a
>>
>>> funcref to a buffer-local variable.
>>
>>&g
> > Patch 7.4.264 (after 7.4.260)
>
> > Problem:Can't define a function starting with "g:". Can't assign a
>
> > funcref to a buffer-local variable.
>
> > Solution: Skip "g:" at the start of a function name. Don'
On 23 April 2014, Bram Moolenaar wrote:
>
> Patch 7.4.264 (after 7.4.260)
> Problem:Can't define a function starting with "g:". Can't assign a
> funcref to a buffer-local variable.
> Solution: Skip "g:" at the start of a function n
Patch 7.4.264 (after 7.4.260)
Problem:Can't define a function starting with "g:". Can't assign a
funcref to a buffer-local variable.
Solution: Skip "g:" at the start of a function name. Don't check for colons
when assigning to
22 matches
Mail list logo
