cknadler
Add commandline option to launch terminal vim session
Added this option because I don't have gvim installed, and would rather use vim in a terminal.
Hey Todd,
Thanks so much for the PR! Can you update the readme to reflect this change?
Also, any ideas on how this would work on OSX? I'm hesitant to add new features if they aren't cross platform as it makes the documentation a bit of a minefield.
Cheers, Chris
Sure, I'll update the readme. As for OSX, I unfortunately don't know, and don't have a machine to try and figure out how to get it to work.
Thanks! I might hold off on this for a bit until I (or someone else) figures out OSX support.
Yeah, I understand. I updated the readme for this PR. If anyone figures out MacOS support, feel free to message me and I will add it to this PR.
@toddgaunt Awesome, thanks for doing this! I created #70 to see if anyone wants to tackle OSX support.
@toddgaunt while we're here, it possible to support neovim as well? It's basically one letter in the executable filename: nvim.
@balta2ar, not a bad idea. I could add test that would go in this priorty: nvim -> vim -> vi. I'll look into this if we can get an OSX patch.
I need nvim 0.5+ support to really be able to use vim-anywhere, as my config is now converted to Lua. I think it should be trivial to implement MacOS support to this PR. What's the best way to contribute a change on a change? Should I fork from @toddgaunt 's branch and submit a PR to that?
[Edit] Scratch that, this PR is so stale that the source is deleted now. I'll just work on the MacOS support for right now and wait for any info on how to proceed with the PR. I'm trying to avoid just freshly implementing Todd's changes in my PR and not having proper contribution in the history.
I'm trying to avoid just freshly implementing Todd's changes in my PR and not having proper contribution in the history.
Whatever makes it easiest/most acceptable. I don't really care myself, or just mention it in the commit.