One thing that's been bugging me since I've started using Worm as my primary WM is occasionally when I click something on a window, it starts to drag the window around.

I eventually narrowed it down to specifically when I do a rapid single-click without moving my pointer, and after a bit of digging found the code that causes it:

https://github.com/codic12/worm/blob/76389eec58cb1490e0702e89680ff1e370849ce8/src/events/buttonpress.nim#L76-L77

Is this intended? If so, would it be possible to gate it behind a setting somewhere?

I've played with deleting the lines of code and it just makes using the WM feel way less "glitchy", as with it included it's far too easy for me to accidentally trigger a drag.

1. Allow the user to change the mouse mod key used to resize/move windows (similar to bspwm's bspc config pointer_modifier)
2. Focus windows when hovering over them (similar to bspwm's bspc config focus_follows_pointer)
3. Cycle through windows using something like Alt + Tab

When I tried to take a float object (window) I can't make it static again

I'm sure its a user error.

here is my sxhkdrc file.

Restart worm

super + ctrl + r worm

Open terminal kitty

super + Return kitty

#ctrl + space

ulauncher &

super + d ulauncher &

super + b brave &

Quit worm

ctrl + alt + q pkill worm

Close app

super + q wormc close-active-client

Maximize app

super + f wormc maximize-active-client

Minimize app

super + h wormc minimize-active-client

Tags

super + {_, shift + } {1-9} wormc {switch,move-active}-tag {1-9}

Set master windows

super + m wormc master-active

Float a window

super + shift + space wormc float-active

For users largely using worm as a floating WM like myself, the button styling and rendering are okay, but not great. Typically I'd like my buttons to change on hover (to indicate that if I click, I will be clicking them and not the space surrounding them) and with everything else having active and inactive coloration, it'd be nice if the buttons could have the same. With the default config's coloration, for example, a black button disappears on a foreground window but looks perfect on a background window.

Some thought needs to be put into how to achieve this however -- ideally you could just give SVG elements a class like worm-fill or worm-stroke and worm could change their colors dynamically, but looking at pixie it doesn't look like this kind of behavior is exposed in any way.

It's still probably technically doable -- just separate out a codepath for SVG files, parse the XML, find all elements with class worm-{fill,stroke}, and set their fill or stroke value or whatever the case may be to the selected color, then render back to text and pass to decodeSvg -- but it wouldn't be particularly clean.

Perhaps worth looking into upstream contributions to pixie's SVG support? SVGs in the browser support styling, with CSS being able to set certain values (including fill and stroke), but since Pixie isn't a browser it does seem like there possibly ought to be a way to pass styles in when rendering an SVG that's not CSS.

https://github.com/codic12/worm/commit/13cbcf96b8de25eb77db6e8e1e03c83f20a8697a

You can use an interactive rebase to remove target folder from repo.

Or use the following command in project root.

git filter-branch --tree-filter 'rm -f target' HEAD

Do note that this will change commit hashes and you'll need to force push once ( git push -f ), but I don't see much issue in that since there aren't any public forks.

Requesting this since the target files are still in git history and that pulls up the size when cloning.

Closes #52.

Turns out that the section I found in i3's source code when first diagnosing the issue was exactly what I needed.

Also, it turns out xprop was also broken by WM_STATE not being set! Go figure.

It's not exactly as clean as the rest of your XChangeProperty calls since WM_STATE was neither in netAtoms or ipcAtoms, but I wasn't sure where I should put a new atom so I just interned it inline.

Hi, just found about this project and I really like it :100:. I was skimming through the code and noticed several simple things that could be improved. No new functionality, just some cleaner code.

Feel free to nitpick stylistic choices. Thanks for the awesome project!

{close,maximize,minimize}-path->{close,maximize,minimize}-{active,inactive}-path

I chose to go ahead and set up a ButtonState enum and change the config options to enum indexed arrays, since there's discussion in #57 about extending the possible states further.

Note that while I haven't implemented it in this PR in the interest of doing one thing at a time, it may be reasonable to get rid of ButtonState and instead have just a FocusState (or focused boolean value, if you're not concerned about the type system insurance from using a dedicated enum I suppose) on each client and moving every active/inactive switched value to be an array[FocusState, t] where t is their type. Then when adding hover states you could just have the button paths' config types be array[FocusState, array[HoverState, string]].

Sorry if there is any mistake on my side, but I can't compile worm and it shows an error while doing it.

Here is the full output when running nimble build -d:release --gc:arc:

  Verifying dependencies for [email protected]
      Info: Dependency on x11@any version already satisfied
  Verifying dependencies for [email protected]
   Building worm/wormc using c backend
   Building worm/worm using c backend
/home/wc/.cache/nim/worm_r/@mworm.nim.c: In function ‘getProperty__9aiI5srh3lf4yinTF7HA9aGQ’:
/home/wc/.cache/nim/worm_r/@mworm.nim.c:3022:26: error: incompatible types when assigning to type ‘tyObject_Option__hcmjwL9c5ECYpHnVevXHwEQ’ from type ‘tyObject_Option__9bcZreTqxpOXg5u4xcKsUEw’
 3022 |                 result = colontmpD__2;
      |                          ^~~~~~~~~~~~
/home/wc/.cache/nim/worm_r/@mworm.nim.c: In function ‘handleUnmapNotify__IBNx9c2pqwde9cI9bE9afvcRpw’:
/home/wc/.cache/nim/worm_r/@mworm.nim.c:4423:27: error: incompatible types when assigning to type ‘tyObject_Option__hcmjwL9c5ECYpHnVevXHwEQ’ from type ‘tyObject_Option__9bcZreTqxpOXg5u4xcKsUEw’
 4423 |         (*self).focused = T12_;
      |                           ^~~~
/home/wc/.cache/nim/worm_r/@mworm.nim.c: In function ‘handleDestroyNotify__UtpRh9a9bdEb3vV3vfdWHAsw’:
/home/wc/.cache/nim/worm_r/@mworm.nim.c:4509:27: error: incompatible types when assigning to type ‘tyObject_Option__hcmjwL9c5ECYpHnVevXHwEQ’ from type ‘tyObject_Option__9bcZreTqxpOXg5u4xcKsUEw’
 4509 |         (*self).focused = T12_;
      |                           ^~~~
Error: execution of an external compiler program 'gcc -c  -w -fmax-errors=3 -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -D_FORTIFY_SOURCE=2 -O3 -fno-strict-aliasing -fno-ident   -I/usr/lib/nim -I/home/wc/tmp/worm/src -o /home/wc/.cache/nim/worm_r/@mworm.nim.c.o /home/wc/.cache/nim/worm_r/@mworm.nim.c' failed with exit code: 1


       Tip: 5 messages have been suppressed, use --verbose to show them.
     Error: Build failed for package: worm
        ... Execution failed with exit code 1
        ... Command: /usr/bin/nim c --colors:on --noNimblePath -d:release --gc:arc -d:NimblePkgVersion=0.1.0 --path:/home/wc/.nimble/pkgs/x11-1.1 --hints:off -o:/home/wc/tmp/worm/worm /home/wc/tmp/worm/src/worm.nim

Master-stack is a simple algorithm:

• 1 window takes all of the screen
• 2 windows, each takes half vertically
• Else, on the left 1 window (100% height, 50% width) on the right the rest, each having 50% horizontal and some amount of vertical space (which is the same for all on the right)

I have tried using git repo and copying over the binaries to /usr/bin/ and chmod +x on both of them.

I have tried using yay -S worm-git using xessions for sddm and lightdm. When I click on worm in the login manager I can only move the cursor.

I have setup all the config files: /home/nixfreak/.config/worm ├── polybar │   └── config.ini ├── rc └── sxhkdrc

I have setup the same config file as in the examples to rc file.

Nothing works , also I had to remove nim 1.6.1 version and devel because the build using yay wanted to install only 1.4. I nim on a daily basis and nimble.

I am using an archinux x86-64 Linux chaosArch 5.17.4-arch1-1 #1 SMP PREEMPT Wed, 20 Apr 2022 18:29:28 +0000 x86_64 GNU/Linux I have nimc version Nim Compiler Version 1.6.6 [Linux: amd64] Compiled at 2022-05-05 Copyright (c) 2006-2021 by Andreas Rumpf

git hash: 0565a70eab02122ce278b98181c7d1170870865c active boot switches: -d:release

If I could debug this why the executable isn't working I would , just no clue where to start.

os: void linux nim ver: 1.6.0

problem:

when ever i run the nim build command, i get alot of errors and have no idea what they mean, ive tried to read them but it looks like nim is trying to find files that arent there?

error(sorry for the block of text) :

/usr/lib/gcc/x86_64-unknown-linux-gnu/12.2/include/avxintrin.h: In function 'fillUnsafeAvx_wm_780': /usr/lib/gcc/x86_64-unknown-linux-gnu/12.2/include/avxintrin.h:1326:1: error: inlining failed in call to 'always_inline' '_mm256_set1_epi32': target specific option mismatch 1326 | _mm256_set1_epi32 (int __A) | ^~~~~~~~~~~~~~~~~ /home/pugn/.cache/nim/worm_r/@mwm.nim.c:2452:20: note: called from here 2452 | colorVec = _mm256_set1_epi32(LOC5.dest); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ /usr/lib/gcc/x86_64-unknown-linux-gnu/12.2/include/avxintrin.h:921:1: error: inlining failed in call to 'always_inline' '_mm256_store_si256': target specific option mismatch 921 | _mm256_store_si256 (__m256i __P, __m256i __A) | ^~~~~~~~~~~~~~~~~~ /home/pugn/.cache/nim/worm_r/@mwm.nim.c:2463:33: note: called from here 2463 | _mm256_store_si256(((void) (p)), colorVec); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /usr/lib/gcc/x86_64-unknown-linux-gnu/12.2/include/avxintrin.h:1326:1: error: inlining failed in call to 'always_inline' '_mm256_set1_epi32': target specific option mismatch 1326 | _mm256_set1_epi32 (int __A) | ^~~~~~~~~~~~~~~~~ /home/pugn/.cache/nim/worm_r/@mwm.nim.c:2452:20: note: called from here 2452 | colorVec = _mm256_set1_epi32(LOC5.dest); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated due to -fmax-errors=3. Error: execution of an external compiler program 'gcc -c -w -fmax-errors=3 -O3 -fno-strict-aliasing -fno-ident -I/home/pugn/.choosenim/toolchains/nim-1.6.0/lib -I/home/pugn/worm/src -o /home/pugn/.cache/nim/worm_r/@mwm.nim.c.o /home/pugn/.cache/nim/worm_r/@mwm.nim.c' failed with exit code: 1

   Tip: 35 messages have been suppressed, use --verbose to show them.
 Error: Build failed for package: worm
    ... Execution failed with exit code 1
    ... Command: /home/pugn/.nimble/bin/nim c --colors:on --noNimblePath -d:release -d:NimblePkgVersion=0.2.5 --path:/home/pugn/.nimble/pkgs/x11-1.1 --path:/home/pugn/.nimble/pkgs/pixie-5.0.4 --path:/home/pugn/.nimble/pkgs/vmath-1.2.0 --path:/home/pugn/.nimble/pkgs/chroma-0.2.7 --path:/home/pugn/.nimble/pkgs/zippy-0.10.5 --path:/home/pugn/.nimble/pkgs/flatty-0.3.4 --path:/home/pugn/.nimble/pkgs/nimsimd-1.2.2 --path:/home/pugn/.nimble/pkgs/bumpy-1.1.1 --path:/home/pugn/.nimble/pkgs/vmath-1.2.0 --path:/home/pugn/.nimble/pkgs/regex-0.20.1 --path:/home/pugn/.nimble/pkgs/unicodedb-0.11.2 --hints:off -o:/home/pugn/worm/worm /home/pugn/worm/src/worm.nim

any help would be great! and thanks!

Documented Behaviour: focus-mode(int)` : Sets the focus mode. 1: is focus-follows-click (like Microsoft Windows). 2: is the traditional X11 focus-follows-mouse.

Observed Behaviour: wormc focus-mode 2 does not result in activation/focus of inactive client on mouse hover. The same situation is observed in both tile and float modes.

Currently when a client in tile mode is maximized there is no way to minimize it.

In most window managers pressing the maximize keybind when the active client is maximized results in minimization of the active client.

A toggle to maximize/minimize the active client would be very convenient.

It should be possible to use XInternAtoms function instead of XInternAtom in getNetAtoms() and getNetAtoms() functions from worm/atoms.nim to speed it up.

I imagine this will only ever pop up when developing on worm for most users, but when working on #70 I spent a while attempting to debug why the new config options weren't working, and it was due to my rcfile using my system wormc, rather than ~/devel/worm/wormc.

That said, it would also be of benefit to reduce down configuration to a "single source of truth" -- currently to add a configuration option you:

1. add a new IPC atom in src/atoms.nim
2. add it to the Config type in src/types.nim
3. implement boilerplate for the option in src/wormc.nim
4. implement the setter for the option in src/events/clientmessage.nim
5. and finally, you can actually use the configuration option in your code

You could get rid of 1 and 3 in a single step (as well as what I mention above, avoiding errors from an easy-to-make mistake) by simply having wormc take its input and send it directly to worm which handles it in its entirety.

Example on sxhkdrc:

super + {Left, Right}
       wormc switch-tag {-1,+1} 

It consists to go to the actualworkspace +1 or -1 (so it depends on on which workspace you are). The same thing with move-active-tag.