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
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
Juraj Malenica -
BekahHW -
mahdi -
Sophia Semga -
Oldest comments (150)
Notepad++ ❤
I feel like VSCode is a bit too much for such files.
Do you think this feeling is a matter of practicality and productivity or more of a personal taste/aesthetic/feelings?
Both actually 😁
VSCode has many extra features (side panel for git & file explorer).
But, notepad++ gives you just the text front of you so you can make changes or peek into the file as quick as possible... save & quit.
My thinking is generally like this: Do I need to open the whole folder and play with it?
Same here, using Moba term which gives a File Explorer like interface in ssh connections, opens file in Notepad++ on my PC then saves back to same opened from directory on the remote server
vim
Same or different from the rest of your coding?
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
Sublime text
😁😁
I think it is important to use an editor that makes syntax colouring and apply rules of indentations and use of spaces/tabs coherent with the rest of the file. It even makes more sense if it is files like YAML for configuration.
By the way, I use Emacs for this. It is kind of the same than using Vim, except you can exit it.
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.
Can you articulate your reasoning for the choices?
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
Vim
Visual Studio Code for everything. :)
nano if I'm looking at something fast, Sublime Text is I will be using it for a while
I use Sublime for most of my development
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.
Nanoooo
100% nano, and if using a current release of nano, -lmx is nice °>°
Nano.
but now I see many people using VS Code to open, I will give that a try too 😀