count0

... Which means that businesses are making 'too much' money on top to sink into such endeavors, no?

Thank you!

This is what I came up with.

• a script that does what you need, and reads a kinda 'config file' which Konsole instance/window/session to use
• another script that saves the current session into that config file

So you'd save the scripts somewhere you like, and run the useThisSession one in the session you'd like to be the target.

Then, you can run / bind to a shortcut / ... the runCommand script, and it will show, raise, set Session, and run the command on the target saved earlier.

useThisSession.sh:

#!/bin/bash
# useThisSession

echo MYCMD_SERVICE=$KONSOLE_DBUS_SERVICE > ~/.config/mycmdrc
echo MYCMD_SESSION=${KONSOLE_DBUS_SESSION#/Sessions/} >> ~/.config/mycmdrc
echo MYCMD_WINDOW=${KONSOLE_DBUS_WINDOW#/Windows/} >> ~/.config/mycmdrc

runCommand.sh:

#!/bin/bash
# runCommand

. ~/.config/mycmdrc

qdbus $MYCMD_SERVICE /konsole/MainWindow_$MYCMD_WINDOW showNormal
qdbus $MYCMD_SERVICE /konsole/MainWindow_$MYCMD_WINDOW raise
qdbus $MYCMD_SERVICE /Windows/$MYCMD_WINDOW setCurrentSession $MYCMD_SESSION
qdbus $KONSOLE_DBUS_SERVICE /Sessions/$MYCMD_SESSION runCommand "echo cmd"

For testing purposes, I'm using "echo cmd" instead of '!!' (note the different type of quotes) to not cause any... unintended... executions.

Running qdbus $MYCMD_SERVICE /konsole/MainWindow_$MYCMD_WINDOW will show you all methods available on the Window, eg, so you can pick&choose from those if you want different behaviour from show (& un-minimize) and raise.

EDIT: syntax adjusted to work in 'regular' bash

Soo... If we could figure out how to do the first one via DBus/from the command line, you could put both in a script and bind that to a (global or so) shortcut, and be set. (?)

What qdbus command line exactly are you using to post input to the shell within Konsole?

I'll have a look later when I'm at my desktop again (and hopefully will remember).

For the vendor (non-)consent thing - Consent-O-Matic provides an appropriate framework.

(Whether such a side would even care about the preference/consent is another matter entirely - I'd suggest a throwaway browser identity and cookie auto delete for a start, anyway.)

Creating rules has a bit of a learning curve the first three or seven times, but I find that more interesting to do than go through a hostile/dark pattern cookie dialog or such the third time.

Hm, maybe the appropriate functionality from CoM could be re-wrapped as a TamperMonkey module...

Web automation for the masses 😱

Great writeup, thank you so much for sharing!

Nothing more frustrating than googling an issue and (only) finding forum threads ending in "nvm it works now" 😬

What exactly does it do / which problem(s) does it solve? Its website reads kinda intentionally vague to me.

Regarding weather: I just love the no-frills at-a-glance presentation of the AF Weather Widget

How does writing things down help when I don't remember to read them back...?

I "tried" to use XMPP/Jabber in its heyday, but in my experience (& memory) it never got to the point to have a "critical mass" of community (I felt to be part of / want to be part of).

Fediverse/Lemmy has this critical mass at least since some weeks now - unless too many of those users decide to leave for another place, I'm happy here no matter what other things get hyped in a given week.

Back in Jabber's day, I would have liked to see it develop some communities as they did - and still do! - exist on IRC, but that simply never happened (with one I would both be interested in and could find).