| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
| |
Added SUPER-<F5> as a binding for launching wee-chat
|
| |
|
|
|
| |
I keep having thoughts of adjustments to make, so I figure I should try
listing them somewhere.
|
| |
|
|
|
| |
TODO: See if it's possible to prevent Zoom notifications from stealing
window focus.
|
| |
|
|
|
|
|
|
| |
This is a little fragile, but it seems like it works at least for my
configuration. If you do a SUPER+SHIFT+CLICK1 on a window, it will
activate all the tags associated with that window. The main idea here
is to allow going to the tags of a window from view all tags with a
mouse click.
|
| |
|
|
|
|
| |
Probably not the best way to do this, but it was the most
straightforward. When viewing all tags, I manually unset all the
scratchpad tags by ^= the monitor's tagset with SPTAGMASK.
|
| | |
|
| |
|
|
| |
https://dwm.suckless.org/patches/pertag/
|
| | |
|
| | |
|
| |
|
|
| |
https://dwm.suckless.org/patches/statusallmons/
|
| | |
|
| | |
|
| |
|
|
| |
Added application keybindings and switched a few other bindings around
|
| | |
|
| |
|
|
| |
http://dwm.suckless.org/patches/movestack/
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Copied Xf86 Keybindings from Luke Smith's config of dwm. I'll probably
change a few of these as time goes on, but it is a convenient starting
point.
|
| |
|
|
|
|
| |
Some of the scratchpad keybindings were duplicated, which resulted
in the toggle functionality being broken. Removing the duplicates
fixes the issue.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
https://dwm.suckless.org/patches/status2d/
For color support in the status bar. Had to tweak the xrdb patch a
bit to make it work with the xresources patch already applied.
Currently had a bug where an unprintable character is shown at the
beginning of the status bar when a symbol is present.
|
| |
|
|
|
|
|
| |
https://dwm.suckless.org/patches/statuscmd/
This was done in preparation for using Luke's build of dwmblocks, and is
needed to support clickable statusbar elements.
|
| |
|
|
| |
https://dwm.suckless.org/patches/statusbarfont/
|
| |
|
|
|
| |
Seems using a fancy Nerdfont breaks things, so for now I'm
just not pulling in a font via Xresources
|
| |\ |
|
| | |
| |
| |
| | |
https://dwm.suckless.org/patches/scratchpads/
|
| |/
|
|
| |
https://dwm.suckless.org/patches/scratchpads/
|
| |
|
|
| |
https://dwm.suckless.org/patches/swallow/
|
| | |
|
| | |
|
| |
|
|
| |
https://dwm.suckless.org/patches/restartsig/
|
| |
|
|
| |
https://dwm.suckless.org/patches/xresources/
|
| | |
|
| |
|
|
| |
https://dwm.suckless.org/patches/vanitygaps/
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|