not consistently cycling through all windows matching class regex

[ehula]

I don't know if this is an active project, but I just stumbled on hypr-run-or-raise.

It has some issues you may be aware of:

• inconsistent results whether windows are tiles or fullscreen
• doesn't cycle through all windows matching class regex

Also, there seems to be a dependency for some sway commands (i.e. swaymsg).

Are you planning on continuing development? Would you consider making your repo a nix flake?

[jixiuf]

I don't know if this is an active project, but I just stumbled on hypr-run-or-raise.

It has some issues you may be aware of:

• inconsistent results whether windows are tiles or fullscreen

I don't undersand what's meaning of this line? Can you describe it in detail

• doesn't cycle through all windows matching class regex

this should be implements

Also, there seems to be a dependency for some sway commands (i.e. swaymsg).

swaymsg is a soft dependency, it would not be executed if you are not running sway

Are you planning on continuing development? Would you consider making your repo a nix flake?

I am planning on continuing development, but I don't known nix or flake? what should I do if it become a nix flake?

[ehula]

I don't undersand what's meaning of this line? Can you describe it in detail

Sure, I am happy to.

I am running hyprland on nixos. I have the following key binding defined:

bind = SUPER, return, exec, hypr-run-or-raise kitty kitty

Let's say I have multiple kitty windows opened on multiple workspaces and monitors. If I hit SUPER-return, a kitty window on a different monitor is focused. But, if I hit it again, nothing happens. It does not focus a different kitty.

I suspect that you need to do more testing with external monitors and also fullscreen windows. I have tried a similar tool to yours (https://github.com/knarkzel/raise). It fails when there is a target window that is fullscreen, and seems to have problems with external monitors as well.

I am planning on continuing development, but I don't known nix or flake? what should I do if it become a nix flake?

To turn your project into a Nix flake, you need to create a flake.nix file in the root of your project repository. This file describes how the flake can be used, including how to build, run, or develop the project. The flake.nix file essentially acts as a declarative, reproducible description of your project. https://nix.dev/manual/nix/2.18/command-ref/new-cli/nix3-flake