You are not logged in.
I've been banging my head with this for a while, and my google-fu is failing me. Sometime not long ago, my vim installation started doing something strange: when I open it, or open a file, rather than starting in normal mode, it starts in command mode with various commands loaded in-- most often I see :1R. It's an annoyance, since I only have to clear it out and I'm back to normal mode, but since I use it so frequently I'd like to fix it.
I haven't changed my .vimrc in a long while, and looking at it I verified there's nothing strange happening there. I have no plugins, no .vim directory at all.
Has this ever happened to anyone, and do you have any suggestions about fixing it?
Last edited by DrMag (2013-08-23 03:50:35)
Offline
Do you have any vim related aliases? And/or does the same happen if you use /usr/bin/vim ?
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
No aliases, /usr/bin/vim yields the same result, this time the command line has :.,.+71R. I've tried removing .vimrc, and the same thing happens.
Offline
I'm assuming you aren't deliberately saving sessions. '$HOME/.viminfo' is a history file for vim, try removing it or renaming it before you next start vim. And scan ':h viminfo' if you're curious.
I sometimes see search highlighting remembered from a previous session, I'm never put into command mode.
Offline
Ok, I've been able to isolate where the problem is, and it's not actually in Arch. Mostly I use my Arch box remotely, and I've been connecting to it through the Bitvise Tunnelier ssh client. If I'm on the direct terminal, or ssh'd in through PuTTY, the problem doesn't occur, so it looks to be a bug in the Bitvise software. I'll have to take it up with them. Thanks for the help; I still welcome other suggestions if you have them!
Offline
File a bug with the NSA ![]()
Please remember to mark your thread as [Solved] by editing your first post and prepending it to the title.
Offline
Bitvise was very responsive to my bug report; apparently the problem has been located and will be fixed in the next release.
Offline