Musca (Tiling Window Manager)

Frabato · 2009-06-30 21:16:26

Hi All,

I'm having trouble keybinding the Alt key (the last two commands)

bind on Mod4+F5  exec opera
bind on Mod4+F6  exec thunderbird
bind on Mod4+F7  exec gmm
bind on Mod4+F8  exec xine
bind on Mod4+F9  exec rox
bind on Mod4+F10 exec sudo rox
bind on Mod4+Mod1+r exec sudo reboot
bind on Mod4+Alt+s exec sudo shutdown -h now

As you can see I've tried Mod1 and Alt. I'm sure that I'm making a simple silly mistake but rather than guessing I'll ask for help. Also, am I correct in assuming that .musca_start will override the settings in config.h. I have looked but cannot find config.h. Is it only used at compile time?

Thanks

Theomachos · 2009-07-13 15:16:23

I really like this wm
Floating + manual tiling is just what I wanted. However... is it (or would it be) possible to move/resize windows in stacking mode using the keyboard ? I don't really like the rodent....

Procyon · 2009-07-13 17:33:52

@Theomachos: wmctrl can do that and works great with musca

This script should work in theory, but for me wmctrl -G -l returns X and Y values that are doubled and +2 (my border size is also 2). Maybe that's just something about my settings though, else you have to insert
((x-=2))
((y-=2))
((x/=2))
((y/=2))

#! /bin/bash
wmctrl -G -l | head -n1 | while read ID desk x y width height rest; do
[ $1 = left ] && ((x-=50))
[ $1 = right ] && ((x+=50))
[ $1 = up ] && ((y-=50))
[ $1 = down ] && ((y+=50))
[ $1 = wide ] && ((width+=50))
[ $1 = narrow ] && ((width-=50))
[ $1 = tall ] && ((height+=50))
[ $1 = short ] && ((height-=50))
wmctrl -i -r $ID -e 0,$x,$y,$width,$height
done

Procyon · 2009-08-01 20:59:03

I have a feature request: undoable undo, so you can quickly toggle between two states.

lino · 2009-08-02 16:22:16

I'd also appreciate to switch between two states!

Procyon · 2009-08-03 14:08:35

I think I got it, in function group_undo() (line 2088)
After char *layout = stack_pop(g->states);
Add while (g->states->depth)
free(stack_pop(g->states));
stack_push(g->states, group_dump(g));

So the entire function

void group_undo()
{
    group *g = heads->groups;
    if (g->states->depth > 0)
    {
        char *layout = stack_pop(g->states);
        while (g->states->depth)
            free(stack_pop(g->states));
        stack_push(g->states, group_dump(g));
        group_load(g, layout); free(layout);
    }
    else    um("nothing to undo for %s", g->name);
}

I didn't realize this before but undo works with a stack (I thought it was behaving randomly after 1)
I don't think the stack is used elsewhere, so I added the clearing (the while loop is from group_destroy)

yvonney · 2009-08-05 09:40:55

However... is it (or would it be) possible to move/resize windows in stacking mode using the keyboard ? I don't really like the rodent.... wink

DWM couldn't do this i think ...?
I would love to have the option to NOT use the mouse. It's not currently possible/sensible ??
Interested to know.

OH ! Procyon !! Interesting!!!

Last edited by yvonney (2009-08-05 09:41:54)

Shender · 2009-08-27 22:51:28

Hi everybody,

I'm using musca for several days and I really like this WM. So I have (as a warmup) one question: is there any way to "glue" application to the some certain frame? For example, I'd like to write such config that evince should start only in the group "book".

Inxsible · 2009-10-13 01:08:22

I use some of the default keybindings for musca for other purposes. I was in the habit of using them and so did not want to re-learn new keys.

For eg. Mod4+w - shows windows in musca, so I changed it to Mod4+Shift+w because I use Mod4+w to start the web browser and so on..

I have all the bindings in my .musca_start and applications keybindings in .xbindkeysrc

However, all the keybindings that are common between the two -- default to the musca action instead of the app. For eg. When I hit Mod4+s, I want screen to start up, but I simply go into stacking mode. This is annoying as I have to start xbindkeys again. After that it works correctly.

I have tried starting xbindkeys in .xinitrc (with an &) and also in .musca_start, but the issue persists.

Is there anyway, I can make sure that the xbindkeysrc takes precedence over the default musca keys?

Here are my .xinitrc and .musca_start and .xbindkeysrc

.xinitrc

#!/bin/sh
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)
#


 eval `cat $HOME/.fehbg` &
 #xbindkeys &
 sleep 1
 exec musca >> /dev/null

# exec ck-launch-session openbox-session

#Musca keybindings
bind on Mod4+Shift+h hsplit 1/2
bind on Mod4+Shift+v vsplit 1/2
bind on Mod4+Shift+r remove
bind on Mod4+Shift+o only
bind on Mod4+Shift+k kill
bind on Mod1+F4 kill
bind on Mod4+Shift+c cycle
bind on Mod1+Tab cycle
bind on Mod4+Left focus left
bind on Mod4+Right focus right
bind on Mod4+Up focus up
bind on Mod4+Down focus down
bind on Mod4+Next use (next)
bind on Mod4+Tab use (next)
bind on Mod4+Prior use (prev)
#bind on Mod4+Tab screen (next)
bind on Mod4+Shift+w switch window
bind on Mod4+Shift+g switch group
bind on Mod4+x shell
bind on Mod4+Shift+x command
bind on Mod4+Shift+d dedicate flip
bind on Mod4+Shift+a catchall flip
bind on Mod4+Shift+u undo
bind on Mod4+Shift+s stack flip
bind on Mod4+Shift+Left swap left
bind on Mod4+Shift+Right swap right
bind on Mod4+Shift+Up swap up
bind on Mod4+Shift+Down swap down
bind on Mod4+Control+Left resize left
bind on Mod4+Control+Right resize right
bind on Mod4+Control+Up resize up
bind on Mod4+Control+Down resize down
bind on Mod4+Shift+q quit
bind on Mod4+Shift+b border flip

#bindings to switch between groups
bind on Mod4+0 use 0
bind on Mod4+1 use 1
bind on Mod4+2 use 2
bind on Mod4+3 use 3
bind on Mod4+4 use 4
bind on Mod4+5 use 5
bind on Mod4+6 use 6
bind on Mod4+7 use 7
bind on Mod4+8 use 8
bind on Mod4+9 use 9

bind on Mod4+Shift+0 move 0
bind on Mod4+Shift+1 move 1
bind on Mod4+Shift+2 move 2
bind on Mod4+Shift+3 move 3
bind on Mod4+Shift+4 move 4
bind on Mod4+Shift+5 move 5
bind on Mod4+Shift+6 move 6
bind on Mod4+Shift+7 move 7
bind on Mod4+Shift+8 move 8
bind on Mod4+Shift+9 move 9

# dmenu settings
#set dmenu dmenu -b -i -nb '#333333' -nf '#a8a3f7' -fn 'terminus-10'
set dmenu dmenu -b -i -nb grey20 -nf '#a1b5cd' -fn '-*-dina-medium-r-normal-*-*-*-*-*-*-*-*-*'
#set dmenu dmenu -b -i -nb '#0A0A0A' -nf '#A0A0A0' -fn 'helvetica 9' -sb '#285577' -sf '#FFFFFF'



manage off stalonetray
manage off Conky

set window_open_frame empty
set window_open_focus 0
set group_close_empty 1


pad 0 0 0 16
exec stalonetray
exec xbindkeys
exec conky

vsplit 40%
hsplit 20%
exec skype

# For the benefit of emacs users: -*- shell-script -*-
###########################
# xbindkeys configuration #
###########################
#
# Version: 1.8.3
#
# If you edit this file, do not forget to uncomment any lines
# that you change.
# The pound(#) symbol may be used anywhere for comments.
#
# To specify a key, you can use 'xbindkeys --key' or
# 'xbindkeys --multikey' and put one of the two lines in this file.
#
# The format of a command line is:
#    "command to start"
#       associated key
#
#
# A list of keys is in /usr/include/X11/keysym.h and in
# /usr/include/X11/keysymdef.h
# The XK_ is not needed.
#
# List of modifier:
#   Release, Control, Shift, Mod1 (Alt), Mod2 (NumLock),
#   Mod3 (CapsLock), Mod4, Mod5 (Scroll).
#

# The release modifier is not a standard X modifier, but you can
# use it if you want to catch release events instead of press events

# By defaults, xbindkeys does not pay attention with the modifiers
# NumLock, CapsLock and ScrollLock.
# Uncomment the lines above if you want to pay attention to them.

#keystate_numlock = enable
#keystate_capslock = enable
#keystate_scrolllock= enable

# Examples of commands:

"xbindkeys_show" 
  control+shift + q

"gmrun"
    m:0x8 + c:68
    Alt + F2

"recorder"
    m:0x40 + c:56
    Mod4 + b
    
"conky"
    m:0x40 + c:54
    Mod4 + c

"easytag"
    m:0x40 + c:26
    Mod4 + e

"pcmanfm"
    m:0x40 + c:41
    Mod4 + f

"gvim"
    m:0x40 + c:42
    Mod4 + g

"skype"
   m:0x40 + c:31
    Mod4 + i

"lxappearance"
    m:0x40 + c:46
    Mod4 + l

"urxvt -e pstree.x11"
    m:0x40 + c:33
    Mod4 + p

"urxvt -e screen"
    m:0x40 + c:39
    Mod4 + s

"urxvt"
    m:0x40 + c:28
    Mod4 + t 

"vlc"
    m:0x40 + c:55
    Mod4 + v

"firefox"
    m:0x40 + c:25
    Mod4 + w

"firefox"
   m:0x0 + c:172
    XF86AudioPlay

"scrot"
    m:0x0 + c:107
    Print

# volume control
"ossmix vol +5"
    m:0x40 + c:112
    Mod4 + Prior

"ossmix vol -- -5"
    m:0x40 + c:117
    Mod4 + Next

"ossmix vol 0"
    m:0x40 + c:115
    Mod4 + End


# set directly keycode (here control + f with my keyboard)
#"xterm"
#  c:41 + m:0x4

# specify a mouse button
#"xterm"
#  control + b:2

#"xterm -geom 50x20+20+20"
#   Shift+Mod2+alt + s
#
## set directly keycode (here control+alt+mod2 + f with my keyboard)
#"xterm"
#  alt + c:0x29 + m:4 + mod2
#
## Control+Shift+a  release event starts rxvt
#"rxvt"
#  release+control+shift + a
#
## Control + mouse button 2 release event starts rxvt
#"rxvt"
#  Control + b:2 + Release

##################################
# End of xbindkeys configuration #
##################################

Last edited by Inxsible (2009-10-13 01:13:29)

Peasantoid · 2009-10-13 01:38:31

Inxsible: You can nuke keybindings with 'bind off ...'.

bind off Mod4+s

Inxsible · 2009-10-13 03:04:03

Peasantoid wrote:

Inxsible: You can nuke keybindings with 'bind off ...'.
bind off Mod4+s

So I'd have to do it for all the bindings eh?

Man.... that sucks !! Oh Well !

Thanks, I will try it out and let you know. The funny thing is that the bindings that are not common for musca work as expected. I guess its a race condition for the bindings and musca always wins.

EDIT : just realized that

bind off all

releases all keybindings. nice.

Last edited by Inxsible (2009-10-13 03:26:01)

Nnexxus · 2009-11-15 10:15:45

Hi all !

I've been using musca for a few days now, great piece of software !

However, I grew tired of launching the same apps each time, and manually placing them in the right group. I would like to launch several apps at startup, and organize them automatically. I managed to create all the groups I need and to apply the desired layouts on them, but I end up having all my clients in the default group at startup.

I browsed the documentation and wiki, but I just can't figure it out. As suggested in the wiki, I ran my startup programs from a script lauched by my .xinitrc. I even added a sleep command at the end of the script, just to make sure. Musca is launched afterward. I clearly see my clients pop up before musca is even started. But when musca boots up, the clients are all piled up in the default group.

Maybe someone could post a step-by-step guide in the wiki ? I guess I'm not the only new musca user that runs into this problem.

Procyon · 2009-11-15 11:00:51

Nnexxus: Version 0.9.23 introduced the feature of `exec` to make programs stay in the group they were launched at (since the window does not pop up immediately) which you should use to launch your windows in the .musca_start (after changing to the respective group), instead of say, launch all applications before (or after) musca in xinitrc, because that won't put applications in the right group unless you use a script that browses through them and moves them one by one.

http://aerosuidae.net/musca/Change_Log

Nnexxus · 2009-11-15 18:14:32

Thanks Procyon !

I guess I saw a problem where there was none... Your suggestion is much more simple than using an external script, I'll give it a try.

Inxsible · 2009-11-16 07:09:36

The change log for 0.9.22 mentions that the move command now creates a group if it doesn't exist. However, this does not work for me by default. Is there a setting that we need to set to get that working?

Note that it works for use, but not for move.

I am using 0.9.24 currently, but it does not work in .23 or .24.

Last edited by Inxsible (2009-11-16 07:11:02)

Procyon · 2009-11-16 08:48:06

@Inxsible: It works here. The code of com_window_to_group() is the same in .22 and .23, in .24 it is split up in functions, but the same thing is done.

How are you using it?

Inxsible · 2009-11-16 17:23:54

Procyon wrote:

@Inxsible: It works here. The code of com_window_to_group() is the same in .22 and .23, in .24 it is split up in functions, but the same thing is done.
How are you using it?

bind on Mod4+Shift+0 move 0
bind on Mod4+Shift+1 move 1
bind on Mod4+Shift+2 move 2
bind on Mod4+Shift+3 move 3
bind on Mod4+Shift+4 move 4
bind on Mod4+Shift+5 move 5
bind on Mod4+Shift+6 move 6
bind on Mod4+Shift+7 move 7
bind on Mod4+Shift+8 move 8
bind on Mod4+Shift+9 move 9

The above are my move usages. But when I hit Mod4+Shift+num, nothing happens except maybe a flicker of the cursor.

Last edited by Inxsible (2009-11-16 17:24:10)

Procyon · 2009-11-16 17:53:15

Groups are differentiated with ID and Name. You can't create a group with a specific ID.
E.g. you have one group, 0 - default, and run:
add 5 (makes a new group named '5' with ID 1)
use 0
move 5 (fails, there is no group with ID 5)
use 5 (makes a new group named '5' with ID 2)

The move command is just a bit smarter than use and add, because it checks if the name is a digit before creating. (I saw this in the source code too)

So just use a, b, c.

Inxsible · 2009-11-16 19:24:14

Procyon wrote:

Groups are differentiated with ID and Name. You can't create a group with a specific ID.
E.g. you have one group, 0 - default, and run:
add 5 (makes a new group named '5' with ID 1)
use 0
move 5 (fails, there is no group with ID 5)
use 5 (makes a new group named '5' with ID 2)
The move command is just a bit smarter than use and add, because it checks if the name is a digit before creating. (I saw this in the source code too)
So just use a, b, c.

So you are saying that I cannot name a group with numerals?

Procyon · 2009-11-16 19:37:00

Inxsible wrote:

So you are saying that I cannot name a group with numerals?

Not without a patch that disables all ID-based code.

Inxsible · 2009-11-16 19:39:50

Procyon wrote:

Inxsible wrote:
So you are saying that I cannot name a group with numerals?
Not without a patch that disables all ID-based code.

gotcha. Thanks. I will change the move to use alphanumeric names.

EnvoyRising · 2009-11-17 14:26:16

Is the flash settings dialog unresponsive for anyone else? (eg, navigate to any youtube video, right-click select "Settings" then try to click on any option).

I also experience similar behavior with WMII, I3 and a few other tilling window managers, but not DWM or floating windows managers (KWin, Metacity, openbox, etc).

If I am in fact the only one experiencing this behavior, how can I correct it?

Procyon · 2009-11-17 15:08:28

@EnvoyRising: This problem is discussed in a few other threads. There is an odd workaround: http://bbs.archlinux.org/viewtopic.php? … 11#p641411

skottish · 2009-11-18 01:41:27

I doesn't really matter either way, but I think that it may be better to start asking specific questions about musca in their own threads. I'm sure a number of you have remembered reading something somewhere in this thread and ended up scanning through hundreds of posts. I know that I've done it at least ten different times.

EnvoyRising · 2009-11-18 05:34:28

skottish wrote:

I doesn't really matter either way, but I think that it may be better to start asking specific questions about musca in their own threads. I'm sure a number of you have remembered reading something somewhere in this thread and ended up scanning through hundreds of posts. I know that I've done it at least ten different times.

Hmmm. Noted for future reference. I guess I get around this issue by subscribing to threads, but I could see it being harder to search for the existence o a known issue.

Thanks Proxy, I'll try it.

Arch Linux

#401 2009-06-30 21:16:26

Re: Musca (Tiling Window Manager)

#402 2009-07-13 15:16:23

Re: Musca (Tiling Window Manager)

#403 2009-07-13 17:33:52

Re: Musca (Tiling Window Manager)

#404 2009-08-01 20:59:03

Re: Musca (Tiling Window Manager)

#405 2009-08-02 16:22:16

Re: Musca (Tiling Window Manager)

#406 2009-08-03 14:08:35

Re: Musca (Tiling Window Manager)

#407 2009-08-05 09:40:55

Re: Musca (Tiling Window Manager)

#408 2009-08-27 22:51:28

Re: Musca (Tiling Window Manager)

#409 2009-10-13 01:08:22

Re: Musca (Tiling Window Manager)

#410 2009-10-13 01:38:31

Re: Musca (Tiling Window Manager)

#411 2009-10-13 03:04:03

Re: Musca (Tiling Window Manager)

#412 2009-11-15 10:15:45

Re: Musca (Tiling Window Manager)

#413 2009-11-15 11:00:51

Re: Musca (Tiling Window Manager)

#414 2009-11-15 18:14:32

Re: Musca (Tiling Window Manager)

#415 2009-11-16 07:09:36

Re: Musca (Tiling Window Manager)

#416 2009-11-16 08:48:06

Re: Musca (Tiling Window Manager)

#417 2009-11-16 17:23:54

Re: Musca (Tiling Window Manager)

#418 2009-11-16 17:53:15

Re: Musca (Tiling Window Manager)

#419 2009-11-16 19:24:14

Re: Musca (Tiling Window Manager)

#420 2009-11-16 19:37:00

Re: Musca (Tiling Window Manager)

#421 2009-11-16 19:39:50

Re: Musca (Tiling Window Manager)

#422 2009-11-17 14:26:16

Re: Musca (Tiling Window Manager)

#423 2009-11-17 15:08:28

Re: Musca (Tiling Window Manager)

#424 2009-11-18 01:41:27

Re: Musca (Tiling Window Manager)

#425 2009-11-18 05:34:28

Re: Musca (Tiling Window Manager)

Board footer