Worm - a floating, tag based window manager

Would love to, don’t know how to contact him

Mastodon maybe;
https://distrotoot.com/about

1 Like

no, not required. i read through the earlier posts when you were contemplating on using it. (js)

yeah, that was an idea as an extension language

v0.1 is tagged and mostly ready! https://github.com/codic12/worm/tree/v0.1, just a little bit of documentation to go. @moson if you want, you can create an aur package for this version now.

4 Likes

Nice. Could you use tags like v0.1.0 in github for the versioning?
Example: https://github.com/Jguer/yay/tags

You can easily do this by just adding a release (“Releases” → “Draft new release”) in Github…

3 Likes

changed! https://github.com/codic12/worm/tree/v0.1.0

1 Like

Seems you created a separate branch, not a tag (or release+tag) :wink:

oh, sorry, not very good with git!
release: https://github.com/codic12/worm/releases/tag/v0.1.0

3 Likes

Perfect :+1:

edit

AUR package is published. Here we go:

https://aur.archlinux.org/packages/worm/

6 Likes

two doubts:

how to make the below line work

#~/.config/worm/sxhjd
super + {p,w,x,s}
	~/.config/qtile/rofi/bin/{launcher,windows,powermenu,screenshot}

secondly, what is the path needed for jgmenu_run. i guess, it is ~/.config/worm/

additionally, is it possible to provide polybar, rofi, etc as optional dependencies for installing worm.

#~/.config/worm/sxhjd
super + {p,w,x,s}
	~/.config/qtile/rofi/bin/{launcher,windows,powermenu,screenshot}

not a worm thing but a sxhkd thing, put the file in ~/.config/sxhkd/sxhkdrc…

you can put it anywhere. you don’t need it, it’s only if you want a root menu

No real point for this as far as I can tell

1 Like

I’m reworking some Git stuff, so @moson when I’m done you might want to update the sha sum on the aur package.

1 Like

sxhjd should be located in the ~/.config/worm according to the documentation. i dont have any issue with that. what i am asking is how the below line will work when i dont have a folder called ~/.config/qtile/rofi/

#~/.config/worm/sxhjd
super + {p,w,x,s}
	~/.config/qtile/rofi/bin/{launcher,windows,powermenu,screenshot}

however, i already have several .rasi files under ~/.config/rofi but yours seemed to require a binary thats why i am little confused.

this is not my configuration, it’s from someone else. you can adapt it or remove it.

the file is called sxhkdrc, not sxhjd. It’s not mentioned in the worm documentation. If it works, it only works because you specify the path manually to sxhkd, which is ok too.

1 Like

ok @codic12 then i would request you to provide your example files, so we can try it. something that works if we copy 3 files from example given on git. (something like you gave us for qtile) of course the lines mentioned in the example files themself may point to other utils like rofi, polybar and configuration.

hope i am not asking too much.

Copy examples/rc to ~/.config/worm/rc.
Copy examples/sxhkdrc to ~/.config/worm/sxhkdrc.

Adapt both to your taste. unless I’m missing something?

2 Likes

already done @codic12

/home/pannet1/.config/worm                                   21-12-13 08:39:00+0530                                                                           
@ tree
.
├── jgmenu_run
├── rc
└── sxhkd

i am only worried about this line

	~/.config/qtile/rofi/bin/{launcher,windows,powermenu,screenshot}

can you explain how this functions (or) can you provide me your line that runs `{launcher, windows, powermenu }`. hope i am not troubling you much.

Like I said, put the sxhkd file in ~/.config/sxhkd and give it the name sxhkdrc! Unless you start sxhkd some other way. Also make sure rc is executable (chmod +x rc).

can you explain how this functions (or) can you provide me your line that runs {launcher, windows, powermenu }. hope i am not troubling you much.

This is from another configuration, like I said. This is completely optional. If you don’t have the files, just remove it. I can give you my sxhkdrc instead to use in ~/.config/sxhkd/sxhkdrc. It’s much simpler:

super + Return
 xfce4-terminal
super + {1-9}
 wormc switch-tag {1-9}
super + shift + {1-9}
 wormc move-active-tag {1-9}
super + shift + f
 wormc float-active
super + f
 wormc layout floating
super + t
 wormc layout tiling
super + q
 wormc close-active-client
2 Likes

I am getting this error running yay worm, tried it a second time with clean build, same result…

:: (1/1) Parsing SRCINFO: worm
==> Making package: worm 0.1.0-1 (Mon 13 Dec 2021 15:37:37)
==> Retrieving sources...
  -> Downloading worm-0.1.0.tar.gz...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   120  100   120    0     0    950      0 --:--:-- --:--:-- --:--:--   952
100 26931    0 26931    0     0  48208      0 --:--:-- --:--:-- --:--:--  462k
==> Validating source files with sha256sums...
    worm-0.1.0.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!
 -> error downloading sources: worm 
	 context: exit status 1 
	 

==> Making package: worm 0.1.0-1 (Mon 13 Dec 2021 15:37:39)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found worm-0.1.0.tar.gz
==> Validating source files with sha256sums...
    worm-0.1.0.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!
 -> error making: worm