Bug#945281: dwm: new upstream release
Hi Bastian,
Thank you very much for this. I'm overwhelmed by work and couldn't find
time and energy for Debian lately. I'm really sorry for the lack of
responsivity!
Best,
Hugo
On Sun, Dec 12, 2021 at 12:02:06PM +0100, Bastian Germann wrote:
> I am sponsoring a NMU (DELAYED/3) for this. The debdiff is attached.
> diff -Nru dwm-6.1/BUGS dwm-6.2/BUGS
> --- dwm-6.1/BUGS 2015-11-08 23:11:48.0 +0100
> +++ dwm-6.2/BUGS 1970-01-01 01:00:00.0 +0100
> @@ -1,44 +0,0 @@
>
> -
> -18:17 < Biolunar> when i change my resolution in dwm (to a smaller one) and
> then back to the native, the top bar is not repainted. that's since 5.7.2, in
> 5.6 it worked fine
> -18:19 < Biolunar> is it just happening to me or a (known) bug?
> -18:24 < Biolunar> and in addition, mplayers fullscreen is limited to the
> small resolution after i changed it back to the native
> -
> -reproducible with xrandr -s but not with --output and --mode, strange
> -
>
> -
> -yet another corner case:
> -open a terminal, focus another monitor, but without moving the mouse
> -pointer there
> -if there is no client on the other monitor to get the focus, then the
> -terminal will be unfocused but it will accept input
> -
>
> -
> -Donald Allen reported this:
> -
> -starting emacs from dmenu in archlinux results in missing configure of
> emacs, but mod1-space or mod1-shift-space fix this problem. this problem is
> new and did not happen in 1.6 xorg servers
> -
>
> -
> -voltaic reports this:
> -
> -When I use two monitors, one larger in resolution than the other, the
> -bar is drawn using the smaller x-dimension on both screens. I think
> -what's happening is that there are two bars drawn, but the short bar
> -is always on top of the long bar such that I can't see the information
> -under the short bar. If I switch to the small screen, hide the short
> -bar, and then switch to the large screen, the long bar is drawn
> -correctly.
> -
> -A similar problem occurs when I have started dwm on a small resolution
> -monitor (laptop screen) and then I switch to a large external display.
> -When I do this, the bar itself is drawn for the original smaller
> -resolution, but the information to be printed on the bar is
> -right-aligned for a longer bar. So what I see is a bar that has the
> -right hand side of it cut-off. See attached screenshot.
> -
> -I am using standard options for xrandr such as --output VGA1 --auto, etc.
> -
>
> diff -Nru dwm-6.1/config.def.h dwm-6.2/config.def.h
> --- dwm-6.1/config.def.h 2015-11-08 23:11:48.0 +0100
> +++ dwm-6.2/config.def.h 2019-02-02 13:55:28.0 +0100
> @@ -1,20 +1,22 @@
> /* See LICENSE file for copyright and license details. */
>
> /* appearance */
> -static const char *fonts[] = {
> - "monospace:size=10"
> -};
> -static const char dmenufont[] = "monospace:size=10";
> -static const char normbordercolor[] = "#44";
> -static const char normbgcolor[] = "#22";
> -static const char normfgcolor[] = "#bb";
> -static const char selbordercolor[] = "#005577";
> -static const char selbgcolor[] = "#005577";
> -static const char selfgcolor[] = "#ee";
> static const unsigned int borderpx = 1;/* border pixel of windows */
> static const unsigned int snap = 32; /* snap pixel */
> static const int showbar= 1;/* 0 means no bar */
> static const int topbar = 1;/* 0 means bottom bar */
> +static const char *fonts[] = { "monospace:size=10" };
> +static const char dmenufont[] = "monospace:size=10";
> +static const char col_gray1[] = "#22";
> +static const char col_gray2[] = "#44";
> +static const char col_gray3[] = "#bb";
> +static const char col_gray4[] = "#ee";
> +static const char col_cyan[]= "#005577";
> +static const char *colors[][3] = {
> + /* fg bg border */
> + [SchemeNorm] = { col_gray3, col_gray1, col_gray2 },
> + [SchemeSel] = { col_gray4, col_cyan, col_cyan },
> +};
>
> /* tagging */
> static const char *tags[] = { "1", "2", "3", "4", "5", "6", "7", "8", "9" };
> @@ -54,7 +56,7 @@
>
> /* commands */
> static char dmenumon[2] = "0"; /* component of dmenucmd, manipulated in
> spawn() */
> -static const char *dmenucmd[] = { "dmenu_run", "-m", dmenumon, "-fn",
> dmenufont, "-nb", normbgcolor, "-nf", normfgcolor, "-sb", selbgcolor, "-sf",
> selfgcolor, NULL };
> +static const char *dmenucmd[] = { "dmenu_run", "-m", dmenumon, "-fn",
> dmenufont, "-nb", col_gray1, "-nf", col_gray3, "-sb", col_cyan, "-sf",
> col_gray4, NULL };
> static const char *termcmd[] = { "st", NULL };
>
> static Key keys[] = {
> @@ -95,7 +97,7 @@
> };
>
> /* button definitions */
> -/* click can be ClkLtSymbol, ClkStatusText, ClkWinTitle, ClkClientWin, or
> ClkRootWin */
> +/* click can be ClkTagBar, ClkLtSymbol, ClkStatusText, ClkWinTitle,
>
Bug#945281: dwm: new upstream release
I am sponsoring a NMU (DELAYED/3) for this. The debdiff is attached.diff -Nru dwm-6.1/BUGS dwm-6.2/BUGS
--- dwm-6.1/BUGS2015-11-08 23:11:48.0 +0100
+++ dwm-6.2/BUGS1970-01-01 01:00:00.0 +0100
@@ -1,44 +0,0 @@
-
-18:17 < Biolunar> when i change my resolution in dwm (to a smaller one) and
then back to the native, the top bar is not repainted. that's since 5.7.2, in
5.6 it worked fine
-18:19 < Biolunar> is it just happening to me or a (known) bug?
-18:24 < Biolunar> and in addition, mplayers fullscreen is limited to the small
resolution after i changed it back to the native
-
-reproducible with xrandr -s but not with --output and --mode, strange
-
-
-yet another corner case:
-open a terminal, focus another monitor, but without moving the mouse
-pointer there
-if there is no client on the other monitor to get the focus, then the
-terminal will be unfocused but it will accept input
-
-
-Donald Allen reported this:
-
-starting emacs from dmenu in archlinux results in missing configure of emacs,
but mod1-space or mod1-shift-space fix this problem. this problem is new and
did not happen in 1.6 xorg servers
-
-
-voltaic reports this:
-
-When I use two monitors, one larger in resolution than the other, the
-bar is drawn using the smaller x-dimension on both screens. I think
-what's happening is that there are two bars drawn, but the short bar
-is always on top of the long bar such that I can't see the information
-under the short bar. If I switch to the small screen, hide the short
-bar, and then switch to the large screen, the long bar is drawn
-correctly.
-
-A similar problem occurs when I have started dwm on a small resolution
-monitor (laptop screen) and then I switch to a large external display.
-When I do this, the bar itself is drawn for the original smaller
-resolution, but the information to be printed on the bar is
-right-aligned for a longer bar. So what I see is a bar that has the
-right hand side of it cut-off. See attached screenshot.
-
-I am using standard options for xrandr such as --output VGA1 --auto, etc.
-
diff -Nru dwm-6.1/config.def.h dwm-6.2/config.def.h
--- dwm-6.1/config.def.h2015-11-08 23:11:48.0 +0100
+++ dwm-6.2/config.def.h2019-02-02 13:55:28.0 +0100
@@ -1,20 +1,22 @@
/* See LICENSE file for copyright and license details. */
/* appearance */
-static const char *fonts[] = {
- "monospace:size=10"
-};
-static const char dmenufont[] = "monospace:size=10";
-static const char normbordercolor[] = "#44";
-static const char normbgcolor[] = "#22";
-static const char normfgcolor[] = "#bb";
-static const char selbordercolor[] = "#005577";
-static const char selbgcolor[] = "#005577";
-static const char selfgcolor[] = "#ee";
static const unsigned int borderpx = 1;/* border pixel of windows */
static const unsigned int snap = 32; /* snap pixel */
static const int showbar= 1;/* 0 means no bar */
static const int topbar = 1;/* 0 means bottom bar */
+static const char *fonts[] = { "monospace:size=10" };
+static const char dmenufont[] = "monospace:size=10";
+static const char col_gray1[] = "#22";
+static const char col_gray2[] = "#44";
+static const char col_gray3[] = "#bb";
+static const char col_gray4[] = "#ee";
+static const char col_cyan[]= "#005577";
+static const char *colors[][3] = {
+ /* fg bg border */
+ [SchemeNorm] = { col_gray3, col_gray1, col_gray2 },
+ [SchemeSel] = { col_gray4, col_cyan, col_cyan },
+};
/* tagging */
static const char *tags[] = { "1", "2", "3", "4", "5", "6", "7", "8", "9" };
@@ -54,7 +56,7 @@
/* commands */
static char dmenumon[2] = "0"; /* component of dmenucmd, manipulated in
spawn() */
-static const char *dmenucmd[] = { "dmenu_run", "-m", dmenumon, "-fn",
dmenufont, "-nb", normbgcolor, "-nf", normfgcolor, "-sb", selbgcolor, "-sf",
selfgcolor, NULL };
+static const char *dmenucmd[] = { "dmenu_run", "-m", dmenumon, "-fn",
dmenufont, "-nb", col_gray1, "-nf", col_gray3, "-sb", col_cyan, "-sf",
col_gray4, NULL };
static const char *termcmd[] = { "st", NULL };
static Key keys[] = {
@@ -95,7 +97,7 @@
};
/* button definitions */
-/* click can be ClkLtSymbol, ClkStatusText, ClkWinTitle, ClkClientWin, or
ClkRootWin */
+/* click can be ClkTagBar, ClkLtSymbol, ClkStatusText, ClkWinTitle,
ClkClientWin, or ClkRootWin */
static Button buttons[] = {
/* clickevent mask button function
argument */
{ ClkLtSymbol, 0, Button1,setlayout,
{0} },
diff -Nru dwm-6.1/config.mk dwm-6.2/config.mk
--- dwm-6.1/config.mk 2015-11-08 23:11:48.0 +0100
+++ dwm-6.2/config.mk 2019-02-02 13:55:28.0 +0100
@@ -1,5 +1,5 @@
# dwm version
-VERSION = 6.1
Bug#945281: dwm: new upstream release
Source: dwm Severity: wishlist Dear maintainer, a new upstream release of dwm is available (6.2). Can you please update the package? Thanks! Kind regards, Reiner signature.asc Description: PGP signature
