Peter Fern
Peter Fern
> can stick to your IDs if you don't use named workspaces. Keep a registry somewhere, or call hyprctl workspaces and find the ID of the workspace by name. Keeping...
> > print ids in events and add a selector like id: to explicitly specify an ID > > This probably solves most of the issues for my particular use-case...
> But I am looking for `workspaceV2` from [issue 4929](https://github.com/hyprwm/Hyprland/issues/4929). Those are events, not configuration stanzas. You can specify detault names for workspaces by ID using: ``` workspace=1,defaultName:foo workspace=2,defaultName:bar ```...
Below is the schema diff, in case it's useful ```diff --- /tmp/20.sql 2024-01-23 23:01:02.773076425 +1100 +++ /tmp/21.sql 2024-01-23 23:01:39.772200224 +1100 @@ -28,6 +28,8 @@ CREATE TABLE tag_link (tag_id integer, media_id...
Would such an exported filesystem allow playback status sync though? I suspect not, right? That's the only reason I use the add-on right now since all my Kodi usage is...
Still an issue on v0.288.1, based on the error message, seems like the current working directory just needs to be set to the .devcontainer path, or an unqualified Dockerfile needs...
Still desirable for consistency.
What if pool and dataset names overlap? I suspect this probably needs to be a separate flag, but could be convinced otherwise.
What if I want to exclude the dataset `rpool`, but not the pool `rpool`?
The top-level dataset name and the pool name cannot be differentiated - there are no slashes, and dataset names are never preceeded by a slash: ``` $ zfs list -o...