twin/xmonad-contrib
1
0
Fork 0
mirror of https://github.com/xmonad/xmonad-contrib.git synced 2025-05-19 03:20:21 -07:00
Code Issues Packages Projects Releases Wiki Activity

Don't auto-delete workspaces

Browse Source 
* Previously I was removing empty workspaces after switching away from
    them, but this seemed to cause a bug when workspaces were defined
    statically in your XMonad configuration.

  * Next up: a function to delete an existing project.
This commit is contained in:
Peter Jones 2015-12-02 20:07:37 -07:00
parent ea8e0ea7b6
commit f35083da9f
1 changed files with 4 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
XMonad/Actions/DynamicProjects.hs
View File

@ -76,13 +76,13 @@ import qualified XMonad.Util.ExtensibleState as XS
-- or further configure the workspace/project.
--
-- When using the @switchProjectPrompt@ function, workspaces are
-- created and deleted as necessary. This means you can create new
-- project spaces on the fly as needed. (These dynamic projects are
-- created as needed. This means you can create new project spaces
-- (and therefore workspaces) on the fly. (These dynamic projects are
-- not preserved across restarts.)
--
-- Additionally, frequently used projects can be configured statically
-- in your XMonad configuration. Doing so allows you to configure the
-- start-up hook.
-- per-project start-up hook.
--------------------------------------------------------------------------------
-- $usage
@ -213,10 +213,7 @@ switchProject p = do
when (null ws && isNothing (projectStartHook oldp)) $
XS.modify (\s -> s {projects = Map.delete name $ projects s})
-- Remove the old workspace (if empty) and activate the new
-- workspace. The project will be activated by the log hook.
removeEmptyWorkspace
addWorkspace (projectName p)
appendWorkspace (projectName p)
--------------------------------------------------------------------------------
-- | Prompt for a project name and then switch to it. Automatically