For my small bash and paython scripts i use VSCodium. Iam not an devoloper, all just for fun.
1 Like
Iāve been using vi, but only because I donāt know how to exit. 
4 Likes
the joke is good! and so much truth in it
1 Like
Quite a few actuallyā¦Obsidian for markdown, Xed for regular bash scripts and Python config files, VScodium for HTML/CSSāPHP/Javascript. When in terminal I use Micro, way better than VI, Less etc. Has sensible shortcuts to close/quit/save you actually remember. 
2 Likes
Okay i use Obsidian too, for my personal wiki. For config files Kate und in terminal nano.
1 Like
Thank you all. I only use Neovim and Cursor with no language model and that serve all the purpose. I am a heavy Neovim user for all from Python, GO, RUST from analysis to deep learning, system administration and also code writing and starting back CPP after few years for integration with CPython and RUST to make it complete. I am not into that making fancy websites(out of my interest, I am more of a compiled binary writer since start of the programming) so i am not sure about the web plugs that use. I only use for database and front end of the database.
For programming purposes I use Visual Studio code, Visual Studio community, notepad++, nano (I discovered it exists an equivalent for Windows powershell!) and geany.
For taking personal notes, as secondary brain, I use obsidian.
-ricky
1 Like
Hey Ricky, thank you for that. I didnāt realize notepad++ was available for Linux. Now I know.
1 Like
@shybry747
Post is generic, it does not require to specify an OS ā¦ however Iām using Windows 10 as primary computer, I use notepad++ beside Visual studio community.
Also Visual studio is community is not available for Linux (:
cheers.
1 Like
Iām a text editor freak so I use a lot of editors every day.
Just to keep it simple I have nano for non GUI command editing, geany as a simple GUI editor and xnedit for writing plain text articles.
The truth is that I almost always have a vi and Emacs editor available too.
2 Likes
I just realized I didnāt answer the question.
I currently use Visual Studio Code and nano on Linux. I use NotePad++ and Geany on Windows.
Back in my Dos days, we used a program called MultiEdit. When we upgraded to Windows MultiEdit released a version for Windows. When I started Java and then .NET programming then I moved to Visual Studio.
1 Like
I am currently switching from VSCodium to Pulsar.
Pulsar feels more lightweight.
1 Like
For Rust, my current obsession, I use Codium on Win 10, which works great on a large monitor. However, with Win 10ās upcoming demise, Iām making plans, and they all include Debian. During my entire *nix life, Iāve needed a terminal editor. Emacs was my favorite for decades, but its chording (finger stretches, e.g. ctrl+f) killed my hands recently. Bummer. Iāve never been a vi fan (used it often decades ago). Helix caught my eye recently, itās on my Ubuntu laptop, and I used it on a small embedded Rust project. Itās not hard on my hands (yay!), but I havenāt wrapped my head around its UI. Since finishing the embedded project, Iāve been 100% back on Win 10 and Codium, but that shipās about to sail. Any other editors I might check out that is terminal capable and doesnāt need a bazilion ctrl+* keystrokes?
1 Like
Though, today, I regularly use micro for most cmd line editing, I still occasionally use vi. Even now, my muscle-memory for those vi commands continues to be in place. Itās weirdā¦
For coding, I currently use VSCode. I had been using VSCodium (I am NOT a fan of MS. Is anyone that knows computers a fan of them?) but went to VSCode because ā well, I now forget why 
But I have extensive .NET experience from my career so maybe something to do with that.
2 Likes
I primarily use Neovim (NvChad) and Micro
1 Like
Mat, if you put either a āDoomā or a āSpacemacsā configuration on top of a reasonably recent instance of GNU Emacs, you can get most of the features of either Emacs or vim, (and the access to either of their key bindings) but also additional bindings that are much easier on the hands. Some of the bindings require 2-3 key presses but none of them MANDATE the use of either Ctrl or Esc, though the ātraditionalā vi and Emacs bindings are still āout thereā. Spacemacs adds so much stuff that, to be honest, you need a reasonably current system (ideally less than five years old), but with current hardware either Doom or Spacemacs will absolutely ROCK. Like any Emacs setup, thereās so much stuff available that you may use only a fraction of it, but what you need will almost certainly be there - without the sore fingers of the past with Doom Emacs or Spacemacs.
2 Likes
I typically favor a less-is-more configuration, but not having to type Ctrl is significant enough to (maybe) move me from my snobbery. Possibly. 
And, as a matter of fact, Emacs loads a monstrous amount of lisp code when itās built, so I shouldnāt be too put off by adding config files. Thank you immensely for pointing out Doom and Spacemacsās bindings. I had heard of them before, but always coupled with ācool newā stuff, which often means ābreaks stuffā. Iām adding āemacs confgsā to my todo list.
1 Like
Mat, I was messing with GNU Emacs on one of my systems and I set up a quick way to move between Doom and Spacemacs; until this test, I had been favoring Spacemacs over Doom Emacs, but after the test, I found that most of the space key bindings are available in both. Doom Emacs can definitely āplayā like vi or Emacs, plus add a few space key bindings to reduce hand stress. Bottom line is that I switched preference: both do the job, but Doom Emacs is faster and every bit as useful. Unless youāre stuck on lighter, more efficient environments, keep in mind that Doom Emacs is more than an editor; itās an extremely powerful IDE - Integrated Development Environment, capable of āworkingā like either Vi or Emacs, somewhat bigger, but a LOT of attention has been paid in Doom Emacs to make as many components as efficient as possible; I evaluated it critically and found that those āefficiencyā improvements WORK big time; excellent full featured, powerful and yet reasonably fast tool!
A friend of mine from a long time ago, back when I worked at Digital (DEC), also worked there, but then joined one of the fast moving Internet companies; I think it was BEA - who were big creators of Web based systems that rapidly advanced a lot of Web-based technologies 25-30 years ago. Anyway, this friend told me that in his multi-system environment used to produce his code, he was using a lot of Microsoft Visual Studio - the full-featured tool, even back then and said that it was an excellent tool. Recently Iāve tried code, code-insiders and code-exploration. Iām not doing much more than tweaking a few bash, Perl, and Python scripts these days, but I do notice that these editors, while not the only ones, they all do work efficiently and quite well, and theyāre capable of color coding keywords and expressions, which helps quickly locate things Iām experimenting with on my moderate sized scripts and tools.
changed my life and I went VERY HARD into Zed
At this point I am tracking the core developers and seeing a space open in the entire field, especially as it pertains to LLM code-assistance
Which then also triggered a chain reaction in other areas
I commented on this elsewhere but if there were an armistice in the area of forum stimulation and a degamification, I would love to showcase some of the unbeatable traits of Zed ā¦ Hands down the best thing to happen to my workstation in like 10 years ā¦ and I have barely opened the box
Updates SO MUCH! But you can turn it off and take them all to the face on your own interval
Like I said, my wife is using it for Markdown also.
As we know, the real metric is the Hotwife Test 
I would sky-write about this āIDEā