Posts [ 5 ]

Topic: Where does _viemurc go for VS2010?

I'm a long-time ViEmu user with VS 2008.

Today I started a new job where they use 2010 and I'm trying to get ViEmu going in my new dev environment.

I have some critical bindings because I use a Dvorak keyboard, but I can't seem to get my _viemurc picked up anywhere. It seems that with the new plugin architecture in VS2010, there is no installation folder in Program Files [(x86)].

The documentation says nothing about this, and it doesn't seem to work in c:\, c:\windows, c:\windows\system32 etc.

Re: Where does _viemurc go for VS2010?

You can put your _viemurc file in the path indicated by the HOMEDRIVE/HOMEPATH environment variables or the path indicated by the HOME environment variable, and ViEmu should read it from there.

I hate to drag up an old post like this, but I've just gone through a reinstall and ViEmu won't for the life of it read _viemurc.

My suspicion is that my HOMEDRIVE/HOMESHARE is on a network drive. Which may create a known issue in Windows 7 for application that run in admin mode: those drives aren't available. According to a MS KB article it's related to UAC. I seem to dimly remember that VS2010 runs as Administrator, or am I confusing it with 2008?

Is there another location ViEmu will read from? One that will assuredly be a local drive, at least?

If this is NOT an issue related to the fact that I have my _viemurc on a network mapped HOMESHARE, I'm at a total loss!

Re: Where does _viemurc go for VS2010?

Indeed, :highlight is not supported in ViEmu. Unfortunately, we can only support a subset of vi/vim commands, and those are listed explicitly in the docs. There are many more, not supported by ViEmu, that are not mentioned. Vi has quite a few options, but vim is genuinely huge, and we can't emulate all of it. We add more and more emulation on each version, but full vim emulation is just impossible.

Hopefully, you can find some functionality in VS that will cover your needs.

And, by the way, the way to locate your home path are the environment variables HOMEDRIVE and HOMEPATH, but I understand that was not really the issue, and that part is solved.