Bug#392943: wmaker: Broken keyboard shortcuts with new default theme
Hi, The current version of wmaker uses a new upstream since version 0.95.0. I am closing old bugs, because wmaker has been changed a lot. this bug is very old. Can I close it? Regards, kix -- .''`. Rodolfo García Peñas (kix) : :' : Proud Debian Developer `. `'` 4096R / 3F48 0B8C C385 AD41 9E28 006A 7B1F 5490 72B7 4923 `- Debian - when you have better things to do than fixing systems -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#392943: wmaker: Broken keyboard shortcuts with new default theme
Hi, Is not nice to change the configuration without ask. Nelson A. de Oliveira made a fair suggestion. [] -- Herbert Parentes Fortes Neto (hpfn) Linux user number 416100 Debian GNU/kFreeBSD (qemu) 0x9834F79E -- http://pgp.mit.edu/ pgptSdtvYroT5.pgp Description: PGP signature
Bug#392943: wmaker: Broken keyboard shortcuts with new default theme
Hi! On 10/19/06, Hubert Chan <[EMAIL PROTECTED]> wrote: The previous default keyboard shortcuts probably weren't a very good choice as a default anyways, as a few of them had a pretty high chance of conflicting with various applications. (e.g. a lot of applications use Alt+.) Is Alt+ used by other programs? I am using WindowMaker since one very old version of Red Hat (that I don't remember the version) and always used Alt+ to switch between the desktops. And I never needed to configure it to do this. The same thing with Debian. I don't think that it's a good choice to disable the keyboard shortcuts. At least there could be a debconf question saying "The new WindowMaker package has no default keyboard shortcuts enabled by default, but they can be enabled. Do you want to enable?" (something like that). If yes then the old config is installed and everything remains the same as before. If not, it will have the new behavior. Is it a fair suggestion? Best regards, Nelson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#392943: wmaker: Broken keyboard shortcuts with new default theme
The previous default keyboard shortcuts probably weren't a very good choice as a default anyways, as a few of them had a pretty high chance of conflicting with various applications. (e.g. a lot of applications use Alt+.) -- Hubert Chan - email & Jabber: [EMAIL PROTECTED] - http://www.uhoreg.ca/ PGP/GnuPG key: 1024D/124B61FA (Key available at wwwkeys.pgp.net) Fingerprint: 96C5 012F 5F74 A5F7 1FF7 5291 AF29 C719 124B 61FA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#392943: wmaker: Broken keyboard shortcuts with new default theme
Hello Gürkan,
On Sun, Oct 15, 2006 at 03:39:26AM +0200, Gürkan Sengün wrote:
> I disagree with your grave severity. The software is perfectly usable
> without
Yes, the severity I picked might be a bit out of proportion.
Please feel free to downgrade it to a sensible choice.
> the "so called" "standard" configuration that you say is "default" by
> Window Maker.
Maybe I should clarify as to what I meant with "default" configuration:
The global configuration as shipped with the Debian package, not the
unaltered upstream one.
> >After an initial shock over the new default theme (which this bug
> >does not
> >mean to put in question), I found the WindowMaker keyboard shortcuts,
> >for
> >example for switching workspaces, not working at all.
>
> are you sure they work if you take the upstream tarball and build it?
> you can set them in WPrefs, the 5th icon from the right.
I did not consider building wmaker from pristine upstream upstream
source or in fact any source. This bug simply means to compare the
previous Debian package version with the current one.
After your suggestion, I tried with a fresh user account and found the
same behaviour, namely missing keyboard bindings. For clarification,
I attached the global and a pristine user configuration.
It is of course very easy for a user to assign keyboard bindings with
WPref or wmakerconf or by any other means, but isn't this exactly the
purpose of a default configuration, i.e. to provide sane defaults
for all configuration options needed for proper usage of a package?
The current Debian config should really include all the previous
config options (that is, the missing options as found in the file
'debian/WindowMaker.default' in source package version 0.92.0-5.3),
while keeping the new NeXTstep theme.
(Regarding the theme: You are absolutely right, my comment on the
previous and the current theme was absolutely subjective, and not
meant to offend anybody.)
Regards,
Peter
{
LargeDisplayFont = "-*-helvetica-bold-r-normal-*-24-*-*-*-*-*-*-*";
HighlightColor = white;
FTitleColor = white;
MenuTextFont = "-*-helvetica-bold-r-normal-*-12-*-*-*-*-*-*-*";
WorkspaceBack = (
spixmap,
"/usr/share/WindowMaker/Backgrounds/debian.tiff",
gray20
);
UTitleBack = (solid, "rgb:aa/aa/aa");
IconTitleFont = "-*-helvetica-bold-r-normal-*-9-*-*-*-*-*-*-*";
PTitleBack = (solid, gray40);
WindowTitleFont = "-*-helvetica-bold-r-normal-*-12-*-*-*-*-*-*-*";
UTitleColor = black;
ClipTitleFont = "Verdana:bold:pixelsize=10";
MenuDisabledColor = gray40;
MenuStyle = normal;
MenuTextBack = (solid, "rgb:aa/aa/aa");
PTitleColor = white;
IconBack = (dgradient, "rgb:a6/a6/b6", "rgb:51/55/61");
DisplayFont = "-*-helvetica-bold-r-normal-*-12-*-*-*-*-*-*-*";
MenuTitleBack = (solid, black);
FTitleBack = (solid, black);
TitleJustify = center;
CClipTitleColor = gray20;
ResizebarBack = (solid, "rgb:aa/aa/aa");
MenuTextColor = black;
ClipTitleColor = black;
IconTitleBack = black;
HighlightTextColor = black;
IconTitleColor = white;
MenuTitleFont = "-*-helvetica-bold-r-normal-*-12-*-*-*-*-*-*-*";
MenuTitleColor = white;
}
{
FTitleColor = white;
MenuTitleBack = (solid, black);
MenuDisabledColor = gray40;
IconTitleBack = black;
FTitleBack = (solid, black);
ClipTitleFont = "Verdana:bold:pixelsize=10";
ClipTitleColor = black;
IconTitleFont =
"helvetica:bold:pixelsize=9:xlfd=-*-helvetica-bold-r-normal-*-9-*-*-*-*-*-*-*";
HighlightColor = white;
WindowTitleFont =
"helvetica:bold:pixelsize=12:xlfd=-*-helvetica-bold-r-normal-*-12-*-*-*-*-*-*-*";
MenuTextBack = (solid, "rgb:aa/aa/aa");
LargeDisplayFont =
"helvetica:bold:pixelsize=24:xlfd=-*-helvetica-bold-r-normal-*-24-*-*-*-*-*-*-*";
CClipTitleColor = gray20;
MenuStyle = normal;
ResizebarBack = (solid, "rgb:aa/aa/aa");
DisplayFont =
"helvetica:bold:pixelsize=12:xlfd=-*-helvetica-bold-r-normal-*-12-*-*-*-*-*-*-*";
IconTitleColor = white;
TitleJustify = center;
MenuTextColor = black;
PTitleBack = (solid, gray40);
IconBack = (dgradient, "rgb:a6/a6/b6", "rgb:51/55/61");
MenuTitleColor = white;
UTitleColor = black;
MenuTitleFont =
"helvetica:bold:pixelsize=12:xlfd=-*-helvetica-bold-r-normal-*-12-*-*-*-*-*-*-*";
UTitleBack = (solid, "rgb:aa/aa/aa");
PTitleColor = white;
MenuTextFont =
"helvetica:bold:pixelsize=12:xlfd=-*-helvetica-bold-r-normal-*-12-*-*-*-*-*-*-*";
WorkspaceBack = (spixmap, "/usr/share/WindowMaker/Backgrounds/debian.tiff",
gray20);
HighlightTextColor = black;
}
Bug#392943: wmaker: Broken keyboard shortcuts with new default theme
Hello Peter I disagree with your grave severity. The software is perfectly usable without the "so called" "standard" configuration that you say is "default" by Window Maker. After an initial shock over the new default theme (which this bug does not mean to put in question), I found the WindowMaker keyboard shortcuts, for example for switching workspaces, not working at all. are you sure they work if you take the upstream tarball and build it? you can set them in WPrefs, the 5th icon from the right. This does not come as a surprise, given that most configuration options have vanished in '/etc/Defaults/WindowMaker'. Please revert to the previous, working default configuration. Regards, Peter p.s. On a side note, why is the wmaker package not allowed to ship with a Debian-inspired theme by default (see bug #286344)? As a default, the Debian theme looked much better who says it's not allowed to ship a debian-inspired theme by default? did you even try it with an account that has no GNUstep directory? It does have a debian theme, just not the one it used to have. "THE" debian theme? your opinion is pretty subjective, and i disagree to it. the brown was very brown... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#392943: wmaker: Broken keyboard shortcuts with new default theme
Package: wmaker Version: 0.92.0-6 Severity: grave Justification: renders package unusable After an initial shock over the new default theme (which this bug does not mean to put in question), I found the WindowMaker keyboard shortcuts, for example for switching workspaces, not working at all. This does not come as a surprise, given that most configuration options have vanished in '/etc/Defaults/WindowMaker'. Please revert to the previous, working default configuration. Regards, Peter p.s. On a side note, why is the wmaker package not allowed to ship with a Debian-inspired theme by default (see bug #286344)? As a default, the Debian theme looked much better than the ugly "NeXTSTEP" theme found in most other distributions :-). -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (400, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-maia Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages wmaker depends on: ii cpp 4:4.1.1-11 The GNU C preprocessor (cpp) ii libc62.3.6.ds1-6 GNU C Library: Shared libraries ii libfontconfig1 2.4.1-2 generic font configuration library ii libwraster3 0.92.0-6Shared libraries of Window Maker r ii libx11-6 2:1.0.3-1 X11 client-side library ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar ii libxft2 2.1.8.2-8 FreeType-based font drawing librar ii libxinerama1 1:1.0.1-4.1 X11 Xinerama extension library wmaker recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
