Eric Engestrom

Added a commit to move the example code to `examples/tree.py`, and changed the `$HOME` to `.` as it should be a smaller folder to list (likely will be the textual...

Actually `examples/code_browser.py` already covers the use of `DirectoryTree`, so I've replaced everything in this PR with just deleting that code :upside_down_face:

Just pointing out that there's a wayland protocol for this here: https://github.com/swaywm/wlr-protocols/pull/25 A CLI implementation is available here: https://github.com/bugaevc/wl-clipboard Hopefully it shouldn't be too hard to use this in ClipIt...

No worries about the mixup with #250/#253, it happens :slightly_smiling_face: Yeah, you're right that "everything is a layer in the end"; `translation driver` sounds good :+1:

I think you'll be interested in [nwggrid](https://github.com/nwg-piotr/nwg-launchers) which does that; easier than adding a completely different feature to this project :wink:

@Tak #2734 is about links *in Tusky* staying in the app instead of opening in the browser. This issue here is about links *anywhere outside of Tusky* being opened in...

@Tak could you reopen this issue since it was marked as a duplicate by mistake?

If I manage to provide the code to do this automatically (ie. "run this script to update the list before making a new release", perhaps even called from your existing...

Automatically updating this from an external source would not stop people from asking for their own domain to be added, but it would allow us to say "this is managed...

The "share to tusky" to open a link in tusky could be an intermediate step, but I don't know if it's really a workflow that enough users will expect for...