Musca (Tiling Window Manager)

Inxsible · 2009-04-22 02:21:32

greenmanwitch wrote:

How do I make a keybinding that toggles?
Like, if I press Mod4+p once, it will pad 0 0 18 0, 2nd time it will pad 0 0 0 0

Easier option : Have two separate keybindings?

You can write a custom script which tracks how many times you hit the particular keybinding...and on all even numbered hits, pad it with 0 0 0 0 and on all odd hits pad it with 0 0 18 0

greenmanwitch · 2009-04-22 02:36:14

Inxsible: Can you give an example? I don't want the two separate keybindings.
Also, is anybody else having trouble with pcmanfm in musca? :S. It keeps freezing when opening folders.

greenmanwitch · 2009-04-22 02:39:50

** (nautilus:21323): WARNING **: Can not get _NET_WORKAREA

Gives this. As far as I know I don't get any problems, but thought I'd just mention it.

aerosuidae · 2009-04-22 03:03:18

@greenmanwitch, @berticus: What gtk2 themes do you each use?

I've seen no pcmanfm problems. Is it still frozen if you issue the refresh command?

greenmanwitch · 2009-04-22 03:05:10

@aerosuidea: Doesn't matter what theme. I deleted my .gtkrc-2.0 and I still get it. Refresh does nothing to aid the situation.

Last edited by greenmanwitch (2009-04-22 03:05:40)

aerosuidae · 2009-04-22 03:09:51

@greenmanwitch: can I see your .config/pcmanfm/main ? I'd like to try to reproduce this...

aerosuidae · 2009-04-22 03:18:36

Btw @all: I'll try to hang out on freenode #musca when possible, incase anyone wants real time (ish ) interaction. I might be on the wrong side of the planet for a lot of you though...

Inxsible · 2009-04-22 03:24:53

greenmanwitch wrote:

Also, is anybody else having trouble with pcmanfm in musca? :S. It keeps freezing when opening folders.

greenmanwitch wrote:

** (nautilus:21323): WARNING **: Can not get _NET_WORKAREA

Are you sure that's a pcmanfm bug that you have reported. nautilus is a different file manager. Can you try to see if you get that bug in another wm as well?

Last edited by Inxsible (2009-04-22 03:34:21)

Inxsible · 2009-04-22 03:25:31

aerosuidae wrote:

.... I might be on the wrong side of the planet for a lot of you though...

and what side is that

aerosuidae · 2009-04-22 03:31:28

Inxsible wrote:

and what side is that

down under

Inxsible · 2009-04-22 05:17:53

EnvoyRising wrote:

Valid question, but as per the main page "startup" is in fact an option.

I did email Sean about it, here's his reply

> Would it be too much trouble if you could move the .musca_start file under
> ~/.config/musca/musca_start ?
>
> I just think it is much cleaner than having it lying around in /home/$USER.
> I looked at the set startup command, but if I change the location of the
> file, how will it know where to read it from?
No, "startup" cannot be set on the fly as the target file is already
being processed
> Am I missing something?
The reason the "startup" setting points to ".musca_start" (ie, no path
at all, not even $HOME, just the current working directory) is to make
it as flexible and platform impartial as possible. So the question
is: Would the .config location suit all Linux distributions out there?
How about the BSDs? (yep, people are running Musca on BSD too). I
suspect it would not...
If we start making package for different distros, we need to create a
custom config.h for each platform, or build a more flexible
configure/make system.
cheers

Procyon · 2009-04-22 08:55:22

Here is an example script for toggling padding, I haven't tested it:

musca -c 'dump .musca_dump'
grep ^group .musca_dump | while read ident left right top bottom name; do
if [ $bottom -eq 0 ]; then
musca -c 'pad 0 0 0 20'
else
musca -c 'pad 0 0 0 0'
fi

hatten · 2009-04-22 14:41:53

How did you get conky working in musca? As soon as i start it it stays on screen until i click somewhere or start something, and then it is hidden behind everything (even if i close everything)

Procyon · 2009-04-22 14:50:40

Where do you want to display conky?

hatten · 2009-04-22 18:23:34

well, on the desktop =P Above the wallpaper set by feh.

Procyon · 2009-04-22 18:51:56

But you never see that, right?

Put it in a window, or use conky-cli to a pager.

You know what I do is, I have a second smaller monitor that I use just for rtorrent, download manager, and system monitoring (pstree, date, df, etc) + an mpd client.

hatten · 2009-04-22 19:23:05

I want some stuff on the desktop, that i don't need to see all the time, and if i need to see it i just create a frame for it.

EnvoyRising · 2009-04-22 22:08:10

Inxsible wrote:

EnvoyRising wrote:
Valid question, but as per the main page "startup" is in fact an option.
I did email Sean about it, here's his reply
> Would it be too much trouble if you could move the .musca_start file under
> ~/.config/musca/musca_start ?
>
> I just think it is much cleaner than having it lying around in /home/$USER.
> I looked at the set startup command, but if I change the location of the
> file, how will it know where to read it from?
No, "startup" cannot be set on the fly as the target file is already
being processed
> Am I missing something?
The reason the "startup" setting points to ".musca_start" (ie, no path
at all, not even $HOME, just the current working directory) is to make
it as flexible and platform impartial as possible. So the question
is: Would the .config location suit all Linux distributions out there?
How about the BSDs? (yep, people are running Musca on BSD too). I
suspect it would not...
If we start making package for different distros, we need to create a
custom config.h for each platform, or build a more flexible
configure/make system.
cheers

Ah, makes since. So then perhaps this option shouldn't be included under the part of the website that says it can be changed with "set" ?
Also, perhaps it could be changed by setting an environment variable (eg $MUSCA_START)? That would prevent users from having to recompile...

Inxsible · 2009-04-22 22:12:08

EnvoyRising wrote:

Ah, makes since. So then perhaps this option shouldn't be included under the part of the website that says it can be changed with "set" ?
Also, perhaps it could be changed by setting an environment variable (eg $MUSCA_START)? That would prevent users from having to recompile...

He also suggested having a command line argument indicating the location of the start file. If there is enough support for it, he might implement it in the next version.

Last edited by Inxsible (2009-04-22 22:13:01)

Inxsible · 2009-04-22 23:52:36

I just got a segfault in musca. I wouldn't be able to tell you exactly how to reproduce it since it just happened once. I will keep an eye out for it.

Here's the log for it from /var/log/everything.log

Apr 22 18:59:02 arch logger: ACPI action undefined: BAT1
Apr 22 19:19:02 arch -- MARK --
Apr 22 19:27:46 arch kernel: musca[5530]: segfault at 1 ip 0804d197 sp bfe46e20 error 4 in musca[8048000+10000]
Apr 22 19:28:39 arch acpid: client connected from 9159[0:1000]
Apr 22 19:28:39 arch acpid: 1 client rule loaded
Apr 22 19:28:40 arch kernel: IRQ 11/nvidia: IRQF_DISABLED is not guaranteed on shared IRQs
Apr 22 19:28:40 arch kernel: agpgart-intel 0000:00:00.0: AGP 2.0 bridge
Apr 22 19:28:40 arch kernel: agpgart-intel 0000:00:00.0: putting AGP V2 device into 4x mode
Apr 22 19:28:40 arch kernel: nvidia 0000:01:00.0: putting AGP V2 device into 4x mode

It just dropped me to tty. I have a logout in my bash_profile and so it dropped me to tty and I had to login again.

aerosuidae · 2009-04-23 02:11:55

@Inxsible: error 4 is EINTR intrerrupted system call. Might be a hard one to reproduce. Try enabling core dump:

ulimit -c unlimited

Might need to be set above in your bash login shell. Then run musca. Another crash should then spit out a core file a few Mb in size (size of musca proess virtual mem size). Compress the core and attach it, plus *your* musca binary, to a bug report. From there we can dig around with gdb.

Procyon · 2009-04-23 07:22:31

I think exec_cmd() should fork and setsid twice, and not once. That way you also won't have processes dying when you kill musca when run from it.

aerosuidae · 2009-04-23 10:09:55

@Procyon: you mean like launching a daemon, to get the child process attached to init directly? Is that normal for a window manager?
You could use nohup.. or screen...

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

I think that is preferred behavior for any launcher. In my dmenu script I use setsid setsid command.

Inxsible · 2009-04-27 05:22:28

Hi Sean,

I got the segfault again. Opened up a bug report on launchpad along with the core dump and the musca binary. Let me know if you need any other info.

Thanks.

Arch Linux

#301 2009-04-22 02:21:32

Re: Musca (Tiling Window Manager)

#302 2009-04-22 02:36:14

Re: Musca (Tiling Window Manager)

#303 2009-04-22 02:39:50

Re: Musca (Tiling Window Manager)

#304 2009-04-22 03:03:18

Re: Musca (Tiling Window Manager)

#305 2009-04-22 03:05:10

Re: Musca (Tiling Window Manager)

#306 2009-04-22 03:09:51

Re: Musca (Tiling Window Manager)

#307 2009-04-22 03:18:36

Re: Musca (Tiling Window Manager)

#308 2009-04-22 03:24:53

Re: Musca (Tiling Window Manager)

#309 2009-04-22 03:25:31

Re: Musca (Tiling Window Manager)

#310 2009-04-22 03:31:28

Re: Musca (Tiling Window Manager)

#311 2009-04-22 05:17:53

Re: Musca (Tiling Window Manager)

#312 2009-04-22 08:55:22

Re: Musca (Tiling Window Manager)

#313 2009-04-22 14:41:53

Re: Musca (Tiling Window Manager)

#314 2009-04-22 14:50:40

Re: Musca (Tiling Window Manager)

#315 2009-04-22 18:23:34

Re: Musca (Tiling Window Manager)

#316 2009-04-22 18:51:56

Re: Musca (Tiling Window Manager)

#317 2009-04-22 19:23:05

Re: Musca (Tiling Window Manager)

#318 2009-04-22 22:08:10

Re: Musca (Tiling Window Manager)

#319 2009-04-22 22:12:08

Re: Musca (Tiling Window Manager)

#320 2009-04-22 23:52:36

Re: Musca (Tiling Window Manager)

#321 2009-04-23 02:11:55

Re: Musca (Tiling Window Manager)

#322 2009-04-23 07:22:31

Re: Musca (Tiling Window Manager)

#323 2009-04-23 10:09:55

Re: Musca (Tiling Window Manager)

#324 2009-04-23 10:23:29

Re: Musca (Tiling Window Manager)

#325 2009-04-27 05:22:28

Re: Musca (Tiling Window Manager)

Board footer