Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Just annotations of little "how to's", so I know I can find how to do something I've already done when I need to do it again, in case I don't remember anymore, which is not unlikely. Hopefully they can be useful to others, but I can't guarantee that it will work, or that it won't even make things worse.
"C" stuff will be much faster than scripts, so sometimes even a "dumb" use of a C program will be more optimal (take less time) than trying to sort out a more minimal task for the C program with bash.
Like
Code:
grep -h -m 1 THING-TO-GREP index_*
versus
Code:
< ... some bash-script logic that tries to figure out the most likely index_NNNN files
so grep has only to work with a few, not all ... >
grep
(Or anywhere using lxqt-notificationd, like in otherwise pure Openbox, which happens to be my case)
The "proper" way would be to have it always explicitly setting something else with "-a," but apparently one can emulate the title-less implementation of other notification daemons with an wrap-around script like this:
Code:
#!/bin/bash
if [[ ! "${@}" =~ "-a " ]] ; then
/usr/bin/notify-send -a ""
I eventually became somewhat youtube-dependent for media consumption, but I don't quite like the natural flow of youtube's algorithms' "play next" suggestions, which are probably even minimally bearable when I'm logged in.
So it can be interesting to have a shuffle of a series of chosen playlists to be played when we're doing whatever. The arguably best-ish way for doing it is to save YT playlists (the list of URLs, not the video files themselves) on disk, then do some bash/sed...
Having something like ~/.cache as a tmpfs, and setting up xsession-errors to be there.
Of course, everything will be lost in the next reboot, and, depending on for how long the session goes, it may be too big for the set-up tmpfs space as well, for the people who use their PCs on a never-really-turn-off/reboot kind of regimen.
If one needs eventually something saved from session to session, maybe one can have a daemon that will tail/pipe the xsession-errors to some...
It's likely there is a more proper way of doing it, not needing to uninstall, but I just lost my patience at this point.
Maybe still needs the non-GTK versions, a "neutral" one and a kde and a qt5 one, I can't really tell. I was about to uninstall them all, but occurred to me to try to uninstall just the gtk one, and voilá, I had kdialog on chrome-based-browsers again.
Why can't things be set by text files or environment variables with sane standards?...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
