Improve on vim mappings #40

Closed
wants to merge 3 commits into
from

Projects

None yet

3 participants

@blueyed
Contributor
blueyed commented Apr 28, 2011

No description provided.

blueyed added some commits Apr 5, 2011
@blueyed blueyed Do not add normal mode mappings for Vim.
Closes #35
7ab92a4
@blueyed blueyed Improve mapping for Vim, using <Plug> maps>
Add redirection through <Plug>SparkupExecute and <Plug>SparkupNext and
check if mappings are defined for them before assigning default maps.
72deab1
@Osse
Osse commented May 19, 2011

I have a different mapping issue with sparkup.py. I have switched . and : with "noremap . :" and "noremap : ." because I use : much more often than . and my (Norwegian) keyboard is set up so that S-. produces :

I wonder if your suggestion also fixes this issue. I see you use imap instead of inoremap but there is some other Vim-fu there that I don't understand.

I have tried replacing imap with inoremap in the original sparkup.vim with success. I haven't noticed any side effects.

@blueyed
Contributor
blueyed commented May 23, 2011

@Osse: Yes, it should be using inoremap - otherwise the : being used would get mapped to . with your mapping. I will change my pull request accordingly - I had just kept it like it was.
Thanks for notifying.

@blueyed blueyed Use `inoremap` for calling Sparkup{,Next}().
This will make the mapping work properly with e.g.
`noremap : .`.

See #40 (comment)
0decf72
@faceleg
Collaborator
faceleg commented Aug 22, 2013

Would you consider syncing this with master? Then I'd be able to merge it in more easily.

@faceleg faceleg closed this Oct 1, 2013
@mikker mikker pushed a commit to mikker/sparkup that referenced this pull request Dec 2, 2013
@blueyed blueyed Use `inoremap` for calling Sparkup{,Next}().
This will make the mapping work properly with e.g.
`noremap : .`.

See rstacruz#40 (comment)
6faebdb
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment