semantics of move command

asked 2013-09-25 20:11:12 +0000

yoav
3 ●2 ●2 ●3

Can you elaborate on the semantics of the "move" commands? it is not entirely clear to me how the movement relate to the tree structure.

I figured out that move left/right will either replace the container with its sibling, or get absorbed into the sibling, depending on the split mode of the sibling (is that correct?)

But I am really confused as to what move up/down do, as far as the tree structure is concerned.

answered 2013-09-25 20:17:29 +0000

Michael
3081 ●13 ●28 ●50 http://i3wm.org/

See http://www.youtube.com/watch?v=AWA8Pl... and toy around with it, and/or read the source.

edit flag offensive delete link

Comments

Thanks. It seems like the move/focus commands are mostly about "doing the right thing" with respect to the screen layout, but is not very well defined intuitively (at least for my intuition) for tree manipulation... I'd like to play with more direct tree manipulation -- is it possible via ipc?

yoav ( 2013-09-25 20:40:14 +0000 )edit

It’s not. The commands that are exposed via the IPC interface are exactly what is documented in the userguide, i.e. what is available for you to bind on your keys.

Michael ( 2013-09-26 16:43:41 +0000 )edit

Will you consider adding an IPC command that will receive a new json tree and replace the existing one? (or is the internal representation more complex than what is exposed?)

yoav ( 2013-09-26 16:56:37 +0000 )edit

add a comment

semantics of move command

1 answer

Comments

Question Tools

Stats

Related questions