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.
Probably can be easily adapted to notifications handled by any other notification daemon, requiring one to see what they're called with xprop or something:
Code:
notify-send "bogus" "$(ls /usr/bin)" & xprop
Then click on the notification. "lxqt-notificationd" is the "_NET_WM_NAME(UTF8_STRING)" but also a lot of other things, I'm not sure which one is...
I'm using MKVToolNix GUI v64.0.0 ('Too Much') 64-bit on Ubuntu MATE 22.04 amd64 desktop, and the GUI is broken. I mean, it's just not working right. I'll include a picture. I don't know if I have it use it as command line or what, but this is weird. I've tried reinstalling
Posted 08-05-2023 at 08:17 PM bythe dsc (linux-related notes)
Updated 08-17-2023 at 09:43 AM bythe dsc
Code:
lastarg=${@:$#}
# options should come all together on the last argument, such as:
# $./script.sh file1.foo file2.bar --scr-opts:optA,optC,opt3,opt2
echo "${@}" | sed 's/--scr-opts:.*//' | sed '/^\s*$/d' > /dev/shm/scripttmpfilelistorwhatever$$
# that strips the files (or something else coming before the options) and adds to a temp file.
# The second sed deletes empty lines, for some reason. I guess sometimes they may end up there somehow,
I kind of use it to a significant degree as a "file manager for images," so more often than not I'm on the file pane, much more so than the folder pane, but apparently there's no way to change the default focus, besides eventually changing the source code somehow and compiling it. Preferably with the default-focus-here-or-there being an option, so everyone can have it the way they chose. But for now the best I can do is having this xdotool wrap-around script on $PATH, named geeqie as well:...
Maybe one can get totally used to it, but the in-between/trying out can be annoyingly troublesome.
Despite not having a bug found on tint2 (unhidden auto-hiding panels being covered/"popping-under" always-on-top windows, instead of above), it doesn't feel the same in a significant way, but I could get over it.
Unfortunately, besides that, the auto-hide mode seems to behave erratically. Not only delays a bit too much to show up, but often seems to just not...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
