Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
So I have to ask
Aside from absolute emergencies
Why would you use a terminal text editor ?
There are tons of GUI ones that work on multiple platforms
Hell and if you don’t like vs code or pycharm or eclipse there’s gnome edit -
Look, I am not saying there is anything wrong with learning about Micro or other simpler text editors. But getting to know vim, and learning through muscle memory can definitely help you a lot in the future. I deal with vim on a daily basis, and even though I consider Emacs a powerhouse, I still know Vim better and use it as my go-to development environment. You don't need to neckbeard over these systems, I got into it because other neck beards told me it was the best thing since sliced bread. But it has come useful from time to time. If you want to, then just learn basic things such as moving to the end of a file, looking for things, etc. In a server it is sometimes the only thing you have.
-
MrAwesome53yI use jetbrains IDE (PHPStorm) with vim bindings, best of both worlds. Learned vim first, totally worth it.
-
@MrAwesome why does no one ever mention this ptimiyive editor which is less a pain in the ass https://en.wikipedia.org/wiki/...
-
YADU13893y@MadMadMadMrMim once you memorize 5000 vim keybindings you get to feel smugly superior to everyone for the rest of your life
-
fuckwit12163y@MadMadMadMrMim I work on the terminal for around 80% of my time. Never leaving the terminal saves a lot of time for me. Also moving the hand away from the keyboard to the mouse, do stuff and move it back is just slow. That's also the reason I use a tiling window manager with with tons of keybinds for moving around.
-
@fuckwit what kind of tasks do you work on the most ?
see thing is a developer this idea of 100 wpm doesn't mesh once the initial code has been laid down or the project doesn't require research or something so the speed aspect doesn't seem to really lay out unless its an involved task that I can just bug out on.
so I'm curious what would be so involved and tedious it would require you to specifically do what you're describing.
i don't feel ide's slow me down, i feel they greatly reduce the keystrokes i have to engage in with things like autocomplete and hover over reference etc. -
fuckwit12163y@MadMadMadMrMim well I Programm stuff. Or do System administration/maintenance or document stuff. Whatever the current cycle dictates or which ever has the highest priority.
It's not about fast writing. If it were for that then anything that inputs and displays text would be sufficient.
I just like be efficient with my stuff and going from neovim to look up documentation is a simple mod4+5 F AA type stuff to search and press enter and mod4+5 to go back to neovim.
Dragging my mouse across three monitors to scroll up to a search box enter stuff and go all way back to neovim takes some time. And doing that whatever amounts of time per hour just isn't cutting it for me.
Also just because people use vim doesn't mean they give up on features like autocomplete, jumping around, refactoring or whatever an ide does. -
@YouAllSuck actually it's just a personal preference. Plus, they works way faster than any GUI code editor.
-
@souvikpaul I kind of doubt that.
The speed increases if they exist don't matter much
Besides when you have oo code which is split into seperate files, things like a symbol parser kind of come in handy as well and its much quicker and easier on the hands to reduce the number of necessary keystokes. -
Most of the popular IDEs offer vim plugin, some even offer support to vimrc which is cool
Related Rants
I found the best text editor for basic code fixing
For a couple of days, I was looking for a simple terminal-based text editor for taking simple code notes or basic code fixing kinds of stuff.
As an aspiring developer, I really like the concept of coding without touching the mouse.
So I downloaded the king of CLI text editors, Vim.
Now, guess what happened.
Yeah, you're right. I stuck inside vim and couldn't even quit from there.
Then, I started watching a bunch of tutorials and started reading vim's documentation.
But then I realized, I have to learn a lot of things only to operate vim and it's a pretty lengthy process.
At that time, I really needed a very simple text editor for doing basic stuff.
But, vim is not simple... you know :)
So, I had to come back to 'nano' & I was not happy enough to write codes by using 'nano'.
Suddenly, I discovered another really cool text editor called 'micro'.
It's really awesome.
It's not as advanced as vim but definitely a lot better than nano.
Micro is an open-source command-line text editor created by Zachary Yedidia.
Some basic key points of Micro:
1. It's really easy to operate.
2. It has different colours and highlights.
3. It supports syntaxes for over 70+ programming languages.
4. It has mouse support.
5. Plugins & colour schemes.
The best thing for me is colour schemes & screen split support.
Check out my full article on DEV - @souviktests.
rant
micro
command-line
text editor
coding