| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I noticed that a non-trivial amount of dwm's work on my machine was from
drw_text, which seemed weird, because I have the bar disabled and we
only use drw_text as part of bar drawing.
Looking more closely, I realised that while we use m->showbar when
updating the monitor bar margins, but don't skip actually drawing the
bar if it is hidden. This patch skips drawing it entirely if that is the
case.
On my machine, this takes 10% of dwm's on-CPU time, primarily from
restack() and focus().
When the bar is toggled on again, the X server will generate an Expose
event, and we'll redraw the bar as normal as part of expose().
|
| |
|
|
|
|
|
| |
This reverts commit 716233534b35f74dba5a46ade8f1a6f8cc72fea4.
It causes issues with truncation of characters when the text does not fit and
so on. The patch should be reworked and properly tested.
|
| |
|
|
|
|
| |
Calculates len & ew in drw_font_getexts loop by incrementing instead of
decrementing; as such avoids proportional increase in time spent in loop
based on provided strings size.
|
| |
|
|
|
| |
Some people are annoyed to have this new behaviour forced for some
application which use fake fullscreen.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
It generally doesn't make much sense to allow focusstack() to navigate
away from the selected fullscreen client, as you can't even see which
client you're selecting behind it.
I have had this up for a while on the wiki as a separate patch[0], but
it seems reasonable to avoid this behaviour in dwm mainline, since I'm
struggling to think of any reason to navigate away from a fullscreen
client other than a mistake.
0: https://dwm.suckless.org/patches/alwaysfullscreen/
|
| | |
|
| | |
|
| |
|
|
| |
The function drw_fontset_free in drw.c was never called.
|
| |
|
|
|
|
|
|
| |
Many users new to dwm find themselves caught out by being kicked out to the login manager (dwm crashing) when they open 50+ clients for demonstration purposes. The number of clients reported varies depending on the resolution of the monitor.
The cause of this is due to how the default tile layout calculates the height of the next client based on the position of the previous client. Because clients have a minimum size the (ty) position can exceed that of the window height, resulting in (m->wh - ty) becoming negative. The negative height stored as an unsigned int results in a very large height ultimately resulting in dwm crashing.
This patch adds safeguards to prevent the ty and my positions from exceeding that of the window height.
|
| |
|
|
|
|
|
| |
This jarred me a bit while reading the code, since "sw" usually refers
to the global screen geometry, but in drawbar() only it refers to
text-related geometry. Renaming it makes it more obvious that these are
not related.
|
| |
|
|
|
| |
No functional changes, but for every other function we have a forward
declaration here. getatomprop should be no exception.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There are two places that mfact can be set:
- In the mfact global, which is defined at compile time and passed
into m->mfact during monitor setup. No bounds checks are performed,
but the comment alongside it says that valid values are [0.05..0.95]:
static const float mfact = 0.55; /* factor of master area size [0.05..0.95] */
- By setmfact, which adjusts m->mfact at runtime. It also does some
minimum and maximum bounds checks, allowing [0.1..0.9]. Values outside
of that range are ignored, and mfact is not adjusted.
These different thresholds mean that one cannot setmfact 0.95 or 0.05,
despite the comment above that lists the legal range for mfact.
Clarify this by enforcing the same bounds in setmfact at runtime as
those listed for mfact at compile time.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The feature test was incorrect:
_POSIX_C_SOURCE=2
"The value 2 or greater additionally exposes definitions for POSIX.2-1992."
http://man7.org/linux/man-pages/man7/feature_test_macros.7.html
A higher value is needed (atleast 1995):
https://pubs.opengroup.org/onlinepubs/9699919799/functions/snprintf.html
FreeBSD feature test macro:
on
https://github.com/freebsd/freebsd/blob/master/include/stdio.h line 297
This was already fixed in dmenu.
This fixes a warning on FreeBSD, reported by Plasmoduck on IRC, thanks.
|
| | |
|
| | |
|
| |
|
|
| |
Don't be fancy and just show the actual output so debugging is simpler.
|
| |
|
|
|
| |
Building with debug symbols is worthless unless LDFLAGS are manually
adjusted as well.
|
| | |
|
| |
|
|
|
|
|
| |
by Christopher Drelich <cd@cdrakka.com>
Patch was mangled on the ML, also adjusted the order to be the same as
the enum in dwm.c
|
| |
|
|
|
|
|
| |
In dwm.c function declarations are in alphabetical order except for
updategeom(). There doesn't appear to be any reason for this, so this
patch corrects that, and now all function declarations are in
alphabetical order.
|
| |
|
|
|
|
| |
the bug in the dwm man page is an (ancient) Java issue.
Thanks David and quinq for the patches and feedback!
|
| |
|
|
| |
Thanks Christopher Drelich <cd@cdrakka.com>
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Reported by Kernc, thanks!
"This makes a particular program that uses libwnck [1] fail after:
Wnck-WARNING **: Property _NET_WM_NAME contained invalid UTF-8
in this code [2] because the returned string contains a '\0' and the
documentation for g_utf8_validate() [3] explicitly states that when
string length is provided, no nul bytes are allowed."
It is not entirely clear it is incorrect, other WM's seem to not
NUL terminate it either though.
|
| | |
|
| | |
|
| |
|
|
|
| |
This is useful for configuring compositors to ignore the status bar
window.
|
| | |
|
| |
|
|
|
| |
The previous patches introduced some unclean space-based indentation
patterns. This patch fixes them.
|
| |
|
|
|
| |
This also fixes a bug where client windows only switch to floating mode when the
mouse is dragged in one specific direction.
|
| |
|
|
|
|
|
|
|
|
|
| |
Before this change it is not possible to press a button in a client on the first
click if the client is not yet focused. The first click on the button would
only focus the client and a second click on the button is needed to activate it.
This situation can occur when moving the mouse over a client (therefore focusing
it) and then moving the focus to another client with keyboard shortcuts.
After this commit the behavior is fixed and button presses on unfocused clients
are passed to the client correctly.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
- unify multi-line expression alignment style.
- unify multi-line function call alignment style.
- simplify client moving on monitor count decrease.
- clarify comment for focusin().
- remove old confusing comment about input focus fix in focusmon(). The
explanation is already in the old commit message, so no need to keep it in the
code.
- remove old comment describing even older state of the code in focus().
- unify comment style.
- break up some long lines.
- fix some typos and grammar.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
thanks Markus Teich and David!
|
| | |
|
| | |
|
| |
|
|
|
| |
- better scaling for occupied tag squares.
- draw statusline first to omitt some complicated calculations.
|
| |
|
|
|
|
| |
Configuring geometry before applying rules makes it possible to have
more complex constraints in applyrules that depend on the initial window
dimensions and location.
|
| |
|
|
| |
patch provided by Bert Münnich <ber.t_AT_posteo.de>, thanks!
|
| | |
|
| | |
|
| | |
|
| | |
|
