- Hi there, fellow vim-mac'ers!
I recently received a MacBookPro, and am in the process of setting it
up for development work. One of the main things I need, of course,
is a working version of vim -- so naturally I tried the latest
available "universal" build (by downloading vim7.0e.02-univ.tar.bz2
from the macvim.org web site).
So far it *kind* of works. File associations work great (unlike with
the earlier vim7.0c2-univ version I tried initially), and it does
seem generally reliable. However, something is seriously wrong with
the keyboard mappings: my _gvimrc file contains a bunch of custom
keyboard mappings like:
map <C-Left> 0
map <C-Right> $
But these simply don't work under vim7.0e.02, while they've worked
fine for years under vim 5 and 6. Basically, it looks as though
*all* my "map" statements are being ignored. I know you've had
reports of some other obscure problems with keyboard mappings, but it
seems to be more seriously mucked up on my machine for some reason,
as all my keyboard mappings appear to be affected.
Overall, I'd say this is an excellent beta release -- it's just this
one bug that's driving me crazy! This is on a stock-standard
MacBookPro running 10.4.5 and with vim7.0e.02-univ.tar.bz2
installed. Any suggestions -- or anything I can do to help track
down this bug? It's been 100% consistently wrong on my machine, so
maybe I can help with bug-chasing in some way.
PS: I'd also really appreciate a version compiled +python, as I've
had to disable the python scripts I wrote. Any chance of an updated
- Hi Erik,
I had a similar problem mapping <F13>.
I typed control-K F13 when I was setting up the :nmap.
That took care of the <F13> not recognized. Although it did not insert a
<F13> (five characters) into my vimrc file, it did put in the escape
sequence. Maybe the control-K <KEY> trick will work for your <C-Left> and
Alternatively, try control-V <KEY> trick, which will take the initial Escape
literally, when you set up your mapping.
(On my machine, control-K control-Left didn't work. But the control-V
control-Left did work. I'm not on 7.0e.02 though, and I haven't purchased a
MacBook Pro 17 yet -- but it's on my todo list and my wife gave me clearance
from the tower. That'll be a nice upgrade from my black-clamshell Powerbook
- Hi Eljay,
> I had a similar problem mapping <F13>.Unfortunately, that doesn't work for me -- typing control-K control-
> I typed control-K F13 when I was setting up the :nmap.
> That took care of the <F13> not recognized. Although it did not
> insert a
> <F13> (five characters) into my vimrc file, it did put in the escape
> sequence. Maybe the control-K <KEY> trick will work for your <C-
> Left> and
Right (in insert mode) simply inserts "<Right>" into the document
rather than "<C-Right>". Ditto for control-V. It seems that these
control-key sequences are ignoring modifier keys when inserting
keycodes (at least under 7.0e.02). Mapping F13 worked fine for me,
I tried your suggestion both in insert mode (to change my _gvimrc
file), and in command-line mode when entering an Ex command (ie,
typing ":map <Control-K><Control-Right> $"). No luck either way, I'm
afraid -- I always just get "map <Right> $".
The interesting thing is that if I enter the above mapping, it works
as it should! Of course, I don't want the right-arrow key mapped to
$, but at least that works correctly. It seems that vim-7.0e.02
doesn't recognise modifiers when mapping the arrow keys, even though
it recognises the arrow keys by themselves.
Hopefully this gives the mac-vim folks some useful clues to help
solve this mystery!
> Alternatively, try control-V <KEY> trick, which will take theThanks for the suggestions, even though they didn't work. And good
> initial Escape
> literally, when you set up your mapping.
> (On my machine, control-K control-Left didn't work. But the control-V
> control-Left did work. I'm not on 7.0e.02 though, and I haven't
> purchased a
> MacBook Pro 17 yet -- but it's on my todo list and my wife gave me
> from the tower. That'll be a nice upgrade from my black-clamshell
> G3/500 "Pismo".)
luck on the MacBook Pro purchase...
- Hi Adam,
> I've got a python enabled universal build atThanks! That's fantastic -- I tried downloading your version of vim
7.0g, and it not only included Python support, but also fixed the
mapping problems I was having. And it even fixes a long-standing
problem I had with "set clipboard=unnamed" (which has been broken in
vim version 6.x for the last year or so).
Thanks a million. I'm an extremely happy camper now!
> also fixed the mapping problems I was having.Interestingly, this build also fixes the strange mappings of <D-Left>
et al that I saw last night. Backspace is still broken, but that
seems a perennial problem.
We're cycling through Cambodia to raise money for Oxfam, help us
- Le 1 mai 06 à 12:58, Afternoon a écrit :
> Backspace is still broken, but that seems a perennial problem.What kind of backspace problem ? I had several which seem all solved