Please avoid double negatives. I’m not quite sure of the meaning of your sentence.
If you’re saying I have issues using vim if I can’t use it in an IDE, no, that’s not how it works. If you use simple vim (not much more than knowing how to get in and out of edit/visual mode, and use hjkl for navigation), then it’s fine. Once you get into more advanced vim features, though, the key presses in vim get picked up by the IDE first, so IDE shortcuts take precedence.
If someone were to learn vim inside an IDE and develops it organically as part of their flow, it’d be fine. If you already have a lot of standalone vim flow setup in your mind, it’s a problem.
Please avoid double negatives. I’m not quite sure of the meaning of your sentence.
If you’re saying I have issues using vim if I can’t use it in an IDE, no, that’s not how it works. If you use simple vim (not much more than knowing how to get in and out of edit/visual mode, and use hjkl for navigation), then it’s fine. Once you get into more advanced vim features, though, the key presses in vim get picked up by the IDE first, so IDE shortcuts take precedence.
If someone were to learn vim inside an IDE and develops it organically as part of their flow, it’d be fine. If you already have a lot of standalone vim flow setup in your mind, it’s a problem.