The drives should work fine, for standard blurays and self wrote disks. There are a mature cli utilities and often the gui version is just a frontend for the cli tools. It is just an optical drive otherwise.

Arch Linux Wiki : https://wiki.archlinux.org/title/Blu-ray

Check out makemkv, which has a cli option, and their forum for compatibility for 4K blurays. Newer bluray drives have additional protection for 4K if I understood correctly.

Yeah and you’d think GNU would like the recognition too.

I’d rather have a little demon than a simp

Couldn’t they just call it IMP(Image Manipulation Program)?

I have heard it used that way in the last decade I think

The feature you are going to want to look for is USB Attached SCSI (UAS) or USB Attached SCSI Protocol (UASP) support.

Try opening a new terminal. If the commands don’t work, type “export PATH=/usr/bin” not quotes and try again and fix what you did.

I must have been tired when I did that math. I’d be happy with the year as well. Just don’t use the firefox/chrome model.

If semantic versioning is:

MAJOR version when you make incompatible API changes MINOR version when you add functionality in a backward compatible manner PATCH version when you make backward compatible bug fixes

then I think that would be on like 3.77.0 or something right now. Not terrible, but honestly prefer it to be like the major upped in the new year every year. It is about 43 years old,so 43.x in 2026. Would be easier to know how old a kernel release is without looking it up.

I’d rather have screws than those clip-in covers that break or having to pry the device open like some brands of devices, ie most of the tech industry. Somewhere in the middle. Quickly being able to replace a battery easily a plus don’t get me wrong, but I don’t want it getting torn up in the process one either extreme. I am ok with it may take several minutes, but not with “can I buff this out” or “where is the tape/glue”.

dead.letter is email draft in some clients when they crash.

I don’t know. Most of the increase above appears to be win 10 users. Win 10 lost 1.09% and the percentage gain was close to evenly split between linux and win11 with a little going to MacOS.

I could see a bunch of people paying $15 to keep win 10 going , but not that much.

Awesome. Will be interesting to see the November December numbers with unpaid Win10 support ending.

I wonder why colorizing manpages like this is not default in most distros. That seems like an obvious thing to configure for end user’s quality of life.

My best guess would be that each terminal could display differently or be buggy and a “lowest common denominator” approach where it work everywhere. I know blue tends to be to dark unless I change the color to a lighter shade and the font could make a difference as well.

No

I wasn’t intending to come off confrontational, I apologize for that. I was looking at this from it sounding like you wanted any command on a system. I did find that you can colorize man. see script below for an example. As for busybox, it is a small project, so colorizing just it would be relatively easy and easy to add as a patch to a system. Not sure if that would upstream though as it is intended to work well on low memory systems among others.

#!/bin/bash

export PAGER="less -r"
export GROFF_NO_SGR=1
export LESS_TERMCAP_mb=$'\E[01;31m'
export LESS_TERMCAP_md=$'\E[01;31m'
export LESS_TERMCAP_me=$'\E[0m'
export LESS_TERMCAP_se=$'\E[0m'
export LESS_TERMCAP_so=$'\E[01;44;33m'
export LESS_TERMCAP_ue=$'\E[0m'
export LESS_TERMCAP_us=$'\E[01;32m'

man ls

Edit: it does seem that this man colorization is disabled by default.

Edit2: “export MANROFFOPT=-c” can replace “export GROFF_NO_SGR=1” to limit just man.

Edit3: source Arch Linux bbs

I am getting the feeling the you are mis-understanding than each project has their own independent implementing function and that each one would need to be rewritten. There a 10 of thousands of projects. This is not some simple, change 1 project task.

16 Color terminals didn’t really start getting used until the 90s and early 2000s. And 256 after that. A lot of software was written back then and it would take a lot to add something that might not display well because of the terminal’s color scheme and now we have color theming.

I agree, I just didn’t want to make assumptions about how newer things work with localization these days.

Not everything uses groff. A lot will have their own function or another.

Edit: I think for what you indicting you are wanting to try you’d need to either patch your shell of choice or write your own.

Edit2: If you did patch it, the best way I can think of to get something upstreamed would be to patch bash to use CTRL-Enter to automatically pipe the output to the default pager defined in BASHPAGER followed by PAGER if it doesn’t exist. Then set the BASHPAGER to your “bat” command.

Or if you are lazy you could add “-h” as an option to said help command for when --help doesn’t work. Shouldn’t take to long to to make a list with a script that runs each command to with --help and logs it all to a file though. Then just go look for the ones that don’t like it in the log. Apparently bash has a builtin command named help, so a different name is probably better then.

ls -1 $dir | while read line do echo “----------” $line --help |& >> logfile.txt done

Just search in you favorite pager for “-----” and just hit “next” key.