view the rest of the comments
Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
If you don't find such a setting, you can try writing a script that checks if it's running already (e.g. with
pgrep
), activates the window if found (no idea how to do that in Wayland properly) and launches a new instance otherwise. Then use a custom.desktop
launcher for Konsole.Thanks for your reply :) I might look into it if I don't find anything easier
Here's a KDE-specific script with
kdotool
(Wayland always needs custom solutions for simple things):sweet! thank you so much!
Well, that's exactly what I did. My point was rather that there's no single consistent way to do this across different DEs with different Wayland implementations - and that's supposedly considered a feature from Wayland design's perspective.
How have you read the part you quoted without reading the package name right in front of it?