0 Followers
30 Following
91 Posts
Profile picture cropped from the photograph titled "Fire Sparks" made by the user named "Kirrus" on Flickr at URL: https://www.flickr.com/photos/kirrus/1496231835/in/photolist-3hdzAB
License for the picture here: https://creativecommons.org/licenses/by/2.0/
Pronouns:he/she
@b0rk Personally, I use vidir to open vim, and delete special characters from filenames. I have a mapping which lets me quickly delete all instances of a character that I'm hovering over, so I can easily delete hard-to-type characters from vidir. vidir isn't vim-specific, so this would work with any other editor that can do something similar.

@b0rk @rkaj This program allegedly does that: https://github.com/f-person/auto-dark-mode.nvim/blob/master/lua/auto-dark-mode/init.lua

Seems they have neovim send a DBus request to figure out what the color is. Probably regular vim could do something similar. Vim's 'bg' settings' auto-detection doesn't get it right on my computer when I reset it as opposed to when I'm starting Vim which does make it get it right, so I am unsure whether Vim does this by default at all.

E: auto-dark-mode works on more than Linux
vim defaults to dark on startup, no matter what

auto-dark-mode.nvim/lua/auto-dark-mode/init.lua at master · f-person/auto-dark-mode.nvim

A Neovim plugin for macOS, Linux & Windows that automatically changes the editor appearance based on system settings. - f-person/auto-dark-mode.nvim

GitHub
@b0rk Start from the highest-contrast version of the colors you want, with everything set to either FF or 00, and then tone down the contrast so that it looks nice. This isn't what I did to get my colors - I don't remember what I did, exactly. But it's how I would get back the colors that I do have if I ever had to get them back from scratch.
@BrodieOnLinux I'm glad that they seem to be contributing back to the project - if they had stuck with coreutils, they might not have seen any need to do so.
@frumble If the GNU folks really wanted their ideas to win, they would have had to change themselves be more likeable to the average programmer. The average programmer isn't that different from the average person, and the average person thinks that Trump isn't that mean-spirited, so that was always going to be a difficult thing to accomplish.

@BrodieOnLinux uutils is trying to become a drop-in replacement for coreutils, so, if distros adopt it long enough from now, like a decade maybe, there might not be much difference in compatibility between them.

E: Not a lot if you expectations for compatibility are "does all things a user might reasonably observe the way that coreutils does, minus their bugs and plus some optional non-default features", I mean. They're probably already very compatible by less strict standards.

@b0rk I disagree with your assumption that terminal emulator should add more features faster. Fast innovation on the web has helped to create overwhelming and confusing designs, and it has caused websites to adopt features which no longer work. I don't doubt that it would be nice to get more people to use the terminal, but working very hard for the sole purpose of making it easier to make big innovations is risky, and it does not have to be the primary form of progress we should aspire towards.
@b0rk It might not exist. You could try asking somebody who participated in the founding of a terminal project how they chose what escape sequences to start their project with, or compare the terminfo databases of popular projects, if you're really motivated to continue this line of research and can't think of any better ideas for doing so.
@b0rk I don't think any of the things you listed relate to Input Method Editors? I know that they're very important for some non-English-speaking people, and they can be used in the terminal, and that there's Wayland and X Window System standards relating to them.
@b0rk The toybox and busybox project websites mentions what standards that they use as guidelines for what they choose to re-implement as part of their goal of being small, fast, somewhat standards-compliant reimplemntations of common shell utilities. Neither project follows any standard to the letter, though, nor does ncurses, which also documents their approach to relevant standards.