281–290 of 337 posts
Earlier quoted context omitted.
I think you missed the point of edit.
I think you missed the question I was answering in my comment.
For starters, there's your assumption that there is "syntax" to be highlighted. Not every text file is something written in a computer programming language.
Earlier quoted context omitted.
Last time I checked, micro should have been called macro based on the binary file size.
Isn't the relatively large binary just because it's written in Golang? Go executables each ship their own copy of the Go runtime. That alone accounts for a big chunk of small programs like this. Nano also links against ncurses, which is about as big as the compressed tarball for micro. I'm looking at the dependency closures of each right now in nix-tree[1], and micro's closure's total size is 15.04 MiB while nano's i…
Earlier quoted context omitted.
Last time I checked, micro should have been called macro based on the binary file size.
Seriously? We're going to complain about a couple megs in a text editor in the year 2025?
Not caring about a couple of megs here and there is what makes some modern systems so bloated.
Earlier quoted context omitted.
There is also dte[1]. It hits exactly the same notch and offers an extremely lean editor with Unicode support, CUA key bindings and much more. It has replaced nano as my terminal editor. [1]: https://craigbarnes.gitlab.io/dte/
Why are you opposed to learning vi which is already installed everywhere?
Earlier quoted context omitted.
As they explained, they needed a text editor that works in a command line (for Windows Core server installs), works across SSH (because for a while now Windows included an SSH Server so you can completely manage it through SSH), and can be used by non-vi-experienced Windows administrators (i.e. a modeless editor).
Telling people to use nano would of course have been next to impossible. Much easier to rewrite a DOS-era editor in Rust, naturally.
Now I'm waiting for EDLIN but with unicode. I remember you could use it in a batch file to script some kinds of editing by piping the keypresses in from stdin. Sort of a replacement for a subset of sed or awk. I haven't tried but this should be possible with vi too. Whether that is deeply cursed is another question.
I think ed is what you’re looking for (possibly with -s).
Was this made just cause someone wanted to do something in Rust?
Earlier quoted context omitted.
I took a screenshot and pasted it into the new Win11 Paint. Even minimized, Paint was constantly using 5% CPU and sitting at ~250MB of RAM. I guess I can begrudgingly get over the RAM, but squandering the CPU like that is ridiculous. What happened to pride or quality control or anything?
I assume it is basically an Electron app now. Anything will be bloated when it's a full web browser running some webapp.
Earlier quoted context omitted.
I think you missed the question I was answering in my comment.
There's an underlying assumption about "target audience for this editor" that you both share, that others, I suspect quite a few others, do not. For starters, there's your assumption that there is "syntax" to be highlighted. Not every text file is something written in a computer programming language.