On Sun, May 19, 2013 at 05:52:22PM +0900, Andre Sihera wrote:
> On 19/05/13 03:27, meh. wrote:
> >I'm writing a fairly complex statusline and using %!Func() as
> >statusline, everything was good until I started using my new shiny
> >statusline and I realized the context it's run in is the current
> >window and not the context %{} would use, so the one the statusline
> >belongs to.
> >
> >Is this intended? Because it makes doing what I want to do basically
> >impossible.
> >
> In my experience, this is a bug. It is definitely not intended.
>
> I reported the same problem around 2~3 years ago but nobody
> really took an interest in it then either. My problem was that buffer-
> specific variables and buffer-specific context in functions weren't
> resolving properly with the %! syntax. The same problem you're
> experiencing I think.
Well that sucks.
> The only workaround then was to use %{...} syntax to call a global
> function which directly established the current buffer, from which
> the correct buffer scope for accessing the buffer-specific variables
> could be recreated.
Do you have any examples? I'm trying to do it but it's not working
very well.
--
--
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 Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
