On Mon, Jun 11, 2007 at 03:55:50PM -0500, Spencer Janssen wrote:

...

I don't know whether we want to change the default bindings here, but mod-Q I find highly annoying, in that it conflicts with one of my favorite emacs commands. It seems like Escape should work as well here.

I think we'll stick with mod-q for now. In general, it is very difficult to find key combinations that don't offend emacs users ;). Perhaps you want to use an alternate key for mod instead?

I could do that, but I imagine it's a bit of a pain, since I use different keyboards (on different computers) with the same xmonad. And it still doesn't really solve the problem, since I have alt keys located in different locations on different keyboards (I suppose I could remap that as well, but then I'd have to remember where it's been remapped). I think I'll just stick with moving this to Escape. I'm sort of curious: why is it that we use the number keys rather than the Fn keys to go to workspaces? It seems like those F1-F12 keys are pretty under-used, and I personally use the number keys pretty often (yes, an emacs user...). -- David Roundy Department of Physics Oregon State University

On Tue, Jun 12, 2007 at 07:48:14AM +0300, Avi Rozen wrote:

David Roundy wrote:

...

On Mon, Jun 11, 2007 at 03:55:50PM -0500, Spencer Janssen wrote:

...

...

I don't know whether we want to change the default bindings here, but mod-Q I find highly annoying, in that it conflicts with one of my favorite emacs commands. It seems like Escape should work as well here.

I think we'll stick with mod-q for now. In general, it is very difficult to find key combinations that don't offend emacs users ;). Perhaps you want to use an alternate key for mod instead?

I could do that, but I imagine it's a bit of a pain, since I use different keyboards (on different computers) with the same xmonad. And it still doesn't really solve the problem, since I have alt keys located in different locations on different keyboards (I suppose I could remap that as well, but then I'd have to remember where it's been remapped). I think I'll just stick with moving this to Escape.

I'm sort of curious: why is it that we use the number keys rather than the Fn keys to go to workspaces? It seems like those F1-F12 keys are pretty under-used, and I personally use the number keys pretty often (yes, an emacs user...).

Is there a way to specify a prefix key instead of just a set of modifiers? This is how I can use emacs (alt-x etc.)/screen (ctrl-a)/ion3 (alt-k)/ratpoison in vncviewer (ctrl-t) all together in the same session...

Use the 'submap' contrib module. BTW, almost everyone here uses WindowsLogo for xmonad and Alt for Meta (in programs) - it's easy to get used to. Stefan

David Glasser wrote:

On 6/12/07, Stefan O'Rear wrote:

...

On Tue, Jun 12, 2007 at 07:48:14AM +0300, Avi Rozen wrote:

...

Is there a way to specify a prefix key instead of just a set of modifiers? This is how I can use emacs (alt-x etc.)/screen (ctrl-a)/ion3 (alt-k)/ratpoison in vncviewer (ctrl-t) all together in the same session...

Use the 'submap' contrib module.

Alternatively, if your memory is too small to remember bindings at all, the 'commands' contrib module achieves a similar goal.

--dave

Took me a while to figure out how enable the 'commands' contrib module. The instructions say to add the following lines to Config.hs-boot : import XMonad (X) workspaces :: Int commands :: [(String, X ())] But I get the following error when building: parse error on input `import' I got it working by removing the import line and moving the declaration of commands to Config.hs: commands :: [(String, X ())] commands = defaultCommands Seems to work fine, but is this the right thing to do? Thanks, Avi. -- "If you are an expert in the intricacies of C++, please consider this knowledge a kind of martial art - something a real master never uses."

Andrea Rossato wrote:

in Config.hs-boot import XMonad is already present. It's enough if you just add: workspaces :: Int commands :: [(String, X ())]

here you can have a better understanding of what hs-boot files are needed for: http://haskell.org/ghc/docs/6.6/html/users_guide/separate-compilation.html#m...

ciao andrea

Thanks for the pointer. It's a bit over my head though (just got to page 3 of the "gentle(?) introduction" ...) - but I think I get the point (seems similar to the role of forward declarations in C/C++). However, if I don't move the type signature declaration of commands to Config.hs I get the following warning: Warning: Definition but no type signature for `commands' I guess something is still missing. Thanks, Avi. -- "If you are an expert in the intricacies of C++, please consider this knowledge a kind of martial art - something a real master never uses."