#17 Password Manager 10 months ago

Comment by ~brocellous on ~brocellous/wlrctl

You should be able to by including literal tab character in the argument. I suggest you use wtype for keyboard input tasks though, it's more flexible with its inputs and easier to use.

REPORTED RESOLVED CLOSED

#15 Curly braces swapped with Brackes 1 year, 4 months ago

Comment by ~brocellous on ~brocellous/wlrctl

REPORTED RESOLVED CLOSED

#15 Curly braces swapped with Brackes 1 year, 4 months ago

Comment by ~brocellous on ~brocellous/wlrctl

Should be resolved in 0.2.2

#15 Curly braces swapped with Brackes 1 year, 4 months ago

Comment by ~brocellous on ~brocellous/wlrctl

I believe that was fixed in 916413b163a0 but I haven't made a release in ages. I guess I could make one.

#14 Build dependencies xkbcommon already installed 1 year, 10 months ago

Comment by ~brocellous on ~brocellous/wlrctl

You don't appear to be using your distribution provided pkg-config. It seems like this uses a different pcfile prefix: https://github.com/Homebrew/linuxbrew-core/issues/2306.

REPORTED RESOLVED NOT_OUR_BUG

#7 wlctrl keyboard type replaces [] with {} and vice versa 2 years ago

Comment by ~brocellous on ~brocellous/wlrctl

Yeah woops. Fixed.

REPORTED RESOLVED FIXED

#5 wlrctl keyboard type "hello world" fails with "Unsupported modifier: ..." 2 years ago

Comment by ~brocellous on ~brocellous/wlrctl

Should be fixed.

REPORTED RESOLVED FIXED

#11 [Feature] listen to window/toplevel events 2 years ago

Comment by ~brocellous on ~brocellous/wlrctl

Yeah "list" is intentionally undocumented. I only use it in the zsh completions to offer relevant app_ids and titles for completion. It could be documented if I decide to pick an output format and stick with it.

Something like "wlrctl window watch" that would just print stuff thats happening could be good.

#10 [Feature]: Add id to wlrctl 2 years ago

Comment by ~brocellous on ~brocellous/wlrctl

I think this would be neat, but it's not easily supported by the protocol. FTM is intended to be used in a continuous way, so the client application can distinguish toplevels by their object ids and there is no issue.

For two different wayland clients (i.e. two invocations of wlrctl), there is no guaranteed event order or persistent uniquely identifying info communicated by the compositor that could be used to make this work. I'll leave this open for now in case I missed something, but I don't know if it even would be a good idea to modify the protocol to support this use case even if that could be easily done.

#9 [Feature request] Support for window layering 3 years ago

Comment by ~brocellous on ~brocellous/wlrctl

Foreign-toplevel doesn't have anything like that. Mako's layer is a layer-shell thing, and foreign-toplevel only deals with toplevel windows – it isn't able to set the layer of layer-shell surfaces. Activating a window with foreign-toplevel will usually bring it to the front, though.

REPORTED RESOLVED WONT_FIX