this post was submitted on 23 Apr 2025
973 points (98.2% liked)
Microblog Memes
7456 readers
3538 users here now
A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.
Created as an evolution of White People Twitter and other tweet-capture subreddits.
Rules:
- Please put at least one word relevant to the post in the post title.
- Be nice.
- No advertising, brand promotion or guerilla marketing.
- Posters are encouraged to link to the toot or tweet etc in the description of posts.
Related communities:
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
In the 20th century I'd expect something that can open, edit and save plaintext files. But we're 1/4th of the way into the 21st century.
I find I have two uses for a plaintext editor: plaintext, and computer script. I don't like using rich text editors like Word for writing notes and such because the formatting options just get in the way; plaintext lets me "just write." And for this, there's very little automation that will be helpful.
In the Linux ecosystem, plaintext editors are all trying so hard to be IDEs. They'll close parentheses or quotes or whatever for you, and if you're doing something like 15" to mean fifteen inches you'll get two, you'll hit backspace and it'll take both away...it doesn't help.
If I'm programming anything of any size I'm going to open an IDE, probably because I'm working within some ecosystem. If I'm writing a couple lines of Bash I'll probably use Vim. So I'd rather tune my plaintext editor to write actual .txt files, as prose.
3rd use perhaps being syntax recognition?
That would fall under "computer script."
I am either: