MaskedNybbles

deleted by creator

deleted by creator

Not that I particularly want to get involved—I do also like inxi—but you can launch Info Center (kinfocenter) from krunner, the application menu, or under About this System in System Settings to get a good amount of this information and more.

For anyone else reading, I stupidly deleted my comment where I asked more-or-less the following (sorry):

This might be a stupid question, as I am unfamiliar with GUIX/Nix and am unlikely to be able to help, but what happens when you try to run LXQt from the CLI?

deleted by creator

I understand what you mean, and tend to agree, although I had some success with zypper se -d '/CD.*burn/'—'CD.*(burn)|(writer)' produced more results than I’d like—for your example. It also appears apt-cache search already searches descriptions by default.

Looking at results for just /CD/—amid the many poor results—it seems my earlier search missed some due to differing word usage, such as recording rather than burning, and whatnot.

According to the man-page at https://manpages.debian.org/buster/apt/apt.8.en.html and the linked https://manpages.debian.org/buster/manpages/regex.7.en.html, you should be able to use regex like apt search '(-|^)vim(-|$)' to get vim as either whole name or related packages with containing vim with leading or trailing dashes, or apt search '^vim' to get any beginning with vim—in case that helps. zypper lets me do essentially that with zypper se '/(-|^)vim(-|$)/' and such.