![]() ![]() Fiddling around in nano felt inefficient for certain things, particularly when trying not to use my mouse in the CLI, I needed something better. ![]() #Macdown plugins vim full#It was huge, exciting, and full of intricate puzzles ready to solve. Using a small home server, running on an old desktop from my grandmother, I was diving head-on into a new world. Not only did I want something "cross-platform" in that it could run on Windows, OSX, and Linux, but I also wanted something that could work from the CLI and on multiple Linux distros.Ī bit before this I was diving into system administration for the first time. I want to give a bit more context to one of these: cross-platform as it was hugely influential in my decision. I think a lot of these are self-evident, I just had to choose what matted to me. In the end, my list of requirements looked something like this for my dream editor: If you are looking to choose a long-term editor, I think making a list like this is helpful! # Choosing my requirements I was hoping that formalising this list would help me make a more permanent decision as I'd moved around a lot in the years past. Instead of focusing on the specific technology or project I was working on at that time, I decided to formalise to myself what I wanted from a general editor. Now around 16, with a few years of working in these environments under my belt, I had more insight into what mattered in an editor to me. ![]() It was a mess, but I persevered swapping editors like hotcakes until I figured out what I liked. I wasn't sticking to one language for an extensive period either so no "holistic IDE" solution felt right. Vim and Emacs felt foreign at first, Notepad++ felt clunky, and Sublime for some odd reason was not clicking. # Years followingĮventually, I migrated to Sublime as it's plugin system was awesome throughout the following years I tried out all of the above options I mentioned. This list was a good start, as I avoided the heavier IDEs like Eclipse which would have bogged down my initial needs in HTML/CSS and light scripting.Īfter some deliberation, I ended up choosing Notepad++ because as I remember it seemed lightweight and extensible. That ended up being a great place to start!Īfter some extensive Googling and speaking with a few friends, I came to my final list of development environments for my first HTML/CSS/JS endeavours: Notepad++, Vim, Emacs, Sublime, and maybe some others I am forgetting. I knew I wanted to make websites and help others manage their sites as I was starting a shared-hosting service and needed to build/maintain my site as well as help my customers. Since I had no formal education in computer science, I just had my internal goals to use as a starting point. When first looking for something to work from I was only 13. To potentially save someone else the years of trials I went through when choosing their go-to work environment (which doesn't have to be Vim, but should be □ ), I'll go into some detail on why I came to my decision. Luckily, I've got an answer with a pretty long story behind it! After spending years looking at different editors, I eventually came to love Vim above all else. ![]() From that first glance, things look pretty tricky to get into I can admit, so I can't blame them! There are also arguably so many other good options on the market, many say, "Why choose Vim at all?" Many people after seeing me enter one hotkey after the next voraciously on my keyboard ask me why I chose Vim as my editor of choice. I use Vim (or vi ) for a considerable portion of my day-to-day work both professionally and recreationally. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |