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.
In GTK3 they came up with the notion that if you have a really long file list, and you want to get to the end of the list by pressing the "end" key, you don't really want to immediatelly jump down there to the end, instead you'd want a few seconds of an animation of the file list rolling up. Which ironically contrasts somewhat with their scrollbar innovation, of instantly moving the view to the "proportional" point on the scrollbar, rather than a click out of the scroller being...
Posted 12-04-2023 at 12:30 PM bythe dsc (linux-related notes)
Updated 12-06-2023 at 01:30 PM bythe dsc
I had the HISTCONTROL options set correctly for that for a while ("ignoreboth:erasedups" -- the first ignores duplicates and command lines starting with a space, and erasedups would "move" a command repeated exactly to the last entry when repeated), and yet it wasn't working, I had duplicates all over.
I had just devised a script-daemon that would do the same thing in a less-than-native manner, when I decided to search a little bit more about it before just "saving"...
Have kdialog preceeded by (or succeeded after an "&" if the context allows it, and if it's preferable for some reason) a loop that has wmctrl "grepping"/activating" the unique name of the kdialog window, followed by xdotool resizing it, and breaking the loop.
Code:
( while true ; do
sleep 0.2 # reduces CPU load if the loop never breaks for some reason
wmctrl -a "relevant and ideally unique title for kdialog window" &&
Was just randomly trying to see if you could have different mouse-bindings association for double and single click on the same context, and decided to web-search a bit after it failed, "maybe there's some syntax trick or something," I thought.
Instead I found an old post in this forum saying that, in completely different circumstances (out of window-management associations, seems to me), Openbox requires a triple click where other/actual DEs would require a double one....
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...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
