From Roland Fredenhagen to ~soywod/himalaya-lib
--- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index ff266af..414f512 100644 --- a/README.md +++ b/README.md @@ -105,7 +105,7 @@ $ cargo test ## Contributing If you find a bug, feel free to open an issue at [~soywod/himalaya-lib](https://todo.sr.ht/~soywod/himalaya-lib). [~soywod/himalaya-lib](https://todo.sr.ht/~soywod/himalaya).[message trimmed]
From to ~tsdh/public-inbox
Hi Tassilo, > Tassilo Horn <tsdh@gnu.org> writes: > Oh, well, I just made the new get-windows-as-json command the first one > making use of that feature and released swayr-0.24.0-beta.0 with it. > Give it a try. > > Bye, > Tassilo Just tried it, and AFAICT it works perfectly. Thank you a lot!
From to ~tsdh/public-inbox
Hi Tassilo, > > I think the only way is to convince the swayipc author to make all the > > IPC structs/enums derive Serialize > > I created an Issue and PR, so hopefully they will add it. > https://github.com/JayceFayne/swayipc-rs/pull/43 They merged it, and released swayipc_types 1.3.0 including the change: https://docs.rs/swayipc-types/1.3.0/swayipc_types/struct.Node.html#impl-Serialize-for-Node . Bye, Roland
From to ~tsdh/public-inbox
Hi Tassilo, > I think the only way is to convince the swayipc author to make all the > IPC structs/enums derive Serialize I created an Issue and PR, so hopefully they will add it. https://github.com/JayceFayne/swayipc-rs/pull/43 > but I guess there are reasons why > they don't (like binary size or so). Since the only open issue there is > yours, you might want to file another wishlist item explaining in kind > words why it would be a good idea. :-) In case they want to keep binary size low, it could just be put behind a feature flag (I offered to do so, so I'll see what they say).
From to ~tsdh/public-inbox
Hi Tassilo, > Ok, I'll implement a new command "swayr get-tree" which is like "swaymsg > -t get_tree" except that it enhances Nodes with a swayr_icon and > swayr_type. That should make it easy enough to filter out windows with > jq, right? That would be great, wondering if something like an option to `--flatten` would be possible, but without a filter that would just lead to problems as it is unclear what to do with the sub nodes of containers and workspaces. And it should be possible to flatten it using the `recurse` in jq: ```sh
From Roland Fredenhagen to ~tsdh/public-inbox
Hi 17.11.2022 13:29:48 Tassilo Horn <tsdh@gnu.org>: > me@modprog.de writes: > > Hi! > >> I want to access icon information for all open windows. As swayr has >> this feature already implemented, it would be great to be able to >> access it. I can see multiple ways to implement this that would work >> for me (ordered most useful to least usable): >>
From Roland Fredenhagen to ~tsdh/public-inbox
--- On my system there were applications that only installed an icon for 128x128. E.g. wezterm: https://archlinux.org/packages/community/x86_64/wezterm/files/ swayr/src/config.rs | 1 + 1 file changed, 1 insertion(+) diff --git a/swayr/src/config.rs b/swayr/src/config.rs index 816f972..4a759a0 100644 --- a/swayr/src/config.rs +++ b/swayr/src/config.rs @@ -297,6 +297,7 @@ impl Default for Format { urgency_end: Some("</span>".to_string()), icon_dirs: Some(vec![ [message trimmed]