Which editor do you use when opening files like .bash_profile, etc?

💯 vim, nano confuses the heck out of me.

Whatever's handy at the time: VSCode, Notepad++. Occasionally WEE. I use the first two interchangeably for software development.

Either VI (NeoVim) or VSCode

vim with plugins

I don't edit anything outside of vim. It's just most efficient for me. I have no arguments about vim being good or bad for other people. I only know that I run circles around others when in group editing situations [even without plugins].

With that said, my first question to potential programming employees in the past has been "what editor do you you use?". I've never cared what the answer was beyond that there IS an answer.

Personally I hate mouse / cursor interaction. It's bothersome to me. But I'm not going to say that my method of interacting with clunky computers is better than others. The answer should always be, 'whatever works'.

I use a tool called Micro(golang) for non sudo purposes. micro-editor.github.io/

Else nano or sublime

vi has 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).

For the longest time, my answer was nano.

Then, I’ve been trying to get better at using dotfiles across multiple operating systems — Mac, Chromebook, Linux servers.

This means I treat the files more like a program, so I use my usual editor, VSCode.

However, when I am editing on the command line, I’ve been using micro — think of it as an upgraded nano that also has mouse support and a bunch more features. Including that you just download the binary and don’t need admin access to use it.

VS Code for everything these days. I just started using the Insider Build so I could try out the Remote Development Extension Pack.

Micro for editing files in the console. It's like nano, but better.

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_PATH for just adding a line at the EOF

Vi and seldom do I use vsc (if it requires more than few lines of editing)

Update: Reading through commends I notice more people use vim than vi curious as to why?

Emacs for almost everything

When I'm working from the shell, most of the times vi and sometimes nano. Otherwise, it would be the VS Code.

vi and nano

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 vim since I just want to open something that works and code away, rather than having to learn another language before I can do that 😂