adashoelace / hadlock Goto Github PK

The workflow test.yml is referencing action actions/checkout using references v1. However this reference is missing the commit a6747255bd19d7a757dbdda8c654a9f84db19839 which may contain fix to the some vulnerability.
The vulnerability fix that is missing by actions version could be related to:
(1) CVE fix
(2) upgrade of vulnerable dependency
(3) fix to secret leak and others.
Please consider to update the reference to the action.

Instead of having to compile code, please consider releasing binaries for Linux and macOS with checksums.

** How to install
Hi @AdaShoelace :) finally tried today the install guide but coming from stuff like awesomewm, bspwm... it seems more complicated like put the hadlock binary alone in /usr/local/bin seems not enough to launch it from a tty.
I probably miss some steps too.
if may be you can had a how to put that in the list of the ui when you log on, (tried in .xinitrc but not enough).
It can be easily scripted too so if you don't get the time the both I can make the script after a detailled how to I think.

Also few options which can be cool too:

• Magnifier layout (yeah I asked on reddit ;) )
• The possibility to bring temporary a app from another workspace to the focused one, (eg: firefox on #3, I'm on the #2 workspace which is code with a shortcut, I can import the content of the #3 into the #2 until I really switch to another workplace.
• A screen recorder ?
• Split config file into miltuple file like keybinding.ron, theming.ron (apps choice like terminal...), modules.ron (which can used by polybar...) ... to avoir getting a too much bugger config file.
• customize the workspace numbers with icons instead of numbers

Ty, Hk

When you switch tags/desks, the previously focused window is not active any longer. Actually, only the root window seems to be in focus. I think this could be related to the cursor position being centered each time you switch tags.

Hadlock should be able reload the config if the config file is modified.
This means that every change change in the config file should be applied without restart of Hadlock or require to close any other application.

Suggested method:
What the config file provided upon start using inotify and reconfigure Hadlock (during runtime) if an event indicating change to the config file is received.

In the event of a crashing application the window manager is not notified of the unmapping of the window and can therefor not delete the corresponding WindowWrapper.

This in turn leads to 'ghost windows' that can not be interacted with hence can not be deleted manually.
These ghost windows will cause the different layouts to behave as if they are still there, formatting existing windows in an unintended way and allocating screen space just to waste it.

Describe the bug
Using --locked flag with cargo build fails because Cargo.lock is not up-to-date.

error: Cargo.lock needs to be updated but --locked was passed to prevent this
If you want to try to generate the lock file without accessing the network, use the --offline flag.

Usage of --locked flag is important for the AUR package's reproducibility.

(I also recommend you to release a new version after updating the Cargo.lock file)

To Reproduce

1. Checkout the repository.
2. Run any cargo command with --locked flag. (e.g. cargo build --locked)

Expected behavior
Successful build.

System Info

• OS: Arch Linux
• Rust: 1.50.0-nightly

Additional context
You should update the Cargo.lock file for solving this issue. Please use cargo build command and commit the updated Cargo.lock file.

Describe the bug
If a window set it's state to hidden on "DestroyNotify" it will minimize to the system tray but leave behind the logical window (WindowWrapper) and still allocate space on the desktop.

To Reproduce
Open eg Discord and kill (using eg default binding mod + shift + q

Expected behavior
Window will be unmapped and the space it used to allocate on the desktop will no be available for other windows.
The remaining, mapped windows on in the workspace will automatically reorder and utilize the space the now unmapped window used to allocate (given that a tiling layout is used).

Screenshots

Desktop (please complete the following information):

• OS: Manjaro
• Version v1.0.6

Hi,
I'm a Rust developer who maintains AUR packages in his spare time. I created the following packages for the installation of hadlock on Arch Linux and other distributions that support installing packages from AUR:

• hadlock (builds from source)
• hadlock-git (VCS/development package)
• hadlock-bin (installs the latest binary)

Installation can be made simply by using an AUR helper such as yay. (e.g: yay -S hadlock)

Feel free to update the documentation regarding to the AUR packages and installation. (I would propose a PR if requested)

Take care,
orhun.

You should consider adding the Cargo.lock file as stated here in the .gitignore.

See: https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries

It would be cool if you could configure the window manager using Rust similar to XMonad

A user should be able to configure their own keybindings in such a way that they can choose between super and Alt as their mod key and pair it with any alpha numerical to perform any supported action.
A user shall also be able to configure their own keybindings such that they can run scripts for eg increasing/decreasing audio volume and screen brightness with the key combination of their choice.

When you set superKey to mod1, it seems to conflict or otherwise mess with, for instance, a terminal's readline bindings.