You are not logged in.
Start off with reading man xbindkeys...
Something like this would do, presuming 122 is decrease volume etc
"amixer set PCM toggle"
c:121
"amixer set PCM 2-"
c:122
"amixer set PCM 2+"
c:123
Offline
Just installed musca and have the basics working. I have my background working and I am able to open apps and switch between them.
However I have not been able to get dmenu started using M+m or M+x?
Also it seems config.h is just for defaults so where can I find musca_start. so I can edit that?
My .xinitrc only includes musca and not dmenu if thats an issue?
Arch64, AMD64, LXDE
Offline
Just installed musca and have the basics working. I have my background working and I am able to open apps and switch between them.
However I have not been able to get dmenu started using M+m or M+x?
Also it seems config.h is just for defaults so where can I find musca_start. so I can edit that?
My .xinitrc only includes musca and not dmenu if thats an issue?
Have you installed from source? If so, you need to install dmenu or any other similar menu program.
The AUR package also has dmenu as a dependency, so you can use that as well.
you will have to create a .musca_start in your /home/$user folder and musca will find it.
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
banshee28 wrote:Just installed musca and have the basics working. I have my background working and I am able to open apps and switch between them.
However I have not been able to get dmenu started using M+m or M+x?
Also it seems config.h is just for defaults so where can I find musca_start. so I can edit that?
My .xinitrc only includes musca and not dmenu if thats an issue?
Have you installed from source? If so, you need to install dmenu or any other similar menu program.
The AUR package also has dmenu as a dependency, so you can use that as well.
you will have to create a .musca_start in your /home/$user folder and musca will find it.
Thanks, I was just going to post back..I installed from AUR but apparently I also needed to install dmenu
So now I see it at the bottom of the screen...lol
I need to create .musca_start now.
Last edited by banshee28 (2009-04-01 00:59:28)
Arch64, AMD64, LXDE
Offline
Start off with reading man xbindkeys...
Something like this would do, presuming 122 is decrease volume etc
"amixer set PCM toggle"
c:121
"amixer set PCM 2-"
c:122
"amixer set PCM 2+"
c:123
You guys are awesome - unbelievable.
Offline
I have a problem with sdlmame. I think it could happen to other apps too. Here is a screenshot:
In ratpoison, the window will be small too initially, but after doing redisplay it makes the window fit the entire screen. Can you add this too?
EDIT:
In ratpoison redisplay is also nice for the firefox download dialog.
Last edited by Procyon (2009-04-01 18:15:27)
Offline
Typo spotted.
http://aerosuidae.net/musca.html#changelog_0_9_6
Added window_open_focus=<current|empty> to determine which frame should be preferred for a new window, and window_open_frame=<1|0> to control whether the new window should take input focus.
It is correct earlier, but here window_open_focus and window_open_frame are mixed up.
Offline
For some reason it seems like my scrolling with the center mouse wheel is slower than normal. When i use the scroll bar I can move it faster. Is there a setting that I can tweak the timing for this?
This type of WM does take some getting used to but so far its about 10-20 percent less on resources measured using the same apps and all than xfce4.6. This was not a detailed scientific test, just a htop observation
Arch64, AMD64, LXDE
Offline
Also, I cant seem to get fbpanel to start or show up when musca starts. Here is my .musca_startup
#manage off fbpanel
stack on
screen 0
name bling
pad 0 0 0 32
exec fbpanel &
Arch64, AMD64, LXDE
Offline
Also, I cant seem to get fbpanel to start or show up when musca starts. Here is my .musca_startup
#manage off fbpanel stack on screen 0 name bling pad 0 0 0 32 exec fbpanel &
Remove the & after the command and it will work.
Just to be sure you have your fbpanel set at the bottom? It will show only if it is since the way you are padding.
Last edited by Inxsible (2009-04-01 23:24:39)
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
banshee28 wrote:Also, I cant seem to get fbpanel to start or show up when musca starts. Here is my .musca_startup
#manage off fbpanel stack on screen 0 name bling pad 0 0 0 32 exec fbpanel &
Remove the & after the command and it will work.
Just to be sure you have your fbpanel set at the bottom? It will show only if it is since the way you are padding.
I thought I needed that & to put it in the background, yes its at the bottom. Will restart musca now.
EDIT: removed the & and still noting. I do have a gap at the bottom of the page where the background image is not going all the way to the bottom. I am thinking that might be the padding? If I run fbpanel from m+fbpanel, it works fine. But then if I open a window or app, it disappears again. So its probably there just hiding. Just checked and there is only one instance of fbpanel running most likely the one I manually opened.
Last edited by banshee28 (2009-04-01 23:40:29)
Arch64, AMD64, LXDE
Offline
Also, I cant seem to get fbpanel to start or show up when musca starts. Here is my .musca_startup
I tried your .musca_start, and it worked ok here. So, a few questions:
1. Does it work if you launch fbpanel from .xinitrc before starting musca?
2. Does it make any difference if you include a delay in .musca_start? Eg:
exec sleep 1s && fbpanel
3. When you launch fbpanel manually and see it hide behind other applications, is that on this "bling" group in stacking mode?
Offline
banshee28 wrote:Also, I cant seem to get fbpanel to start or show up when musca starts. Here is my .musca_startup
I tried your .musca_start, and it worked ok here. So, a few questions:
1. Does it work if you launch fbpanel from .xinitrc before starting musca?
2. Does it make any difference if you include a delay in .musca_start? Eg:
exec sleep 1s && fbpanel
3. When you launch fbpanel manually and see it hide behind other applications, is that on this "bling" group in stacking mode?
1) YES, it starts fine this way, but then my M+ keys dont seem to work, plus the curser is an x instead of the pointer, i cant M+ any longer, etc.
2) Tried the delay and seems the same.
3) I dont necessarily see it hide but assume its hiding there.
.xinitrc:
sleep 1
exec fbpanel
sleep 1
exec musca >> /dev/null
ull
.musca_startup
#manage off fbpanel
stack on
screen 1
name bling
#pad 0 0 0 32
#exec fbpanel
ALSO, it seems quite slow sometime switching between screens: M+c ?? Alt-tab is much quicker with xfce...Is this normal?
Arch64, AMD64, LXDE
Offline
Also, my background image is a few inches from the bottom of the screen, but all windows\apps go to the very bottom. Could this be the problem?
Arch64, AMD64, LXDE
Offline
aerosuidae wrote:1. Does it work if you launch fbpanel from .xinitrc before starting musca?
1) YES, it starts fine this way, but then my M+ keys dont seem to work, plus the curser is an x instead of the pointer, i cant M+ any longer, etc.
Only use exec for the last line in .xinitrc. Commands prior to launching the window manager need to be regular commands with & to put them in the background. http://wiki.archlinux.org/index.php/.xinitrc The cursor is an x becuase it is the default X showing; musca is not being started when you exec fbpanel in .xinitrc
ALSO, it seems quite slow sometime switching between screens: M+c ?? Alt-tab is much quicker with xfce...Is this normal?
M+c is switching windows, not screens. In any case both operations should be fast. I only notice slowdown on my system when something like Firefox is chock full of javascript and is slow to refresh after switching.
Do you notice if the slow switching is specific to all apps or just certain ones?
Also, my background image is a few inches from the bottom of the screen, but all windows\apps go to the very bottom. Could this be the problem?
No idea, but it sounds wrong. Is your image the same resolution as your default X resolution? Could we see a screen shot?
Offline
Ok, I got fbpanel to start using .xinitrc, and musca starts properly also. Then once I open something (terminal), fbpanel is no longer there, but is still running just cant be seen. I commented out the background so that should not be an issue any more?
I am almost there...
.xinitrc
fbpanel &
exec musca >> /dev/null
musca_startup
stack on
screen 1
name bling
pad 0 0 0 32
Arch64, AMD64, LXDE
Offline
Ok, I got fbpanel to start using .xinitrc, and musca starts properly also. Then once I open something (terminal), fbpanel is no longer there, but is still running just cant be seen.
Ok, so you're in stacking mode. Is the terminal window full screen, and if so can you see fbpanel if you resize it?
Last edited by aerosuidae (2009-04-02 02:27:32)
Offline
banshee28 wrote:Ok, I got fbpanel to start using .xinitrc, and musca starts properly also. Then once I open something (terminal), fbpanel is no longer there, but is still running just cant be seen.
Ok, so you're in stacking mode. Is the terminal window full screen, and if so can you see fbpanel if you resize it?
It was but the problem is once i resize or close it, fbpanel is gone also. But yes the full screen apps go to the bottom of the monitor with no padding for the panel?
Arch64, AMD64, LXDE
Offline
It was but the problem is once i resize or close it, fbpanel is gone also.
I note you had 'screen 1' in the last .musca_start, and 'screen 0' earlier. The fbpanel launching from .xinitrc will probably launch on screen 0.
But yes the full screen apps go to the bottom of the monitor with no padding for the panel?
Well, no actually Stacking mode always starts with 0 0 0 0 padding, but if you apply padding to a group in stacking mode (as you are in .musca_start), any new or resizing apps should respect that padding. If they don't, then something is either not setup as you expect, or you've found a bug.
What you describe with fbpanel being hidden sounds like tiling mode with no padding. As to why you're seeing this in stacking mode, I don't know. What happens if you try (apologies if you've tried this already):
- Start with no .musca_start (take it out of the loop to reduce unknowns)
- Use default tiling mode (ie, don't issue 'stack on' yet)
- pad 0 0 0 32
- launch fbpanel
- launch terminal
Does this show fbpanel bottom of the screen as normal?
- stack on
- resize the terminal if needs be
Is fbpanel still there, or now gone?
Offline
Hi.
I've found many really good things in musca. It's great wm!
But, is there any way to customize dmenu look from .musca_start file?
I know that I could do this from config.h.
//EDIT
Oh, I've found one ;]
Called 'set'
Last edited by sirmacik (2009-04-02 11:14:46)
Offline
Ok, tried with these settings and same thing: fbpanel is there on bootup. I start term close it and fbpanel is gone. Trying now without .musca_startup
.xinitrc
fbpanel &
exec musca >> /dev/null
musca_startup
screen 0
name test
pad 0 0 0 32
Edit: Tried with no .musca_startup file and same results. As soon as I open and resize term, no more fbpanel??
Last edited by banshee28 (2009-04-03 23:16:35)
Arch64, AMD64, LXDE
Offline
Have you tried using a different panel? Try it out with lxpanel or pypanel. Maybe its fbpanel that is not playing well.
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
Have you tried using a different panel? Try it out with lxpanel or pypanel. Maybe its fbpanel that is not playing well.
Now we are getting closer, but here is what is happening: I think I figured out that even though I dont have "stacking on" in the musca_start file (I deleted it completely) I can now get the panel to STAY there by pressing M+s!
Once I do that, the panel re-appears and works fine. (lxpanel) . Once I hit M+s again, its gone.
Also to run lxpanel as me, I get this
lxpanel
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
** (lxpanel:4338): DEBUG: cache file_name = /home/me/.cache/menus/4636f5d66047921d5ea838f6eac383a9
Segmentation fault
I have to run it as root, then it works but i get this
Su
bash-3.2# lxpanel
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
** (lxpanel:4390): DEBUG: cache file_name = /home/me/.cache/menus/4636f5d66047921d5ea838f6eac383a9
lxpanel : type is not XA_CARDINALlxpanel: can't load netstat plugin
lxpanel : X error: BadAlloc (insufficient resources for operation)
lxpanel : X error: BadDrawable (invalid Pixmap or Window parameter)
lxpanel : X error: BadPixmap (invalid Pixmap parameter)
Then, once I have the panel there and working none of the M+ keys are working. Maybe this is by design but I need to do something about this so I can have everything working together.
Arch64, AMD64, LXDE
Offline
Good news. I got the padding to work correctly and now the panel stays put
I can switch M+s and see the border like I should be able to!
I think I had a backup .musca_startup that someone got auto created which was conflicting with the one I was updating since the one that is working now is the same as I posted before.
Edit2: fbpanel is actually playing alot nicer than lxpanel was based on the above errors. Now I have to configure some panel plugins and see if I really like this wm
Last edited by banshee28 (2009-04-04 01:12:36)
Arch64, AMD64, LXDE
Offline
I already have xfce4.6 installed so I tried to simply change to xfce4-panel. It starts right away and seems great. However after opening a few windows and trying to right click and close them from the task bar, the panel freezes and cpu goes to 100% for ~15 secs then back to normal. This will happen each time. I am now using lxpanel and it closes fine by right clicking from the task bar.
Edit: When I first startup with xfce panel it will work 100% but after about 15 seconds after starting, it has this problem.
When I am running xfce it does not have any issues like this.
Also with musca xfce-panel is taking 6.7% or ram and in xfce its only taking 1.8%.
I know I am having too many issues with this setup, but it may not be related to musca. musca itself seems solid.
Last edited by banshee28 (2009-04-04 01:57:52)
Arch64, AMD64, LXDE
Offline