Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clickable status: alternate method #5

Open
ejv2 opened this issue Apr 17, 2022 · 1 comment
Open

Clickable status: alternate method #5

ejv2 opened this issue Apr 17, 2022 · 1 comment

Comments

@ejv2
Copy link
Contributor

ejv2 commented Apr 17, 2022

Although the standard dwm patch for clickable status requires the use of BSD user signals, would it be worth programming an alternate interface and a custom dwm patch which uses some other RPC mechanism. For instance, a simple named pipe would do. We could have dwm write the index of the block into the FIFO. Then, all gocaudices has to do is have a goroutine waiting for the data (FIFOs are buffered) and send a signal over a channel when data is recieved. This would be much cleaner than all the cgo stuff you had to do for signals.

The downside of this is, obviously, that you can't use the stock dwm clickablestatus patch, but I think this could be well worth the cost of a separate patch to remove all the C signal handling.

I'll do some more research into named pipes and, if you want, start a draft PR.

@LordRusk
Copy link
Owner

Funny you should bring this up, I've been thinking on using fifo specifically to make this patch, but I've lost a lot of time for programming and what little I have has been for zara, similar to this project except uses interfaces rather than external programs or scripts.

I say full send on this, I'll be working on it when I can but if you can get a working model, I'll merge it in. And tbh having a patch for dwm that handles status clicks through fifo rather than signals would be simpler, and might I say, suck less.

And I'd love nothing more than to get rid of the shitty cgo I had to write to get it working with the other patch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants