bakkeby / dusk Goto Github PK

View Code? Open in Web Editor NEW

139.0 10.0 21.0 1.46 MB

Just another fork of dwm

License: MIT License

Makefile 0.54% C 97.77% Roff 1.68%

dusk's Introduction

Refer to the comprehensive wiki for an introduction to dusk.

dusk's People

Contributors

Stargazers

Watchers

dusk's Issues

how to deactivate bottombar?

howdy,
first of all, i really like DUSK :)

one thing i can't get my head around:

how do i deactivate the bottombar? in my flexipatch dwm-setup when i hide a client/tag i stays in the topbar, but only the color changes....
is this also possible?

cheers and thnaks in advanced

BSD support

There is currently no support for BSD in dusk because the IPC (inter-process communication) implementation uses epoll which is a very Linux centric facility for I/O event notification.

The IPC logic is used to allow the dusk client (duskc) to communicate with dusk to run commands, set the status, get information, etc.

One option would be to port the IPC patch (github) to use the cross-platform libevent library to handle the lower end communication (epoll, kqueue, etc.). There is also a smaller libev library, but this is not so readily available on all platforms to my knowledge.

Alternatively one could use the kqueue library directly and have compile time flags to switch between the kqueue or epoll implementation. Dropping IPC altogether would be less than ideal.

This may be a waste of effort if there is no interest in support for BSD of course so add a 👍🏻 to this issue to show interest.

If you would like to get involved regarding this then that would be most appreciated.

Is Dusk maintained seaprately from dwm?

Forgive the ignorance. What I mean is that whether further modifications in dwm will be integrated into dusk?

Application that should start minimized to systray is opening a window instead.

I have two applications that start minimized to systray: Nextcloud-client and KeePassXC, the later works as expected, but Nextcloud-client starts showing its GUI instead.
I did some testing on dwm, maybe it will help figuring out what is happening:
dwm with no patches shows the GUI when the application starts.
dwm with only the systray patch behaves as expected, i.e. starts minimized to systray and no open windows.
So, the application seems to be behaving as if dusk had no systray when it starts. Although, other than that, the icon shows in it and everything works fine.

Random colors in the systrayspacing background.

The space provided by systrayspacing used to have the same background color as the other icons on systray, but now it shows random colors instead.

in wiki, "broken link"...

hello,
in the page configuration, when arriving on Icon section this :
"Refer to the flexwintitle page for more details. " sends you back to the "cover" of the wiki...
And I tried to locate if there is such page but I was unsuccessful.

sorry english isn't my native language.(It was pretty fun to adapt the keyboard to have dusk working...)
have a good day(and a good year, it's the season ^^)

ViewOnWS does not work

Looks like currently behavior with both ViewOnWS enabled/disabled is the same. leaving it commented out still switches workspace when you move a window and does the same when it is uncommented.

Also to confirm I tried it unmodified and got the same result.

Also, thanks for this awesome application. Been looking for something to fit my workflow for years and looks like this is just what I have been looking for.

restart fails to restart when nm-applet was autostarted

restart doesn't restart
quit doesn't quit cleanly

(sorry, don't have the exact errors, but can get them if needed).

I merged in some of the recent code changes. Built dusk.
Used my keybinding for restart
I believe autostarted processes stopped as expected
Boom. I'm back at a tty looking at an error

startx to get dusk going

keybinding for quit
// does not seem to quit cleaning

startx to get dusk going
keybinding for restart
// same behavior as before

Let me know if versions of any packages/libraries are needed. Arch system was up to date as of Sunday with kernel (lts) and related.

XCB rewrite

Nothing serious, just some autism.. But there are some benefits in using xcb over the good old Xlib.
I've committed too much to my build to use another wm and I don't know other dwm fork with that much modification than dusk.

This will be such tedious work, change all X functions to xcb ones.

Just wondering what's your opinion.

XF86 keys

Hey bakkeby!,
I am currently setting up dusk on my machine running arch linux. I was setting the keybindings and now I want to setup xf86 keys, like brightness up and down, play/pause, etc.
Is there any way to do this or have I missed something in the wiki?

Focus lost when switching workspaces; mod+k fails

Put 3 clients on 2 workspaces, using default layout, []=. I'm using st as the terminal. Let's call the spaces WS A and WS B

In WS B, move focus to a stack window.
Type WS A to move to that workspace
Type WS A to move back to the WS B workspace
// no focus
// mod+k does nothing
// mod+j gives focus, now mod+k works

Seems to happen only when A<B.

This has workarounds and is cosmetic. Lower priority.

When on WS1 and MOD1 moves to another WS, the resultant WS looses it's apps in the top panel

Watch the top panel / bar, in particular the apps between the tag indicator and the blocks (if any are set) in these.

Put a couple windows on WS1, WS2, and maybe WS3. Move mouse onto the top panel and/or a corner.

Go to WS1 via MOD-1. Go to WS2 via MOD-2. MOD-1, MOD-1 again. You should be on WS2

The middle of the top panel is dark. Yet the workspace has clients on it.

Give a window on WS2 focus. Now MOD-2 (back to WS1), MOD-2 (back to WS2) and the top panel is as expected.

It seems that when WS1 is front, and MOD-1 occurs, whatever was the previous to WS1 workspace that is moved to doesn't get an event or a paint of the clients on that workspace. Doing this with any other workspace combo seems to work as expected. I only hit this when leaving WS1 and using MOD1.

Process dusk dumped core.

Hi,
I am trying the latest github version od dusk.
If I press 5 times MODKEY+1, dusk restarts.
Later I discovered from journalctl and dmesg that there is segmentation fault.
I am not sure if this is related with my changes in config.h.
config.h.txt

[root@dle5570 ~]# journalctl -xe
...
Jan 07 09:57:18 dle5570 kernel: audit: type=1130 audit(1641545838.279:214): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@10-19075-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=>
Jan 07 09:57:18 dle5570 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@10-19075-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 07 09:57:18 dle5570 systemd-coredump[19076]: [🡕] Process 18488 (dusk) of user 24840 dumped core.

                                                 Module /home/kmarzic/bin/dusk with build-id 7c58ebbf30969476359db1591636318932e6147f
                                                 Module linux-vdso.so.1 with build-id 035c7da8b451e8d19aed30c8ca3970d363e14060
                                                 Module libXfixes.so.3 with build-id 0a05c7e8714522bfbdd7c0027c3e2a94965664b0
                                                 Module libXcursor.so.1 with build-id eb6315bcd7526aaf51b0a1307efdc587cea0a152
                                                 Module libpcre.so.1 with build-id 845483dd0acba86de9f0313102bebbaf3ce52767
                                                 Module libbrotlicommon.so.1 with build-id a4ba3f4b4571c8272343b621da812a6e24a202a7
                                                 Module libglib-2.0.so.0 with build-id 8214b56e554b7cbead4034b6ba32c90bc8c674da
                                                 Module libgraphite2.so.3 with build-id 47761dc11e553f519cde97ed9ee985be12ccdae2
                                                 Module libbrotlidec.so.1 with build-id 45defc036e918e0140a72f1fbce6e7692d38241d
                                                 Module libharfbuzz.so.0 with build-id 1d9dee49dd99162c3f83eb3259c3c88c6b4cd7fe
                                                 Module libpng16.so.16 with build-id 2dc0bce07f199bf983c07a05fb95a6f4af83a9b3
                                                 Module libbz2.so.1.0 with build-id 919597c477c9b2cb9cdbb7745ed6494ac0e6da60
                                                 Module libz.so.1 with build-id 0c1459c56513efd5d53eb3868290e9afee6a6a26
                                                 Module ld-linux-x86-64.so.2 with build-id 040cc3dd10461562f177df39e3be2f3704258c3c
                                                 Module libxcb-shm.so.0 with build-id fb797f299a446f559a95afcc168227482cc800d1
                                                 Module libm.so.6 with build-id 2b8fd1f869ecab4e0b55e92f2f151897f6818acf
                                                 Module libXdmcp.so.6 with build-id 8ca0792d23c8b8b4c0864297512349292bea5955
                                                 Module libXau.so.6 with build-id 1c67764663e07bec24d8951e5fd93f4d165979ff
                                                 Module libpthread.so.0 with build-id 07c8f95b4f3251d08550217ad8a1f31066229996
                                                 Module libexpat.so.1 with build-id 16023a53e7b5bbdff92bd0bf2eebd36f9b5b879f
                                                 Module libfreetype.so.6 with build-id 26c5f833068ff72660d1975cbc2074c3eb47fad8
                                                 Module libXext.so.6 with build-id d70f24beb4fad748d6becffdcc13e51be0a2ebfa
                                                 Module libdl.so.2 with build-id 5abc547e7b0949f89f3c0e21ab0c8331a7440a8a
                                                 Module libc.so.6 with build-id 4b406737057708c0e4c642345a703c47a61c73dc
                                                 Module libImlib2.so.1 with build-id f5c3881e6d998f80a7666caa27c070a6f21dd4cd
                                                 Module libyajl.so.2 with build-id 392467faca2d964441b8226ee48d994ffc70e545
                                                 Module libxcb-res.so.0 with build-id b825f66a75478fd00eeb4c57ecb0ac7792e00f5e
                                                 Module libxcb.so.1 with build-id 0d1ef11740a5daad2ee331e812a51aa6574af222
                                                 Module libX11-xcb.so.1 with build-id 0db4f94d8ae31b8dc9a83f825a9171656f1e532c
                                                 Module libXrender.so.1 with build-id 97e0b9ab6ba96ebc86527cc2b3c3078aad8616b3
                                                 Module libXft.so.2 with build-id 21aed1dfa73fa7301e280e3a573cc2523a1f7ff2
                                                 Module libfontconfig.so.1 with build-id 1103a641395c7d3b42e49b793d3a9ea927c77bf6
                                                 Module libXinerama.so.1 with build-id dbb6adece34ea2766d3efcd628af8f9757344dd6
                                                 Module libX11.so.6 with build-id 5ba5798d193c0065014b8c6252a0678671c8d478
                                                 Stack trace of thread 18488:
                                                 #0  0x000055ed99768e01 n/a (/home/kmarzic/bin/dusk + 0x18e01)
                                                 ELF object binary architecture: AMD x86-64
░░ Subject: Process 18488 (dusk) dumped core
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ Documentation: man:core(5)
░░
░░ Process 18488 (dusk) crashed and dumped core.
░░
░░ This usually indicates a programming error in the crashing program and
░░ should be reported to its vendor as a bug.
Jan 07 09:57:18 dle5570 kernel: audit: type=1131 audit(1641545838.373:215): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@10-19075-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=>
Jan 07 09:57:18 dle5570 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@10-19075-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 07 09:57:18 dle5570 systemd[1]: [email protected]: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
...
[root@dle5570 ~]#

[root@dle5570 ~]#  dmesg -T
...
[Fri Jan  7 09:57:17 2022] show_signal_msg: 30 callbacks suppressed
[Fri Jan  7 09:57:17 2022] dusk[18488]: segfault at a0 ip 000055ed99768e01 sp 00007ffc1f54fe00 error 4 in dusk[55ed9975b000+20000]
[Fri Jan  7 09:57:17 2022] Code: a8 00 00 00 48 89 fe eb 28 bf 40 00 00 00 e8 19 0f 01 00 41 89 c0 b8 02 00 00 00 45 85 c0 74 16 48 8b 43 08 31 f6 48 8b 40 50 <48> 8b b8 a0 00 00 00 e8 ba 70 ff ff 83 7b 38 00 89 43 3c 74 50 48
[Fri Jan  7 09:57:17 2022] audit: type=1701 audit(1641545838.243:210): auid=24840 uid=24840 gid=100 ses=1 pid=18488 comm="dusk" exe="/home/kmarzic/bin/dusk" sig=11 res=1
...
[root@dle5570 ~]#

Best regards

Arabic and Right-to-Left Languages is NOT rendered Correctly.

Hi @bakkeby thanks for this amazing fork of DWM it's working great;
but there is a simple problem with an easy fix and it's that Arabic and right-to-left languages are not rendered probably on the bar, it looks like this.

There is a patch in DWM website called bidi BUT i don't know how to put it in dusk.
thanks again.

What patch is this?

What patch do you use to do https://raw.githubusercontent.com/wiki/bakkeby/dwm-vanitygaps/dusk_scr01.gif ? I'd like to know because i am looking for such behaviour on my dwm. Thanks.

Wayland support

I am adding this as an issue as it is likely going to be a frequently asked question.

There is currently no support for Wayland with regards to dusk. Wayland support is not entirely out of the question, but going down that route would be a separate project in any case.

Such a project could draw from the experiences of dwl (dwm for Wayland) and sway both relying on the wlroots libraries.

Now you may want to curb your expectations with regards to dusk on Wayland as the reality of it is that it would mean a lot less features:

the window manager essentially has to implement their own compositor, or use wlroots, which means that certain features that your favourite compositor has will not be available
client rules may potentially not be available besides filtering on application ID or window title
seamless restarts will likely not be possible
such an implementation might have to drop the bar(s)
multi-monitor support may have to be hardcoded (like in Sway), i.e. no hotplugging support
workspace previews would likely have to be dropped
and quite likely a range of other features would have to go as well (will try to update if I come across any specifics)

This may be a waste of effort if there is no interest in support for Wayland of course so add a 👍🏻 to this issue to show interest.

bakkeby / dusk Goto Github PK

dusk's Introduction

dusk's People

Contributors

Stargazers

Watchers

Forkers

dusk's Issues

Recommend Projects

Recommend Topics

Recommend Org