summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'master' of github.com:dbrumbaugh/dwmDouglas Rumbaugh2022-02-032-2/+25
|\
| * Added keybinding for htopDouglas Rumbaugh2022-02-031-1/+5
| |
| * Updated todo listDouglas Rumbaugh2022-02-031-0/+1
| |
| * weechat keybinding:Douglas Rumbaugh2022-02-011-1/+1
| | | | | | | | Added SUPER-<F5> as a binding for launching wee-chat
| * Added TODO list to READMEDouglas Rumbaugh2022-01-271-0/+18
| | | | | | | | | | I keep having thoughts of adjustments to make, so I figure I should try listing them somewhere.
* | Replace all drawbar() with drawbars()Douglas Rumbaugh2022-02-031-19/+17
|/ | | | | Replaced all calls to drawbar() with drawbars(), to ensure that all statusbars are regularly updated, rather than just the active one.
* zoom: Make zoom floating, so notifications aren't as annoyingDouglas Rumbaugh2022-01-211-0/+1
| | | | | TODO: See if it's possible to prevent Zoom notifications from stealing window focus.
* Enabled switching to tags by clickingDouglas Rumbaugh2022-01-122-1/+3
| | | | | | | | 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.
* Scratchpads no longer show while viewing all tagsDouglas Rumbaugh2022-01-121-1/+3
| | | | | | 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.
* Added a grid layoutDouglas Rumbaugh2022-01-121-1/+1
|
* Applied the pertag patchDouglas Rumbaugh2022-01-121-6/+82
| | | | https://dwm.suckless.org/patches/pertag/
* gitignoreDouglas Rumbaugh2022-01-121-0/+1
|
* Keybinding modificationsDouglas Rumbaugh2022-01-121-11/+15
|
* Applied statusallmons patchDouglas Rumbaugh2022-01-091-2/+4
| | | | https://dwm.suckless.org/patches/statusallmons/
* keybindings: added and re-orged some keybindingsDouglas Rumbaugh2022-01-051-20/+19
|
* Fixed issue with F3 not properly launching newsboatDouglas Rumbaugh2021-12-311-2/+6
|
* dwm keybindingsDouglas Rumbaugh2021-12-291-23/+26
| | | | Added application keybindings and switched a few other bindings around
* Increased brightness granularityDouglas Rumbaugh2021-12-271-2/+2
|
* Applied movestack patchDouglas Rumbaugh2021-12-262-1/+52
| | | | http://dwm.suckless.org/patches/movestack/
* Added sleep hotkeyDouglas Rumbaugh2021-12-261-1/+1
|
* Added screen-lock hotkeyDouglas Rumbaugh2021-12-251-0/+2
|
* XF86 KeybindingsDouglas Rumbaugh2021-12-251-1/+31
| | | | | | 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.
* Removed doubled keybindingsDouglas Rumbaugh2021-12-251-2/+0
| | | | | | Some of the scratchpad keybindings were duplicated, which resulted in the toggle functionality being broken. Removing the duplicates fixes the issue.
* Updated font configurationDouglas Rumbaugh2021-12-251-3/+4
|
* Applied status2d with xrdb patchDouglas Rumbaugh2021-12-252-9/+172
| | | | | | | | | | 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.
* Applied the statuscmd patchDouglas Rumbaugh2021-12-222-5/+98
| | | | | | | 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.
* Applied statusbar font patchDouglas Rumbaugh2021-12-195-18/+34
| | | | https://dwm.suckless.org/patches/statusbarfont/
* Merge cleanup and removed xresource for fontDouglas Rumbaugh2021-12-191-5/+1
| | | | | Seems using a fancy Nerdfont breaks things, so for now I'm just not pulling in a font via Xresources
* Merge branch 'master' of github.com:dbrumbaugh/dwmDouglas Rumbaugh2021-12-191-0/+6
|\
| * Added scratchpads patchDouglas Rumbaugh2021-12-192-9/+70
| | | | | | | | https://dwm.suckless.org/patches/scratchpads/
* | Added scratchpads patchDouglas Rumbaugh2021-12-192-11/+75
|/ | | | https://dwm.suckless.org/patches/scratchpads/
* Added swallow patchDouglas Rumbaugh2021-12-193-10/+240
| | | | https://dwm.suckless.org/patches/swallow/
* Modifications for better gapsDouglas Rumbaugh2021-12-191-6/+6
|
* Revised keybindingsDouglas Rumbaugh2021-12-191-8/+12
|
* Applied restartsig patchDouglas Rumbaugh2021-12-191-0/+22
| | | | https://dwm.suckless.org/patches/restartsig/
* Applied Xresources patchDouglas Rumbaugh2021-12-194-23/+118
| | | | https://dwm.suckless.org/patches/xresources/
* Make now cleans up config fileDouglas Rumbaugh2021-12-191-1/+1
|
* Applied Vanity Gaps patchDouglas Rumbaugh2021-12-194-30/+860
| | | | https://dwm.suckless.org/patches/vanitygaps/
* drawbar: Don't expend effort drawing bar if it is occludedChris Down2021-12-191-0/+3
| | | | | | | | | | | | | | | | | 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().
* Revert "Improve speed of drw_text when provided with large strings"Hiltjo Posthuma2021-08-201-5/+2
| | | | | | | 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.
* Improve speed of drw_text when provided with large stringsMiles Alan2021-08-091-2/+5
| | | | | | 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.
* Add a configuration option for fullscreen lockingQuentin Rameau2021-07-142-1/+2
| | | | | Some people are annoyed to have this new behaviour forced for some application which use fake fullscreen.
* Do not allow focus to drift from fullscreen client via focusstack()Chris Down2021-03-291-1/+1
| | | | | | | | | | | | | 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/
* Fix x coordinate calculation in buttonpress.Ian Remmler2020-08-211-1/+1
|
* dwm.1: fix wrong text in man pageHiltjo Posthuma2020-07-081-1/+1
|
* Fix memory leaks in drwAlex Flierl2020-06-111-0/+1
| | | | The function drw_fontset_free in drw.c was never called.
* dwm crashes when opening 50+ clients (tile layout)bakkeby2020-04-251-2/+4
| | | | | | | | 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.
* drawbar: Don't shadow sw globalChris Down2020-04-221-4/+4
| | | | | | | 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.
* getatomprop: Add forward declarationChris Down2020-04-221-0/+1
| | | | | No functional changes, but for every other function we have a forward declaration here. getatomprop should be no exception.
* setmfact: Unify bounds for compile-time and runtime mfactChris Down2020-04-201-1/+1
| | | | | | | | | | | | | | | | | | | | 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.