11–20 of 303 posts
[flagged]
Much to my surprise, I recently found nano was symlinked to pico on macOS. It'd been niggling at me for a while, I'd just assumed I'd been given an older version of nano. Guess I was kind of right.
Remote VSCode is kind of magic, I'm increasingly working in (local) VMs via it. I have one project that is probably never going to never going to support ARM, and I'm close to needing to upgrade my MacBook. I really want an M2, but this project would be hard to run locally on it. VSCode on a remove VM is probably going to be the answer.
[flagged]
All of the old editors are horrible. Nano, vi, emacs... sure they might be conveniently placed, but are a pain to learn. This one is a vast improvement https://micro-editor.github.io/
If you don't want the power, or don't need the tool, fine. I get that.
But calling vi terrible, is like complaining that a sledgehammer is terrible, because you want to hang a picture, and that's all you have.
I used to be a nano user but now whenever I want to use a terminal text editor I will almost always use micro as it has built in support for most languages. https://micro-editor.github.io/
vim does just as well and has a lot more functionality universally.
There was a time (2006?) when I was getting into linux. I was a big microsofty, due to comfort mostly, and I was shamed into trying Linux. Like most people I went Ubuntu first, but wifi drivers at the time were lacking, and nvidia of yore was certainly not better than nvidia of now. Suffice it to say: I spent a lot of time in the terminal trying to fix things. Nano was my tool of choice because: honestly the initial…
Perhaps, but your experience sounds like a good blueprint for what new terminal users might want. Start with nano move to more powerful tools when you need them.
All of the old editors are horrible. Nano, vi, emacs... sure they might be conveniently placed, but are a pain to learn. This one is a vast improvement https://micro-editor.github.io/