b:foo and g:foo. Or s:foo_default otherwise.
So far, {default} is not optional as I have both integer and string
variables, and I can't easily tell the exact type of the variable.
Having such function as builtin would be nice. I can easily cope without
it. But still, it would be nice.
--
Luc Hermitte
http://hermitte.free.fr/vim/
f
...
:SomeExpectedCommand foobar
However, with vim7 I do not see the point of such complex dependency
enforcements anymore. autoloaded plugins seem to be a much better and
simpler solution.
Regarding the g:force_reload_plugin_name, it eases plugin maintenance.
--
Luc Hermitte
http://hermitte.free.fr/vim/
* On Thu, May 25, 2006 at 11:02:29PM -0400, Benji Fisher <[EMAIL PROTECTED]>
wrote:
> On Thu, May 25, 2006 at 03:17:54PM +0200, Luc Hermitte wrote:
> > * On Thu, May 25, 2006 at 08:30:52AM -0400, Benji Fisher <[EMAIL
> > PROTECTED]> wrote:
> >
> >
=)
What about @= ? Can I use it to execute a sequence that will change the
mode to insert- or select-mode, according to the result of my function ?
Or is it also an undocumented feature that may not be supported in the
future ?
--
Luc Hermitte
http://hermitte.free.fr/vim/
urn select."\"
endfunction
nnoremap !jp! @=N_jump()
imap !jp! !jp!
function! I_expand_n_jump()
let str = "toto\ntiti\ntutu"
let l = line('.')
put=str
exe l
normal !jp!
return "\\"
endfunction
inoremap !exp! =I_expand_n_jump()
--- >%
--
Luc Hermitte
http://hermitte.free.fr/vim/
