darcs patch: add modules to deal with Workspaces (select, etc) by n...

Hi all,
This patch allows ion3-style selection of workspace and creation of new
named workspaces. Also allows you to do stuff like move a window to a
named workspace, interactively selecting this workspace by name.
David
Tue Oct 16 18:33:47 EDT 2007 David Roundy

On 10/17/07, David Roundy
Hi all,
This patch allows ion3-style selection of workspace and creation of new named workspaces. Also allows you to do stuff like move a window to a named workspace, interactively selecting this workspace by name.
David
Tue Oct 16 18:33:47 EDT 2007 David Roundy
* add modules to deal with Workspaces (select, etc) by name using XPrompt.
You are quick. :) And this feature works nicely! There is no way to rename current workspace, is there? Anyway, DynamicWorkspaces.hs is very useful *already*. Thank you, David. -- vvv

On Wed, Oct 17, 2007 at 11:58:46AM +0300, Valery V. Vorotyntsev wrote:
On 10/17/07, David Roundy
wrote: Hi all,
This patch allows ion3-style selection of workspace and creation of new named workspaces. Also allows you to do stuff like move a window to a named workspace, interactively selecting this workspace by name.
David
Tue Oct 16 18:33:47 EDT 2007 David Roundy
* add modules to deal with Workspaces (select, etc) by name using XPrompt. You are quick. :) And this feature works nicely!
You're welcome! :)
There is no way to rename current workspace, is there? Anyway, DynamicWorkspaces.hs is very useful *already*.
That's next on my list (workspace renaming), but I really shouldn't get to it today, as I have some debugging of darcs that I need to do that probably will take all day.
Thank you, David.
You're welcome! -- David Roundy Department of Physics Oregon State University

On 10/17/07, David Roundy
wrote: That's next on my list (workspace renaming), but I really shouldn't get to it today, as I have some debugging of darcs that I need to do that probably will take all day.
Changes to DynamicWorkspaces.hs:
Thu Oct 18 17:56:04 EEST 2007 David Roundy
* add function to rename workspaces.
I haven't found this patch in mailing list, anyway... It works, it's lovely! Very useful. :) BTW, could someone tell me, why does , ((modMask .|. shiftMask, xK_a), renameWorkspace defaultXPConfig) work and , ((modMask, xK_A), renameWorkspace defaultXPConfig) (no shift, the capital `A') does not? -- vvv

On Thu, Oct 18, 2007 at 07:23:15PM +0300, Valery V. Vorotyntsev wrote:
On 10/17/07, David Roundy
wrote: That's next on my list (workspace renaming), but I really shouldn't get to it today, as I have some debugging of darcs that I need to do that probably will take all day.
Changes to DynamicWorkspaces.hs:
Thu Oct 18 17:56:04 EEST 2007 David Roundy
* add function to rename workspaces. I haven't found this patch in mailing list, anyway...
I didn't email it, because I was afraid of swamping the list. Would you (and others) prefer to get emails of patches that introduce new features?
It works, it's lovely! Very useful. :)
Indeed, it's a little shocking how often I've renamed my workspaces since writing this code. :) A (hopefully) useful feature is that if you rename a workspace to an existing workspace name, then the two workspaces get merged. I haven't tested this feature yet, so I haven't documented it, but it seems like it ought to have good uses, and will perhaps make removeWorkspace obsolete.
BTW, could someone tell me, why does , ((modMask .|. shiftMask, xK_a), renameWorkspace defaultXPConfig) work and , ((modMask, xK_A), renameWorkspace defaultXPConfig) (no shift, the capital `A') does not?
Not me... (and not because I'm being unfriendly, either) -- David Roundy Department of Physics Oregon State University

On Oct 18, 2007, at 13:16 , David Roundy wrote:
On Thu, Oct 18, 2007 at 07:23:15PM +0300, Valery V. Vorotyntsev wrote:
BTW, could someone tell me, why does , ((modMask .|. shiftMask, xK_a), renameWorkspace defaultXPConfig) work and , ((modMask, xK_A), renameWorkspace defaultXPConfig) (no shift, the capital `A') does not?
Not me... (and not because I'm being unfriendly, either)
Because xmonad listens on untranslated key events, whereas xK_A is a translated key event (the translation absorbing the shift status). This is also why there are problems when numlock/capslock are engaged: translation normally removes those, but the window manager bindings operate at a lower level. Note that, while xmonad could be changed to operate on translated events, that could cause other problems: notably, for those of us who can't allocate e.g. a Windows key to xmonad, we would lose the ability to pass through modifier bindings that xmonad itself doesn't use. -- brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allbery@kf8nh.com system administrator [openafs,heimdal,too many hats] allbery@ece.cmu.edu electrical and computer engineering, carnegie mellon university KF8NH

On Thu, Oct 18, 2007 at 04:53:29PM -0400, Brandon S. Allbery KF8NH wrote:
On Oct 18, 2007, at 13:16 , David Roundy wrote:
On Thu, Oct 18, 2007 at 07:23:15PM +0300, Valery V. Vorotyntsev wrote:
BTW, could someone tell me, why does , ((modMask .|. shiftMask, xK_a), renameWorkspace defaultXPConfig) work and , ((modMask, xK_A), renameWorkspace defaultXPConfig) (no shift, the capital `A') does not?
Not me... (and not because I'm being unfriendly, either)
Because xmonad listens on untranslated key events, whereas xK_A is a translated key event (the translation absorbing the shift status). This is also why there are problems when numlock/capslock are engaged: translation normally removes those, but the window manager bindings operate at a lower level.
Note that, while xmonad could be changed to operate on translated events, that could cause other problems: notably, for those of us who can't allocate e.g. a Windows key to xmonad, we would lose the ability to pass through modifier bindings that xmonad itself doesn't use.
Thanks for that clear explanation! -- David Roundy Department of Physics Oregon State University

On 10/18/07, Brandon S. Allbery KF8NH
Because xmonad listens on untranslated key events, whereas xK_A is a translated key event (the translation absorbing the shift status). This is also why there are problems when numlock/capslock are engaged: translation normally removes those, but the window manager bindings operate at a lower level.
Thank you, Brandon. :) -- vvv

On 10/18/07, David Roundy
I didn't email it, because I was afraid of swamping the list. Would you (and others) prefer to get emails of patches that introduce new features?
Perhaps, the better place would be `XMonadContrib/NEWS' file.
A (hopefully) useful feature is that if you rename a workspace to an existing workspace name, then the two workspaces get merged. I haven't tested this feature yet, so I haven't documented it, but it seems like it ought to have good uses, and will perhaps make removeWorkspace obsolete.
You never know until you try. :) I haven't met such kind of feature in other... places. Looks interesting. -- vvv
participants (3)
-
Brandon S. Allbery KF8NH
-
David Roundy
-
Valery V. Vorotyntsev