ft-labs / pdwm Goto Github PK

I felt the need for an additional feature, where the windows that have been assigned particular tags in the "tags mask" section of client rules, are sent back to the assigned tag upon restart.

Current behaviour is that, the assigned client remains in the current tag.
In other words, if I am using Firefox [assigned to tag 9] in tag 2, upon restart, Firefox should be sent to tag 9, and the windows that haven't been assigned tags should remain in tag 2.

So, I'm using your dwm-preserve-on-restart patch and I'm really appreciating it. However, when restarting dwm, the tag jumps back to the 1st tag. I'd like it to stay on the most recent tag I was on.

First of all, great build of DWM and DWMBlocks.
I really wanted to implement your version of dwmblocks but, I am having a hard time to do so. Could you please tell me how did you implement the clickability into dwm.c?
Did you use statuscmd with signals or something?

Hi there,

do you have a config for plain dwm? I don't mind if there are no animations, but I like the look of your dwm setup.

hello phy
saw ur commit about not focusing sticky windows,
might wanna check out this pr LukeSmithxyz/dwm#181, think it 'fixes' this behaviour pretty well

the ISVISIBLE(c) || c->issticky thing makes impossible to focus sticky windows if they are alone in a tag with focusstack() keybinding (you can still focus the window with the mouse).

Please, when you are free, publish a patch for Alt + Tab functionality.

i have been trying to do exactly this and all i'm getting is uncleared bar text

i loved ur config but for the time being i can not re install my system unfortunately to try phy os, can u please tell how can i get your Alt+tab and the picom that u are using?

Note - I am not using this build of dwm, rather I am using the 'preserveonrestart' patch with my own build of dwm.

I have ran into an issue that I heavily suspect has to do with the preserveonrestart patch.

The easiest example of it I can show is with deadbeef music player's search window. If I send the deadbeef main window to another tag, go to its tag, and then trigger the search window with ctrl-f, the search window will spawn on the original deadbeef tag rather than the one the window actually exists on.

Furthermore, checking the _NET_CLIENT_INFO property of each window, the deadbeef window is updated from '4, 0' to '8, 0', while even the new search window after the old has been killed retains the old property.

I am unable to test this on pdwm at the moment, however I heavily suspect the same thing would occur on it.

Here is a video of the issue.

You have a nice power menu. Can you install it separately. Or can you tell me how to make it?

Please fix the following bug:

Wow GitHub buggy too doesn't let me uploads let's try again ah doesn't work

Basically if I open more than two windows it starts glitching and flackering around which is very bad for health.

Using some old apple laptop. Resolution is terrible since yay -Syu too, WLAN driver is not the right one, it's the one that has terrible performance and phyup dots --force does not work - it doesn't create the hard link.

Firstly, I would like to say, this is an excellent piece of work, really commendable. I had a few questions, I wanted to ask.

• Are there any resources for making a custom Arch ISO that I can refer to?
• How are you handling the installation, from the ISO, I mean are you using something like the calamares installer?

I would appreciate it if you could help me with this.

Thanks

I wanted to give this one a shot and followed the instructions, but I get an error with nvidia.hook

error: failed to commit transaction (conflicting files)
phyOS-sysconf: /etc/pacman.d/hooks/nvidia.hook exists in filesystem

I moved nvidia.hook to nvidia.hook.bkp and the installation proceeded, but it created a bunch of files in /etc/pacman.d/hooks. Is this necessary?

$: paru -S phyOS-dwm-beta 

community/gum                    0.6.0-1         26,19 MiB
phyOS-repo/phyOS-sysconf         2.0-03          14,94 MiB
phyOS-repo/phyOS-system-scripts  2.7-02           0,08 MiB
phyOS-repo/phyOS-dwm-beta        1.2.5_beta-01    0,17 MiB

Total Installed Size:  41,38 MiB

:: Proceed with installation? [Y/n] 
(4/4) checking keys in keyring                                                 [--------------------------------------------] 100%
(4/4) checking package integrity                                               [--------------------------------------------] 100%
(4/4) loading package files                                                    [--------------------------------------------] 100%
(4/4) checking for file conflicts                                              [--------------------------------------------] 100%
error: failed to commit transaction (conflicting files)
phyOS-sysconf: /etc/pacman.d/hooks/nvidia.hook exists in filesystem
Errors occurred, no packages were upgraded.

or at least tell me the code changes required

Hi! Doing just as described in README:

sudo pacman-key --recv-key 964FD85861C858D7
sudo pacman-key --lsign-key 964FD85861C858D7
sudo pacman -Syy phyOS-keyring
sudo pacman-key --init
sudo pacman-key --populate phyOS

But the last command gives this error:

==> Appending keys from phyOS.gpg...
gpg: error reading key: No public key
==> Locally signing trusted keys in keyring...
==> ERROR: 5E29997979B066C7CCF502FE7B2148AD90FEEC50 could not be locally signed.

Im using Arch

error occurred renewing keyring when select "REFRESH PACMAN MIRRORS"

phyOS-repo is up to date
error: target not found: phyOS-dwm
error: target not found: phyOS-dunst
error: target not found: phyOS-dwmblocks
error: target not found: phyOS-st
error: target not found: phyOS-fonts
error: target not found: phyOS-dmenu
error: target not found: phyOS-xmenu
error: target not found: lf

thank you for your work and this project ❤️

Greetings,

I am trying to install this on arch linux. I've installed the necessary packages and built both pdwm and pdwmc. When I try to run the `phyup dots --force' command, it cannot be found. Do you know what could be the problem?

https://ft-labs.github.io/$repo/$arch just does not work.

If I try to do: sudo pacman -Syy phyOS-keyring, It does not work.

╰─$ sudo pacman -Syy phyOS-keyring
:: Synchronizing package databases...
 core                                                           157.0 KiB   518 KiB/s 00:00 [#####################################################] 100%
 extra                                                         1715.3 KiB  4.30 MiB/s 00:00 [#####################################################] 100%
 community                                                        6.7 MiB  9.04 MiB/s 00:01 [#####################################################] 100%
 multilib                                                       170.8 KiB  1761 KiB/s 00:00 [#####################################################] 100%
 phyOS-repo                                                      15.1 KiB   119 KiB/s 00:00 [#####################################################] 100%
resolving dependencies...
looking for conflicting packages...

Packages (1) phyOS-keyring-20240603-3

Total Download Size:   0.02 MiB
Total Installed Size:  0.00 MiB

:: Proceed with installation? [Y/n] 
:: Retrieving packages...
 phyOS-keyring-20240603-3-any                                    19.1 KiB   415 KiB/s 00:00 [#####################################################] 100%
(1/1) checking keys in keyring                                                              [#####################################################] 100%
(1/1) checking package integrity                                                            [#####################################################] 100%
error: phyOS-keyring: signature from "Arda Atci ([email protected]) <[email protected]>" is unknown trust
:: File /var/cache/pacman/pkg/phyOS-keyring-20240603-3-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.

as a solution, I suggest uploading the packages to the official arch repo. I need the components, not the entire package (as provided by the compiling option via git)

Hi there! great build. Btw could you share the patch needed for having png in the statusbar?

Dear Phy,
Great project with great eye candy but I have a suggestion to enhance the feel.

I hope you have heard of Elkowar's Wacky Widgets (eww). I think you have seen (elenapan's rice)[https://old.reddit.com/r/unixporn/comments/hpakeu/awesome_afternoon_in_a_perfect_world/] on unixporn. The dashboard widget on the bottom picture is made with eww. It would be a great addition to your dwm build.

El Psy Kongroo.

So, I'm using your dwm-preserve-on-restart patch and I'm really appreciating it. However, when restarting dwm, the tag jumps back to the 1st tag. I'd like it to stay on the most recent tag I was on.

Hi, I am using endeavouros with gnome desktop right now, and have been trying to install phyOS-dwm. However, when I tried to start dwm from the login screen, it just returns me back to login. I have setup everything according to this repo. dotfiles have also been put into my home directory. I have tried disabling wayland on gnome but it didn't change anything as well. Im not sure if it's path issue, since I didn't know what to set in path.

Good morning,

I was able to get through all of the installation process until the very end. I have my pacman set up and updated. Then the readme tells me to pacman -Syy
and then
curl [https://raw.githubusercontent.com/FT-Labs/phyOS-Aug-22/master/packages.x86_64](https://raw.githubusercontent.com/FT-Labs/phyOS-Aug-22/master/packages.x86_64) | sed -e '/\#/d' | tr -s "\n" | xargs sudo pacman -S --noconfirm

The former works just fine. But the latter returns zsh: unknown file attribute: h error: no targets specified (use -h for help

I literally copied and pasted that second curl code into my terminal, so I assume it's correct. But there are several commands I am not familiar with, so I'm posting this here for some guidance.

Thank you.

Was there a reason to merge the two? They're two separate pieces of software that do two different things. By merging them you've violated the suckless methodology.

Is there a technical reason to doing this other than "only installing one thing?"

It's a shame because I want to use your flavor of dwmblocks but not dwm and now that is not possible.