| Commit message (Collapse) | Author | Age |
| ... | |
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Right now, Mosaic operate on the windows itself. But this means that
swapping windows can act very unintuitively. This wrapper changes
mosaci to work on window /positions/ rather than windows themselves,
so the window in position 1 will always be the same size, and when moved
to position 2, it will inherit that position's size.
There's still some buggy behavior, but it is in general much more
intuitive than it was before.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
It's not the best thing in the world, but it should help keep things in
a consistent state when dealing with many multi-stroke bindings.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
sure how I feel about it right now; it'll take some getting used to.
|
| | |
| |
| |
| | |
than a LayoutModifier.
|
| | |
| |
| |
| | |
sure how I feel about it, but Imma try it out
|
| | |
| |
| |
| |
| |
| |
| | |
This is mostly an academic exercise, as there's probably not much reason
to put a hole in the layout, but I must admit that sometimes is
aesthetically pleasing to see a little more desktop wallpaper in some
cases.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
This also combines the two into a single type.
|
| | | |
|
| | |
| |
| |
| |
| | |
Unfortunately it's a little hacky how this ended up working, but I don't
have a great solution yet.
|
| | |
| |
| |
| | |
Much cleaner.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is using xdotool to send a keystroke, which is not the best way to
do this. In fact, a proper server protocol would be better, but this is
how it is at the momement unfortunately.
There is a problem where trying to use xdotool to send a key for a
multibyte character will cause all events to freeze on XMonad for some
reason, so these actions are guarded so only 'a-zA-Z0-9' are clickable
and the rest are not, which is /okay/, I don't use unicode workspaces
that often.
|
| | |
| |
| |
| | |
stack file.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Now LayoutZipper can be circular, which means layout switching operates
semantically identically to how it did before making the typesafe
selector.
The selector was very much an acedemic exercise, but since it is working
as expect, I will keep it. I like the type-safety and it can be used as
an example for similar exercises.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
So, when doing something like a "zoom", it will only affect the current
layout. Before a "zoom" would be persistent across all layouts, now it
will only occur on the current layout.
I'm still trying to decide if I like it this way or not. It looks like
it'll have minimal impact on things. I don't use different layouts that
often anyway.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |\ |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This lets the user cycle between past windows. The rules for when a
window gets added to the history is the same as when a window is
considered the last marked.
In fact, now all the last mark does is swap the current window with the
previous one in the history.
|
| | |/ |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The hope is to get to a point where documentation can be automatically
generated for key bindings, while keeping as much of the existing
DSL unchanged as possible.
The goal is to have something like:
bind xK_h $ do
doc "Set focus to the next window in the stack"
justMod nextWindow
doc "Swap this window with the next window in the stack."
shiftMod shiftNextWindow
Then "theoretically" a markdown/latex/text file can be generated with
documentation for each of those bindings and have the documentation
automatically update if the keys change.
|
| | | |
|
| | |
| |
| |
| | |
window-specific bindings
|
| | | |
|
| | |
| |
| |
| | |
Keys.hs file.
|