Timeline for Mappings defined in vimrc file only work sometimes?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 14, 2017 at 9:32 | vote | accept | Zeth | ||
| Apr 14, 2017 at 3:01 | history | edited | Martin Tournoij | CC BY-SA 3.0 |
Clearer title
|
| Apr 13, 2017 at 16:11 | answer | added | grodzik | timeline score: 4 | |
| Apr 13, 2017 at 13:40 | comment | added | Zeth | That seems to work! Yeah, @grodzik - please post your comment as an answer. | |
| Apr 13, 2017 at 12:42 | comment | added | Wolfie |
yeah, <buffer> makes no sense outside of autocmd. But as another aside, please note that ftp transmission is not secure and your username and password are transmitted unencrypted. Consider scp or sftp instead if this matters in your working enviroment.
|
|
| Apr 13, 2017 at 12:29 | comment | added | muru |
^that. Vimrc isn't read for each buffer that's loaded, and mappings with <buffer> are only set for that buffer, so this would only apply to the first buffer (and to any in which you manually run :so $MYVIMRC). @grodzik maybe post an answer.
|
|
| Apr 13, 2017 at 11:48 | comment | added | grodzik |
Try removing <buffer> keyword, I think it doesn't make sense when defined in .vimrc in global scope (without autocmd. or smth like that).
|
|
| Apr 13, 2017 at 11:26 | history | asked | Zeth | CC BY-SA 3.0 |