You are not logged in.
Man !!
After all the problems you have with panels, am I glad I dont use one at all !!
Using openbox, kind of taught me how to deal without a panel...and its great.
Question : I don't know your usage so I will go ahead and ask this : why would you need a panel with a tiling wm anyway? all the windows are on the display anyway, so you hardly need the panel to click on the windows?
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
Man !!
After all the problems you have with panels, am I glad I dont use one at all !!
Using openbox, kind of taught me how to deal without a panel...and its great.
Question : I don't know your usage so I will go ahead and ask this : why would you need a panel with a tiling wm anyway? all the windows are on the display anyway, so you hardly need the panel to click on the windows?
Yea, I used OB before and it was really good. I did not have any issues once I had it setup. I wanted a panel since I am used to it and like to be able to minmize all windows and hit the "start" menu top choose new apps. I have kinda gotten used to M+x which is cool, but I like the menus also.
Arch64, AMD64, LXDE
Offline
cycle prev is doing the same as cycle for me in 0.9.14
Offline
@aerosuidae: would it be possible to add a couple of commands to musca that would list open windows, available groups, focused window, etc? The reason would be that then one could use for instance 'echo list windows |musca -i' in various scripts, status bars, or even replace a panel app by dzen or such.
Offline
@bender02: you can use dump for that.
Here is an example of a script I am working on, it will cycle differently depending on what frame-layout you have: 1 frame, n frame and <=n windows, n frames and >n windows.
The "n frames and >n windows" still needs some work, right now it just cycles like 1 frame.
It will make sure that the cycling is done as expected in "n frames and <=n windows" by sorting the frames too.
#! /bin/bash
cd
function m() { musca -c "$*"; }
[ $# -ne 1 ] && exit
[ $1 = next -o $1 = prev ] || exit
m dump .musca_dump
if [ $(grep ^frame .musca_dump | wc -l) -eq 1 ]; then #single window mode
m cycle $1
exit
fi
if [ $(grep ^frame .musca_dump | wc -l) -lt $(grep ^window .musca_dump | wc -l) ]; then
#trouble
m cycle $1
exit
fi
if [ $1 = prev ]; then #anti clockwise
sedclock='$!H;${p;x;s~\n~~;p}'
elif [ $1 = next ]; then #clockwise
sedclock='1h;2,$p;${x;p}'
fi
frames="$(grep ^frame .musca_dump | sort -n -k3 -k2)"
(echo 'g/^frame/d'
echo i
paste <(echo "$frames" | cut -f-6 ) <(echo "$frames" | cut -f7 | sed -n $sedclock)
echo .
echo wq) | ed -s .musca_dump
m load .musca_dump
Offline
I have a problem with sdlmame. I think it could happen to other apps too. Here is a screenshot:
http://omploader.org/tMWd1agIn 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.
This isn't happening to me anymore. Not sure why. And the dialog resizing is not very important I think.
Offline
I would expect:
bind on Mod1+Shift+Return vsplit 1/2
bind on Mod1+Control+Return hsplit 1/2
hook on vsplit focus down
hook on hsplit focus right
to have the same effect as:
bind on Mod1+Shift+Return exec musca -c "vsplit 1/2" && musca -c "focus down"
bind on Mod1+Control+Return exec musca -c "hsplit 1/2 && musca -c "focus right"
However, it doesn't. If I try to use the hook method above, focus right on hsplit works, but focus down on vsplit does not. If I try them out independantly, they work, but not when combined. While the exec method works fine, I think it would be more flexible to use hooks, because it would allow for more flexibilty.
I wasn't sure if this was a user error or a bug. Please advise. Thanks, and once again, great job on musca, I'm loving it more and more each day.
Last edited by EnvoyRising (2009-04-06 03:37:10)
Offline
I would expect:
bind on Mod1+Shift+Return vsplit 1/2 bind on Mod1+Control+Return hsplit 1/2 hook on vsplit focus down hook on hsplit focus right
...
I wasn't sure if this was a user error or a bug. Please advise. Thanks, and once again, great job on musca, I'm loving it more and more each day.
Couple of things here:
1. There is no vsplit hook. Both vsplit and hsplit trigger a generic split hook: http://aerosuidae.net/musca.html#hooks.
2. You've found a bug in that both hsplit and vsplit should be reported as an invalid hook attempts.
Hooks are a bit experimental and may not persist in their current form. I'm not aiming to have hooks 1:1 map to commands, as eventually we'll add events that are not directly related to commands. I'm also not convinced the current hooks are all useful as they don't add much benefit compared to aliases.
If anyone has ideas, speak up
Last edited by aerosuidae (2009-04-06 04:18:07)
Offline
@bender02: you can use dump for that.
Thanks, i guess i tried dump, but didn't know that i should supply a filename to it. Still i would like to see that 'dump' without arguments would just print info to standard output - but even with the current status it's scriptable
I'll take a look at your script.
Offline
My 2 thoughts:
1: The name is horrible in my opinion.
2: It is the only wm that I have wanted to try in the last 4 years.
Offline
How can I open a group I started in screen 0 in screen 1?
Offline
@b3n: Windows are stuck on the screen you open them in.
Offline
wow... looks nice
I'm really gonna try this
edit: wow i am amazed, this replaced my awesome setup!!
Last edited by Frots (2009-04-06 13:50:29)
Offline
How can I open a group I started in screen 0 in screen 1?
you can move windows between groups using the move command, but I don't think you can move groups between screens.
Hooks are a bit experimental and may not persist in their current form. I'm not aiming to have hooks 1:1 map to commands, as eventually we'll add events that are not directly related to commands. I'm also not convinced the current hooks are all useful as they don't add much benefit compared to aliases.
If anyone has ideas, speak up
Does that mean that I can have an alias which uses two commands?
alias addnpad add newGroup pad 0 0 0 16
?? How would the syntax be?
Last edited by Inxsible (2009-04-06 17:17:18)
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
Does that mean that I can have an alias which uses two commands? How would the syntax be?
No, alias can't accept two commands directly. It needs to use exec to get two commands in, same as EnvoyRising did with bind:
alias addnpad exec musca -c "add newGroup" && musca -c "pad 0 0 0 16"
I meant that hooks as they are in 0.9.14 don't offer much benefit compared to aliases because, even though the alias syntax above is more clunky, you can do everything a hook can do with an alias and/or a bind.
I've recently changed the development version of Musca to use a posix regex for hooks, instead of the current hook names. So, instead of:
hook on add pad 0 0 0 16
it might be:
hook on ^add pad 0 0 0 16
hook on ^(add|use) pad 0 0 0 16
Basically it allows a single hook to link to multiple commands, or a very specific command. The regex option will solve EnvoyRising's earlier problem of attaching to hsplit and vsplit, as the following all become valid:
# hook to any split
hook on split <command>
# hook to hsplit only
hook on ^hsplit <command>
# hook to hsplit 1/2 only
hook on ^hsplit[[:space:]]1/2 <command>
Offline
Thanks aerosuidae. I updated to 0.9.15 in AUR as well.
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
Thanks aerosuidae. I updated to 0.9.15 in AUR as well.
Thanks. Did you notice the update email I sent out? The correct 0.9.15 tarball md5sum is 6234ba6a8ddaf86021071fadea6f80c5.
Sorry for the confusion. I need to clean up my release script bahavior, as I've made this mistake before.
Offline
Inxsible wrote:Thanks aerosuidae. I updated to 0.9.15 in AUR as well.
Thanks. Did you notice the update email I sent out? The correct 0.9.15 tarball md5sum is 6234ba6a8ddaf86021071fadea6f80c5.
Sorry for the confusion. I need to clean up my release script bahavior, as I've made this mistake before.
I had checked the md5 after I saw your email and it started with 11 - and your website listed the same thing at that time.
I guess I will re-install and re-update the AUR package.
Last edited by Inxsible (2009-04-07 05:53:11)
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
I had checked the md5 after I saw your email and it started with 11,
I guess I will re-install and re-update the AUR package.
11something was the old one, yes. My web host seems to have some sort of caching solution running. New files appear live instantly. but replaced files seem to have a delay of up to a few minutes between upload and appearing live.
Offline
Inxsible wrote:I had checked the md5 after I saw your email and it started with 11,
I guess I will re-install and re-update the AUR package.11something was the old one, yes. My web host seems to have some sort of caching solution running. New files appear live instantly. but replaced files seem to have a delay of up to a few minutes between upload and appearing live.
Not a problem !
I guess I always catch it at the wrong time
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
I also have this problem with a few apps where the display goes out of whack. Here's a screenie of rTorrent which is gone bonkers and you can hardly make any sense of it.
I have seen this happen in rTorrent (frequently) and in my terminal (although quite infrequently of late)
As you can see, its not displaying the torrent correctly and only a few numbers are seen which looks like the upload speed or something and the total time at the end. (I think)
Ok, A little further investigation tells me that this only happens when I use the keybinding for rTorrent which is defined as follows in xbindkeys
"urxvt -bg black -fg white -e screen -S rtorrent rtorrent"
m:0x40 + c:27
Mod4 + r
If I start a terminal first and then issue
screen -S rtorrent rtorrent
the display looks fine.
This means that this is probably not a Musca issue but something to do with keybindings
Last edited by Inxsible (2009-04-07 06:25:19)
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
Also what does 0.9.15 include that would make its memory usage shoot up? I saw that musca now uses twice the memory that it used in 0.9.14.
0.9.14 used about 340-450KB. 0.9.15 uses about 970KB.
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
@Inxsible - Might still be a musca thing. Does it ever mess up in stacking mode?
To me, terminals getting messed up always suggests the app within is having problems with terminal window resizing. Could be a timing thing too. What happens if you switch to another shell within screen, and back again? Still messed up?
Offline
Also what does 0.9.15 include that would make its memory usage shoot up? I saw that musca now uses twice the memory that it used in 0.9.14. 0.9.14 used about 340-450KB. 0.9.15 uses about 970KB.
We are now precompiling all regular expressions, for speed. But I havn't checked exactly how much additional memory that uses.
Most importantly:
1. Is Musca memory usage stable, or increasing, for you? I've been using valgrind --leak-check=full so I'm rather hoping it is stable.
2. What are you checking here? Virtual or resident memory usage?
3. 32 or 64 bit system?
Last edited by aerosuidae (2009-04-07 06:52:47)
Offline
@Inxsible - Might still be a musca thing. Does it ever mess up in stacking mode?
Yes, it does
To me, terminals getting messed up always suggests the app within is having problems with terminal window resizing. Could be a timing thing too. What happens if you switch to another shell within screen, and back again? Still messed up?
I started rtorrent within screen using the keybinding i listed above. then i used another terminal to connect to that instance of the rtorrent application and the display was messed up here as well. Then i closed both windows (Alt +F4). then launched a new terminal and reattached to rtorrent => display still messed up.
simply starting a terminal and then starting rtorrent within screen, does not suffer from weird displays..so even if i detach and then re-attach to this instance -- the display is correctly rendered as it was when i first started a screen session.
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline