Ben Schmidt schrieb:
The builtin Escape key already expands abbrevs. Isn't this like a
part of its definition? If I put esc on the right side of a
noremap, I do this in order to get this builtin behaviour.
I disagree. If *I* put Esc on the right hand side of a mapping I do
it to get the
Of course an abbreviation given in the
{rhs} of a :noremap is not to be expanded, just like any other user
mapping.
My example
:ino esc esc
targets an abbreviation that is not part of the mapping, but already to
be found in the text.
That makes sense. I didn't realise you were
Nikolai Weibull wrote:
I have the following mapping:
map g: Esc:set operatorfunc=SIDget_command_mode_rangeCRg@
and have recorded
g:}j^M
into register 'a'.
Running @a now does nothing.
Why?
(It should run :join from the current line to the end of the current
paragraph.)
It might help
On Jan 8, 2008 6:45 PM, Charles E Campbell Jr [EMAIL PROTECTED] wrote:
It might help folks help you if you included the
get_command_mode_range() function.
Ugh, yeah, I'm beginning to have a suspicion as to what the problem is:
function! s:get_command_mode_range(type)
let b = line('[)
let
I'm exploring functional programming with vimL and immediately ran into
seemingly counter-intuitive behavior:
function! Outer()
let outer_var = 0
function! Inner()
let outer_var += 1
endfunction
call Inner()
Ian Tegebo wrote:
I'm exploring functional programming with vimL and immediately ran into
seemingly counter-intuitive behavior:
function! Outer()
let outer_var = 0
function! Inner()
let outer_var += 1
On Jan 8, 10:00 pm, Ian Tegebo [EMAIL PROTECTED] wrote:
I'm exploring functional programming with vimL and immediately ran into
seemingly counter-intuitive behavior:
function! Outer()
let outer_var = 0
function! Inner()
Nikolai Weibull wrote:
I have the following mapping:
map g: Esc:set operatorfunc=SIDget_command_mode_rangeCRg@
and have recorded
g:}j^M
into register 'a'.
Running @a now does nothing.
Why?
(It should run :join from the current line to the end of the current
paragraph.)
It might help folks help you if you included the
get_command_mode_range() function.
Ugh, yeah, I'm beginning to have a suspicion as to what the problem is:
function! s:get_command_mode_range(type)
let b = line('[)
let e = line('])
if b e
let range = '.,+' . (e - b)
I like using the '**' wildcard
in commands which search for files. I REALLY like adding a digit to
the end of it to limit how far it digs. I wish it could
work with the globpath() function.
From editing.txt, line 1471:
The file searching is currently used for the 'path', 'cdpath' and 'tags'
Ben Schmidt wrote:
Adri Verhoef wrote:
An easy way to reproduce this bug:
$ echo y y
$ vim -u NONE y
y 1 line, 2 characters
Then type ) and the cursor moves one position to the right, although
there's nothing there!
Vim 7.1 - Included patches: 1-2, 4-6, 8-12 - on Fedora 7.
I
Adri Verhoef wrote:
An easy way to reproduce this bug:
$ echo y y
$ vim -u NONE y
y 1 line, 2 characters
Then type ) and the cursor moves one position to the right, although
there's nothing there!
Vim 7.1 - Included patches: 1-2, 4-6, 8-12 - on Fedora 7.
I believe Bram fixed
An easy way to reproduce this bug:
$ echo y y
$ vim -u NONE y
y 1 line, 2 characters
Then type ) and the cursor moves one position to the right, although
there's nothing there!
Vim 7.1 - Included patches: 1-2, 4-6, 8-12 - on Fedora 7.
Adri
Your code is equivalent
to this :
function! Outer()
let outer_var = 0
call Inner()
echo outer_var
endfunction
function! Inner()
let outer_var += 1
endfunction
call Outer()
-
On Jan 8, 2008 3:00 PM, ap [EMAIL PROTECTED] wrote:
On Jan 8, 10:00 pm, Ian Tegebo [EMAIL PROTECTED] wrote:
I'm exploring functional programming with vimL ...
Btw where did you get the idea vimscript is a functional language ?
Apologies for not being more clear. I meant to say:
I'm
15 matches
Mail list logo
