[dwm] maximize problem

2007-12-09 Thread pancake
I find quite anoying the maximize command. Because allows you to hide windows to the user. I don't know if the right solution for this would be to make maximize act as monocle, or avoid changing the focus of the maximized client for the current tag, or making the maximized flag be inheritable for

Re: [dwm] maximize problem

2007-12-09 Thread Anselm R. Garbe
On Sun, Dec 09, 2007 at 11:04:24AM +0100, pancake wrote: I find quite anoying the maximize command. Because allows you to hide windows to the user. I don't know if the right solution for this would be to make maximize act as monocle, or avoid changing the focus of the maximized client for the

Re: [dwm] cycling through clients

2007-12-09 Thread Felix Leckow
On Sun, Dec 09, 2007 at 01:49:27AM +0100, Engin Tola wrote: comments are welcome. I've bound next_client and prev_client to Shift-j and Shift-k respectively, and I think this functionality integrates quite nicely with dwm. It saves a keystroke zooming in the last client in the stack. :) I

Re: [dwm] cycling through clients

2007-12-09 Thread Anselm R. Garbe
On Sun, Dec 09, 2007 at 11:44:03AM +, Felix Leckow wrote: On Sun, Dec 09, 2007 at 01:49:27AM +0100, Engin Tola wrote: comments are welcome. I've bound next_client and prev_client to Shift-j and Shift-k respectively, You never type J or K? ;) Regards, -- Anselm R. Garbe

Re: [dwm] cycling through clients

2007-12-09 Thread Enno Gottox Boland
You never type J or K? ;) that's what capslock is good for :) -- http://www.gnuffy.org - Real Community Distro http://www.gnuffy.org/index.php/GnuEm - Gnuffy on Ipaq (Codename Peggy)

[dwm] Xinerama support

2007-12-09 Thread Anselm R. Garbe
Hi there, could you imagine that there is a way that dwm could be used in a Xinerama environment and how that might look like? Regardless if that is necessary or not for mainstream dwm, I see the following possibilities: - aim multihead setup (distinct bars, tag sets and layouts for each

Re: [dwm] Xinerama support

2007-12-09 Thread Anselm R. Garbe
On Sun, Dec 09, 2007 at 12:54:00PM +0100, Anselm R. Garbe wrote: could you imagine that there is a way that dwm could be used in a Xinerama environment and how that might look like? Regardless if that is necessary or not for mainstream dwm, I see the following possibilities: - aim

Re: [dwm] Xinerama support

2007-12-09 Thread Anselm R. Garbe
On Sun, Dec 09, 2007 at 12:59:21PM +0100, Maarten Maathuis wrote: A shared tagging setup, but a flag to indicate primary or secondary head. Sort of like adding an extra dimension to dwm. That sounds like a simple solution, but still very similiar to aiming the multihead setup. But how to

Re: [dwm] Xinerama support

2007-12-09 Thread David Tweed
On Dec 9, 2007 11:54 AM, Anselm R. Garbe [EMAIL PROTECTED] wrote: could you imagine that there is a way that dwm could be used in a Xinerama environment and how that might look like? [A collective groan goes around as people realise I'm still around :-) ] Yes and

Re: [dwm] OT: which or type or what else?

2007-12-09 Thread markus schnalke
Anselm R. Garbe [EMAIL PROTECTED] wrote: Both, type(1) and which(1) are not POSIX compliant and might be absent. Though I'd use which(1) if you don't want to go the way used by dmenu_path for instance. Thanks to you and the others who answered. I will use `which' now. meillo

Re: [dwm] weird screen height problem

2007-12-09 Thread Kurt H Maier
They're xterm instances, aren't they. On Dec 9, 2007 8:28 AM, Engin Tola [EMAIL PROTECTED] wrote: Hi everyone, When I open more than 1 client in the tile() layout mode, the total height of the display is changing with every client I open like this: +-++ | || |

Re: [dwm] Xinerama support

2007-12-09 Thread Anselm R. Garbe
On Sun, Dec 09, 2007 at 02:12:48PM +0100, Engin Tola wrote: pancake [EMAIL PROTECTED] writes: Recently I buyed a 20 16:10 tft, and i really feel interesting to have xinerama with dwm. Thinking about that I got the idea that we should just store two variables: - selected tag for each

Re: [dwm] weird screen height problem

2007-12-09 Thread Anselm R. Garbe
Try this in config.h: #define RESIZEHINTS False However, you only delegate the problem to the client app, and you will get other side-effects from e.g. xterm then. The behavior you notice is no bug/problem, but dwm provides two ways two workaround, the default one which leads to some non-used

Re: [dwm] Xinerama support

2007-12-09 Thread Kurt H Maier
Seems like this would call for an alternative layout to be #included, which allows for the large-resolution screen-spanning desktop, and it could just emulate multihead by tiling / maximizing windows to those sections of the desktop which are displayed on each screen. These boundaries could be

Re: [dwm] Xinerama support

2007-12-09 Thread Antoni Grzymala
Anselm R. Garbe dixit (2007-12-09, 18:27): [snip] One idea I was playing in my mind with for a while was assigning some of the tags to the other display and move between the displays seamlessly as if moving between the tags - I guess I'll still have the problem of not being able to move