On Tue, Oct 9, 2012 at 1:43 PM, Jacek Generowicz <jacek.generowicz@cern.ch> wrote:
OK, I'll have a go. I won't paste my whole config file, as that could
well overwhelm you with irrelevant nonsense (and I'm embarassed about
how much of a mess some of it is :-).
Wow, thanks for the comprehensive explanation! I actually figured it out myself, but your config looks very interesting and I'll certainly see what more I can learn from it.
Here's what I did:
1. Define two custom prompts:
myXPConfigSelect = defaultXPConfig
{ autoComplete = Just 0
, showCompletionOnTab = True
}
myXPConfigNew = defaultXPConfig
{ autoComplete = Nothing
, showCompletionOnTab = True
}
(I have some more settings but they aren't relevant here.)
2. Bind keys for switching and creating workspaces, in the latter case it doesn't autocomplete:
-- Switch workspace
, ((modm , xK_h), selectWorkspace myXPConfigSelect)
-- Move window to workspace
, ((modm .|. shiftMask, xK_h), withWorkspace myXPConfigSelect (windows . W.shift))
-- Create new workspace
, ((modm , xK_n), selectWorkspace myXPConfigNew)
-- Move window to newly created workspace
, ((modm .|. shiftMask, xK_n), withWorkspace myXPConfigNew (windows . W.shift)
Works like a charm. I'm still experimenting with which keys to use, but otherwise I'm pretty satisfied with this.
On Wed, Oct 10, 2012 at 12:04 AM, Pablo Olmos de Aguilera C. <pablo@glatelier.org> wrote:
That's sounds great. I don't understand how (or where) in the screen
you can list all those workspaces without going crazy or memorizing
everything. I tried to use DWS and every new workspace is added before
the first one (which seems a bit odd to me) and after a while dzen was
totally filled, so I couldn't keep track of everything.
On Wed, Oct 10, 2012 at 12:26 AM, Carlos López Camey
<c.lopez@kmels.net> wrote:
FWIW, I would like a setup where I can use Actions.CycleWS functions
without going through empty workspaces. This could be
simulated with workspaces on the fly.