| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |/
| |
| |
| |
| |
| | |
Additionally, variables xcursor and xcursor_mgr are only used
when xwayland is defined, so I make the variables declaration
contingent on whether xwayland is being used
|
|\ \
| | |
| | | |
Determine monitor order spatially
|
| | | |
|
| |/
| |
| |
| |
| | |
No need to track our own order; wlroots has a reasonable default for us
already.
|
|/
|
|
| |
Tracking with breaking change from swaywm/wlroots@b7dc4f2.
|
|\
| |
| | |
Define monitor's x,y at compile time
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Replaces the outputOrder patch.
This avoids recalculating positions and allows to arrange monitors in
any order, not just from left to right.
The order in which monitors are defined in config.h still matters but
it's just the order in the list, not the actual position.
|
| |
| |
| |
| | |
Tracking with breaking change in swaywm/wlroots#2593.
|
| | |
|
| |
| |
| |
| |
| |
| | |
I am embarrassed to have let this slip through someone's merge. Anybody
who genuinely needs to `sudo make` will know it; everyone else should
use a proper package manager and build system.
|
|\ \
| |/
|/| |
document that we currently follow wlroots-git
|
|/
|
|
| |
Closes #73.
|
|
|
|
|
| |
This reverts commit 90cc3b1e2c824db74e932dbb9733d398619a037c. Didn't
mean to merge this change.
|
|
|
|
|
|
|
| |
This is the order of *_destroy calls which resulted in the fewest
errors/leaks detected by Valgrind. Most of the errors come from the
gbm_allocator code - will have to figure out which destroy call is still
missing.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This was a prime candidate for reducing the verbosity of some of our
code
|
|
|
|
| |
This reverts commit 572ccd92c43b83b677e87c3926d0f5703224c2d8.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Similar to Linux kernel approach, encapsulate some of the uglier
conditional compilation into inline functions in header files.
The goal is to make dwl.c more attractive to people who embrace the
suckless philosophy - simple, short, hackable, and easy to understand.
We want dwm users to feel comfortable here, not scare them off. Plus,
if we do this right, the main dwl.c code should require only minimal
changes once XWayland is no longer a necessary evil.
According to `cloc`, this also brings dwl.c down below 2000 lines of
non-blank, non-comment code.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Fix style.
|
|\
| |
| |
| |
| | |
Thanks so much for helping to keep the project running while life was
crazy!
|
| | |
|
| | |
|
| |
| |
| |
| | |
This inverts the scroll even on regular mice.
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
The order in which monitors are defined in monrules[] actually matters.
Monotors that aren't configured in monrules[], it will always be the
leftmost.
|
| |
| |
| |
| |
| |
| | |
...in internal calls to restore pointer focus. Necessary for the
unclutter patch, and there's no harm in avoiding this call even in
mainline; might prevents issues in same edge cases.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- A maximum SLOC can't be reasonably determined before implementing the
missing protocols, so not any time soon
- dwl definitely isn't a simple as dwm since it must implement lots of
Wayland protocols and not just manage windows. The status bar
integration, layer shell popups, damage tracking and IME are gonna
require hundreds more lines each.
- "Buffering of input when spawning a client so you don't have to wait
for the window (use `wl_client_get_credentials` to get the PID) - would
this require passing through something like dmenu? Extension protocol?"
This sounds exoteric, if anything this should be patch.
- Can dwl really be started from within an X session? When I do it from
dwm it crashes.
- A window's texture is scaled for its "home" monitor only (noticeable
when window sits across a monitor boundary)
Gonna open a ticket for this rather than keep it in the README.
|
| |
| |
| |
| | |
just wtf is XXX supposed to be? It sounds like a pornographic thing.
|
| |
| |
| |
| |
| | |
It's impossible to understand that this stands from drawable if you're
not familiar with dwm's code.
|
| |
| |
| |
| | |
...or update selmon when we just want to restore pointer focus.
|
| | |
|
| |
| |
| |
| | |
And don't activate clients while an overlay is focused.
|
| |
| |
| |
| |
| |
| |
| | |
Don't let internal calls to motionnotify(0) meant to update the pointer
focus from maplayersurfacenotify and destroylayersurfacenotify also
shift the keyboard focus to the surface under the cursor with
sloppyfocus.
|
| |
| |
| |
| |
| |
| |
| | |
Don't show an X cursor when closing an Xwayland window or with certain
dropdowns.
Based on https://github.com/djpohly/dwl/pull/32
|
| |
| |
| |
| |
| | |
The comment in this function's declaration says the backend is free to
ignore this setting, so maybe there's no need to make it configurable?
|
| |
| |
| |
| |
| | |
Because it's 2020. Passing integers to wlroots variables and functions
with bool in their signature is silly.
|
| |
| |
| |
| |
| |
| | |
wtf is the point of this crap? It makes the code harder to follow,
increases the line count and made me fail compilation a million times.
We shouldn't blindy follow everything about suckless's style.
|