We're a place where coders share, stay up-to-date and grow their careers.
Posted on
And is it the same editor you use for the majority of your software development?
For further actions, you may consider blocking this person and/or reporting abuse
It's a scientific fact.
AscendixTech -
Ankan Saha -
Erin Bensinger -
Hari Narayan G -
Once suspended, ben will not be able to comment or publish posts until their suspension is removed.
Once unsuspended, ben will be able to comment and publish posts again.
Once unpublished, all posts by ben will become hidden and only accessible to themselves.
If ben is not suspended, they can still re-publish their posts from their dashboard.
Once unpublished, this post will become invisible to the public and only accessible to Ben Halpern.
They can still re-publish the post if they are not suspended.
Thanks for keeping DEV Community 👩💻👨💻 safe. Here is what you can do to flag ben:
Unflagging ben will restore default visibility to their posts.
Top comments (158)
Confusingly, this is the
onlything I use vim for. Everything else is in a different tool.I don't find this to be overly odd. I was actually specifically curious as to whether this was a thing.
I think since some people (myself included) think of vim as an editor just for quick edits, we use it for just that
What about the thought that stuff like
viis often the default way to do these things, it becomes your standard procedure, even if for code editing you've always used other types of editors?I feel like this scenario could play out because folks may not switch off of the approximate default behavior.
What if the situation in which we edit these files is one where we're on an ssh connection in a console window where vim is the most powerful choice that isn't a desktop application? And then that becomes default behavior for config files, like you suggest.
I used to do this in
vim, I think because I thought it was quicker. Since I have VS Code open almost all of the time, especially if I'm doing something to.bash_profile, it's just as quick to open in Code and easier (well, more comfortable) to edit.Also, I have tended to use the terminal from within VS Code more these days, so the whole open and edit process can happen in the same program and I like that.
For me it's the same. The only downside is that my vim skills don't evolve as fast as I want them to.
SAME! I have never even considered opening it in Sublime which is my main editor of choice when I am coding
I do the same.. but i use nvim.
I use the same, and never thought about other tool to edit it.
Nanoooo
100% nano, and if using a current release of nano, -lmx is nice °>°
code -r /path/to/fileThis opens the file with VS Code to the same workspace as rest of the files making it a really fast process. Then just save and close it like usual. I'm only using Vim when I'm working over SSH.
Cool. I don't know it
nano -wIf you're just going in and out, why get fancy. You still get emacs-like keyboard nav at a fraction of the cost.
On Linux I like use more nano than vim
Vim, but i also use vim as my regular editor.
I feel like if you use a terminal editor, it's probably the obvious choice.
I'm curious if folks who use standalone editors choose terminal apps in these contexts.
It is (I do everything except Java in NeoVim); but also, if I'm just looking something up and don't mean to make changes, we've got other shell tools. I use
lessandgrep/rga lot with history files and so on.Makes sense
Nano.
but now I see many people using VS Code to open, I will give that a try too 😀
Vi. It was the only editor in town other than emacs when I first learned to edit anything on the computer.
I still use Vim for CLI stuff and VS Code for other stuff. Don’t know why I don’t use Vim for writing anymore. Probably years of other options making their way into MY $PATH.
Same
Vim, and I’ll use that as my regular editor if it’s just a few files I’m throwing together to try something, or if it is on a less powerful computer. It works good but looking at multiple files and projects, I can’t be as productive. I know the shortcuts and the plugins. It just doesn’t work as well as vs code for me.
Vs code is definitely my high productivity, big brain space editor of choice. It is just generally a little slower if I’m just tweaking a few lines or doing a quick search and replace.
Although, vs code does have some amazing command line flags that make it ideal for git commit message editor, diff viewer, and more.
vihas been a tough habit to break. I use it pretty much anywhere I can (thank you Cygwin/Moba). And, when I can't use it, I pray that, at the very least, I can install a copy of Notepad++ (harder, these days, now that Windows 10+ more-easily affords enterprise-managed systems the ability to allow only the installation of whitelisted tools).Nano or VS Code, with using only VS Code looking likely going forward after seeing some of the comments here. Slightly controversial perhaps, but I never bothered to learn
vimsince I just want to open something that works and code away, rather than having to learn another language before I can do that 😂I swear by Micro. It has made editing in the command line a joy.
Features:
Sublime text
😁😁
I do some hefty customization with my bash_profile, so opening up in VS Code (along with everything else) is nice. I don't use vim and nano would fine if I had a smaller file. It's not much to do
code ~/.bash_profile.Nano makes a lot of sense in its control scheme.
Nano : if I am on terminal
IntelliJ : for practicing Java
Gedit : writing diary, editing files launched from file manager and just about everything else
BONUS :
echo $TEXT >> $FILE_PATHfor just adding a line at the EOF