Musca (Tiling Window Manager)

Procyon · 2009-04-17 09:56:22

I just installed .17, the bazaar page had me excited. I do have some problems:

The shivering became worse, it is now happening with any two mouse clicks in any application.

And something curious: when I switched from .16 to .17 the recovery of unmapped windows didn't work, but when I restarted .17 it did.

aerosuidae · 2009-04-17 10:35:25

Procyon wrote:

The shivering became worse, it is now happening with any two mouse clicks in any application.

Interesting. I can't seem to reproduce this. Are the borders of windows moving at all (as your previous report seemed to suggest) or does it seem like some sort of extra redrawing of the window contents?

@all: anyone else seeing this?

Procyon wrote:

nd something curious: when I switched from .16 to .17 the recovery of unmapped windows didn't work, but when I restarted .17 it did.

s/curious/expected/

Procyon · 2009-04-17 11:09:10

When I scroll down on urxvt when it's at the bottom, (so it gets lots of mouse clicks), I think I can see the border unfocus color.

aerosuidae · 2009-04-17 11:18:33

@Procyon: Mind testing for any improvement with revision 172 from https://code.launchpad.net/musca ?

Procyon · 2009-04-17 12:06:14

@aerosuidae: Works perfectly, thanks!

EDIT:

It caused a new problem: when I switch groups it will be blank until I cycle or if there is only one window until there is something to redraw.

Last edited by Procyon (2009-04-17 12:09:41)

aerosuidae · 2009-04-17 13:28:38

@Procyon: Ok, try revision 173.

Procyon · 2009-04-17 13:39:29

@aerosuidae: It's working nicely.

Inxsible · 2009-04-17 23:30:48

Started using .17. I noticed that the groups are now being numbered. Is there a way to add a keybinding like Mod + number to go to that group?

I find it useful, because sometimes I have multiple groups with the same layout and I have to hit Mod+g just to see which one I am in.

Thanks.

Last edited by Inxsible (2009-04-17 23:33:03)

aerosuidae · 2009-04-17 23:53:13

Inxsible wrote:

Started using .17. I noticed that the groups are now being numbered. Is there a way to add a keybinding like Mod + number to go to that group?

The use command will accept either group number or group name. So, just bind it:

bind on Mod4+1 use 1

aerosuidae · 2009-04-18 00:19:51

Inxsible wrote:

I find it useful, because sometimes I have multiple groups with the same layout and I have to hit Mod+g just to see which one I am in.

Incidentally (kind of related to this): We now support enough EWMH for the "superswitcher" utility to work. http://code.google.com/p/superswitcher/ and available in community repo on Arch. My personal favourite. I start it with the Caps Lock key.

megajosh2 · 2009-04-18 00:54:34

I've been very interested with these tiling window managers, although I haven't tried one yet. This looks promising.

Inxsible · 2009-04-18 04:38:29

aerosuidae wrote:

The use command will accept either group number or group name. So, just bind it:
bind on Mod4+1 use 1

Sweet !!

aerosuidae wrote:

Incidentally (kind of related to this): We now support enough EWMH for the "superswitcher" utility to work. http://code.google.com/p/superswitcher/ and available in community repo on Arch. My personal favourite. I start it with the Caps Lock key.

Did not know about this. Will look into it. Thanks again.

Also, Since .17, I have been noticing that stalonetray always stays on top, even when I give a pad 0 0 0 0. I haven't changed any setting in stalonetrayrc. Conky hides as it should after issuing that pad, so I am not sure why stalonetray is not. I don't know what happened. I will try to restart musca and see if this persists.

Last edited by Inxsible (2009-04-18 04:47:44)

aerosuidae · 2009-04-18 05:51:02

Inxsible wrote:

Also, Since .17, I have been noticing that stalonetray always stays on top, even when I give a pad 0 0 0 0. I haven't changed any setting in stalonetrayrc. Conky hides as it should after issuing that pad, so I am not sure why stalonetray is not. I don't know what happened. I will try to restart musca and see if this persists.

When you start a panel it is unmanaged because it is _NET_WM_WINDOW_TYPE_DOCK. Being unmanaged, it will initially appear on top of the window stack. However as soon as you change or cycle a frame, or switch groups, I would expect the panel to disapear underneath application windows, unless it also uses _NET_WM_STATE_ABOVE.

This behavior seems to occur as expected for me with a quick test of fbpanel and stalonetray. At what step in the process is it behaving differently for you?

Inxsible · 2009-04-18 06:34:00

I simply have a stalonetray of geometry 120x16. My conky is also shown alongside the tray. I also have a

manage off stalonetray
manage off Conky
hook on ^add pad 0 0 0 16

in my musca_start file. Now I remove the padding when I watch movies. Until .16, when i removed the padding (manually entering pad 0 0 0 0), stalonetray would disappear beneath the vlc video. Since .17, however, conky disappears beneath, but stalonetray stays on top, no matter the padding.

Mesher · 2009-04-18 23:34:21

Is the .start file automatically placed in my home directory? If not, where does musca pull the default settings?

Procyon · 2009-04-19 00:06:08

Mesher wrote:

Is the .start file automatically placed in my home directory? If not, where does musca pull the default settings?

Defaults are in config.h. You have to make the .musca_start file yourself.

aerosuidae · 2009-04-19 06:41:52

Inxsible wrote:

Until .16, when i removed the padding (manually entering pad 0 0 0 0), stalonetray would disappear beneath the vlc video. Since .17, however, conky disappears beneath, but stalonetray stays on top, no matter the padding.

If you pad 0 0 0 0 then cycle the frame, or switch groups and back again, does stalonetray then disapear?

EnvoyRising · 2009-04-19 14:06:18

I've seen a few people asking where the musca_start file is. Perhaps it would be a good idea to ship a musca_start file with musca (located in /etc/musca/musca_start) and have a post install message that tells them to copy it to .musca_start, or change "set startup" to a location of their chosing? Perhaps something like what follows would be helpful to new muscateers (pardon the lame pun):

# This file is part of Musca.
# 
# Musca is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
#
# Musca is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with Musca.  If not, see <http://www.gnu.org/licenses/>.
#
# Sean Pringle
# sean dot pringle at gmail dot com
# https://launchpad.net/musca

# Location of this file.
set startup                    .musca_start

# These colours must be strings that X11 will recognize.
set border_focus                Blue
set border_unfocus            Dim Gray
set border_dedicate_focus    Red
set border_dedicate_unfocus    Dark Red
set border_catchall_focus    Green
set border_catchall_unfocus    Dark Green
set border_width                1

# Frame size limits in pixels.
set frame_min_wh                100
set frame_resize                20

# Customize the dmenu command.
set dmenu                        dmenu -i -b 

# Customize the actions of dmenu driven window/group/command minues. 
# By default we just spit commands bck to musca but you cn wrap or 
# redirect stuff. The $MUSCA environment variable is set to arg[0] 
# in setup(). -i means execute stdin.
set switch_window                sed 's/^/raise /'    | $MUSCA -i
set switch_group                sed 's/^/use /'    | $MUSCA -i
set run_musca_command                        $MUSCA -i
set run_shell_command            sed 's/^/exec'        | $MUSCA -i

# Your preferred method of being sent a message eg:
#        print to stdout with line break: echo `cat`
#        popup xmessage: xmessage -timeout 3 -file -
#        popup dzen2 (needs a line break): echo `cat` | dezen2 -p 33 -w 300
#        popup notify-send (doesn't accept stdin): notify-send -t 3000 Musca \`cat`\
set notify                        echo `cat`

# This  keyboard modifier is used in stacking mode along with mouse 
# buttons 1 and 3 to move and resize windows respectively.
set stack_mouse_modifier            bind on Mod4
set focus_follow_mouse            0

# Whether new windows should open in the current focused frame (current)
# or try to find an empty frame (empty).
set window_open_frame            current

# Whether new windows should automatically take the focus or not
set window_open_focus            1

# Buffer sizes in bytes
set command_buffer_size            4096
set notify_buffer_size                4096

# Whether empty frames should automatically find nd display a hidden window.
set frame_display_hidden            1

# Default list of window *classes* to ignore. use xprop WM_CLASS to find them.
manage off                    trayer
manage off                    Xmessage
manage off                    Conky    

# We simply map key bindings to any musca command. 
bind on Mod4+h                    hsplit 1/2    
bind on Mod4+v                    vsplit 1/2    
bind on Mod4+r                    remove        
bind on Mod4+o                    only          
bind on Mod4+k                    kill          
bind on Mod4+c                    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+Prior                use (prev)    
bind on Mod4+Tab                screen (next) 
bind on Mod4+w                    switch window 
bind on Mod4+g                    switch group  
bind on Mod4+x                    shell         
bind on Mod4+m                command       
bind on Mod4+d                    dedicate flip 
bind on Mod4+a                    catchall flip 
bind on Mod4+u                    undo          
bind on Mod4+s                    stack flip    
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+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+t                    exec xterm    

# These are only general settings. To take full advantageo of Musca,
# users are encouraged to read the full list of available commands,
# located at http://aerosuidae.net/musca.html or issue "man musca"
# on the command line.

Please pardon the ugly spacing I no matter what I did, I couldn't seem to get things to line up correctly in the forums. I have a copy of this file in my home folder that is correctly formatted if anyone is interested.

update
fixed typo

Last edited by EnvoyRising (2009-04-20 12:34:33)

hatten · 2009-04-19 18:11:30

bugfix:

# Custompize the dmenu command.

should be customize ofcourse

Inxsible · 2009-04-19 18:17:37

aerosuidae wrote:

Inxsible wrote:
Until .16, when i removed the padding (manually entering pad 0 0 0 0), stalonetray would disappear beneath the vlc video. Since .17, however, conky disappears beneath, but stalonetray stays on top, no matter the padding.
If you pad 0 0 0 0 then cycle the frame, or switch groups and back again, does stalonetray then disapear?

No it does not

Procyon · 2009-04-19 18:37:09

@ Inxsible: Can't you change the WM Hints of Stalonetray? I think the old way was worse because if you had dmenu open and click on firefox, dmenu disappears even though it is still grabbing keys. Some apps just need to be on top always and the current version respects that.

@ Envoy Rising: That is certainly more informative than config.h, but with the website documentation, musca -c 'show settings|etc|etc', and that the startfile is better built bottom up than top down, I don't know if it is really a good thing to put in the official package.

Inxsible · 2009-04-19 18:59:35

Procyon wrote:

@ Inxsible: Can't you change the WM Hints of Stalonetray? I think the old way was worse because if you had dmenu open and click on firefox, dmenu disappears even though it is still grabbing keys. Some apps just need to be on top always and the current version respects that.
@ Envoy Rising: That is certainly more informative than config.h, but with the website documentation, musca -c 'show settings|etc|etc', and that the startfile is better built bottom up than top down, I don't know if it is really a good thing to put in the official package.

Hmmm. I never had the issue of dmenu locking up in musca....although I had had that happen to me a lot in wmii. I will try and change the WM Hints of stalonetray and see if it helps. The thing is, I want the tray to disappear only when I am watching a movie...At all other times, I want it staying at the bottom right corner, which is why I pad all my groups by 0 0 0 16.

I agree that building a musca_start file from bottom up is much better, because you can only add stuff that you want different from default. But a good thing would be to be able to change the location of the start file. I like all my config files to go under ~/.config/appName, rather than clutter the /home/$USER. I know we can change the location in config.h and re-compile...but I am just lazy to do it for every update

Procyon · 2009-04-19 19:29:10

I never had the issue of dmenu locking up in musca.

It's not locking up, pressing Escape even if the window was hidden would shut dmenu down.

If you want the pager to hide just with mplayer, can't you put mplayer even more in the foreground with fstype?

aerosuidae · 2009-04-20 00:05:55

@Inxsible: Your stalonetray instance is behaving differently to my test instance of stalonetray. May we see your stalonetrayrc?

Last edited by aerosuidae (2009-04-20 00:06:54)

Inxsible · 2009-04-20 00:15:40

aerosuidae wrote:

@Inxsible: Your stalonetray instance is behaving differently to my test instance of stalonetray. May we see your stalonetrayrc?

Here's my stalonetray which is basically unchanged ever since I started using Musca.

# vim:filetype=config:tw=80:et
# 
# This is sample ~/.stalonetrayrc, resembling default configuration.
# Remember: command line parameters take precedence.
#
# Directives introduced in 0.7.6 are marked with "NEW in 0.7.6"
#
####################################################################
# 
# stalonetray understands following directives
#
####################################################################

# background <color>         # color can be specified as an HTML hex triplet or
                             # as a name from rgb.txt, note that '#' must be quoted
background "#777777"

# decorations <decspec>      # set trays window decorations; possible values for
                             # decspec are: all, title, border, none
decorations none

# display <display name>     # as usual

# dbg_level <int>            # controls the amount of debug info (for this setting to
                             # have effect, stalonetray sources must have been
                             # configured and compiled with --enable-debug)
# dbg_level 0

# fuzzy_edges [<level>]      # enable fuzzy edges and set fuzziness level. level
                             # can be from 0 (disabled) to 3; this setting works
                             # with tinting and/or transparent and/or pixmap
                             # backgrounds (NEW in 0.7)
fuzzy_edges 0

# geometry <geometry>        # tray's geometry in standard X notation
geometry 80x16+1600-0

# grow_gravity <gravity>     # one of N, S, E, W, NW, NE, SW, SE; tray will grow
                             # in the direction opposite to one specified by
                             # grow_gravity; if horizontal or vertical
                             # direction is no specified, tray will not grow in
                             # that direction
grow_gravity NW

# icon_gravity <gravity>     # icon placement gravity, one of NW, NE, SW, SE
icon_gravity NW

# icon_size <int>            # specifies dimensions of typical icon slot
icon_size 16

# ignore_icon_resize [<bool>] # ignore icon attempts to resize their windows
                             # (NEW in 1.7)
ignore_icon_resize false

# max_width <int>            # specifies maximal tray's width (0 = no limit)
max_width 0

# max_height <int>           # specifies maximal tray's height (0 = no limit)
max_height 16

# no_shrink [<bool>]         # disables shrink-back mode (NEW in 0.7)
no_shrink false

# parent_bg [<bool>]         # whether to use pseudo-transparency 
                             # (looks better when reparented into smth like FvwmButtons)
parent_bg true

# pixmap_bg <path_to_xpm>    # use pixmap from specified xpm file for (tiled) background
# pixmap_bg /home/user/.stalonetraybg.xpm

# respect_icon_hints [<bool>] # try to respect icon hints (NEW in 0.7)
respect_icon_hints false

# skip_taskbar [<bool>]      # hide tray`s window from the taskbar
skip_taskbar true

# sticky [<bool>]            # make a tray`s window sticky across the
                             # desktops/pages
sticky true

# tint_color <color>         # set tinting color (NEW in 0.7)
tint_color black

# tint_level <level>         # set tinting level; level ranges from 0 (disabled)
                             # to 255 (NEW in 0.7)
tint_level 0 

# transparent [<bool>]       # whether to use root-transparency (background
                             # image must be set with Esetroot or compatible utility)
transparent false

# vertical [<bool>]          # whether to use vertical layout (horizontal layout
                             # is used by default)
vertical false

# window_layer <layer>       # set the EWMH-compatible window layer; one of:
                             # bottom, normal, top
window_layer top

# window_type <type>         # set the EWMH-compatible window type; one of:
                             # dock, normal, toolbar, utility
window_type dock 

# withdrawn [<bool>]         # start withdrawn (NEW in 0.7, prior to that
                             # withdrawn mode was default!)
withdrawn true 

# xsync [<bool>]             # whether to operate on X server synchronously (SLOOOOW)
xsync false

Arch Linux

#251 2009-04-17 09:56:22

Re: Musca (Tiling Window Manager)

#252 2009-04-17 10:35:25

Re: Musca (Tiling Window Manager)

#253 2009-04-17 11:09:10

Re: Musca (Tiling Window Manager)

#254 2009-04-17 11:18:33

Re: Musca (Tiling Window Manager)

#255 2009-04-17 12:06:14

Re: Musca (Tiling Window Manager)

#256 2009-04-17 13:28:38

Re: Musca (Tiling Window Manager)

#257 2009-04-17 13:39:29

Re: Musca (Tiling Window Manager)

#258 2009-04-17 23:30:48

Re: Musca (Tiling Window Manager)

#259 2009-04-17 23:53:13

Re: Musca (Tiling Window Manager)

#260 2009-04-18 00:19:51

Re: Musca (Tiling Window Manager)

#261 2009-04-18 00:54:34

Re: Musca (Tiling Window Manager)

#262 2009-04-18 04:38:29

Re: Musca (Tiling Window Manager)

#263 2009-04-18 05:51:02

Re: Musca (Tiling Window Manager)

#264 2009-04-18 06:34:00

Re: Musca (Tiling Window Manager)

#265 2009-04-18 23:34:21

Re: Musca (Tiling Window Manager)

#266 2009-04-19 00:06:08

Re: Musca (Tiling Window Manager)

#267 2009-04-19 06:41:52

Re: Musca (Tiling Window Manager)

#268 2009-04-19 14:06:18

Re: Musca (Tiling Window Manager)

#269 2009-04-19 18:11:30

Re: Musca (Tiling Window Manager)

#270 2009-04-19 18:17:37

Re: Musca (Tiling Window Manager)

#271 2009-04-19 18:37:09

Re: Musca (Tiling Window Manager)

#272 2009-04-19 18:59:35

Re: Musca (Tiling Window Manager)

#273 2009-04-19 19:29:10

Re: Musca (Tiling Window Manager)

#274 2009-04-20 00:05:55

Re: Musca (Tiling Window Manager)

#275 2009-04-20 00:15:40

Re: Musca (Tiling Window Manager)

Board footer