Musca (Tiling Window Manager)

mhertz · 2011-06-11 15:57:10

Yeah, I know, but I just prefer to use it directly, since when I tried it some time ago, then I had problems with displaying the output of commands i.e. $(...) or ``...

Probably just me being a moron, but oh well...

By default there's no notifications when changing groups, so that's why I made the one listed in my previous post. I also made one for when cycling, i.e. which shows the current window and which windows else there's hidden and in which direction, but I decided to skip it, as I didn't need it and found it annoying, but I do use dzen2 notifications for group-switching when using Mod4+PgUP/PgDn for next/previous group, and also for volume changing, where I feel it's most usefull...

Last edited by mhertz (2011-06-11 16:01:28)

thehodapp · 2011-06-24 06:36:26

So I was thinking about starting to contribute to an open source project for learning experience (in coding and C), and I also really want musca to continue getting better. The source code doesn't seem to be completely overwhelming, but I realize it's not actively developed. Does anyone think it would be a good or bad idea to start working on it, or am I probably not going to get anywhere with it? If I should, how should I get started?

Army · 2011-06-24 07:30:15

I don't know HOW you should get started, but you should definitely do it!

Afaik the usual way to do this is by forking the project (e.g. southerncross is a fork of musca as well) and adding or removing features just the way you want to. You have to be careful with the license, which in musca's case is the GPL afair, so you always have to tell who was the original author, you can't tell people that your fork is completely YOURS. But I'm not 100% sure about all that, please investigate.

Good luck! And please tell us where we will be able to find your new sourcecode! I'd be very happy to test it and give feedback.

thehodapp · 2011-06-24 07:58:56

I understand the GPL pretty well. I have no problem with it (like a lot of devs). I'm not too big of the direction of southerncross, and I'd like to just sort of continue the direction musca was going when development stopped...basically fixing bugs and adding the functionality people wanted.

It might be a bit of time before I've got anything to show though because it's more of a learning experience for me.

gorilla · 2011-06-24 08:32:25

Great!!! I've been waiting for you :-)

Well, one thing I sometimes miss is tagging (as in dynamic tiling wm's like dwm) or the possibility to crate hooks for window-classes or something like this. E.g. I've created a hook for my browser, so always when I hit the keys for it, it opens in the "browser-group". But when I open a link in a terminal or somewhere else it opens in the same group as the terminal. So I have to move it manually... I don't know if the fits into a manual tiling wm, but if it's not a big act, musca is nearly the perfect wm for me...
If you don't do this I wont cry.

Thank you for continueing the development of this great app!

tum · 2011-06-24 18:19:16

thehodapp wrote:

So I was thinking about starting to contribute to an open source project for learning experience (in coding and C), and I also really want musca to continue getting better.

Just do it

thehodapp · 2011-06-29 15:25:22

cool! well I'm looking at the code and no promises but I'll see what I can do.

mhertz · 2011-07-02 23:29:33

...Just saw this latest commit from today at the southerncross git-repo:

+# SouthernCross
2
+
3
+## THIS PROJECT IS GOING TO BE DELETED ON 1st AUGUST
4
+
5
+Make sure to clone the project, if you want to keep a copy.
[

whenov · 2011-07-03 07:15:16

Who can help me?
When I start musca, or just run "musca -c ..." command, musca will dump a lot of message, but it runs well.
Here are the messages:
musca.c 3621 setup WM_PROTOCOLS 278
musca.c 3621 setup WM_DELETE_WINDOW 277
musca.c 3621 setup WM_STATE 300
musca.c 3621 setup WM_CLASS 67
musca.c 3621 setup WM_NAME 39
musca.c 3621 setup WM_WINDOW_ROLE 301
musca.c 3621 setup WM_CHANGE_STATE 302
musca.c 3621 setup MUSCA_COMMAND 303
musca.c 3621 setup MUSCA_READY 304
musca.c 3621 setup MUSCA_RESULT 305
musca.c 3621 setup MUSCA_TYPE 306
musca.c 3621 setup UTF8_STRING 282
musca.c 3621 setup _NET_SUPPORTED 307
musca.c 3621 setup _NET_WM_NAME 308
musca.c 3621 setup _NET_CLIENT_LIST 309
musca.c 3621 setup _NET_CLIENT_LIST_STACKING 310
musca.c 3621 setup _NET_ACTIVE_WINDOW 311
musca.c 3621 setup _NET_NUMBER_OF_DESKTOPS 312
musca.c 3621 setup _NET_DESKTOP_NAMES 313
musca.c 3621 setup _NET_CURRENT_DESKTOP 314
musca.c 3621 setup _NET_DESKTOP_GEOMETRY 315
musca.c 3621 setup _NET_CLOSE_WINDOW 316
musca.c 3621 setup _NET_SUPPORTING_WM_CHECK 317
musca.c 3621 setup _NET_WM_WINDOW_TYPE 279
musca.c 3621 setup _NET_WM_WINDOW_TYPE_DESKTOP 318
musca.c 3621 setup _NET_WM_WINDOW_TYPE_DOCK 319
musca.c 3621 setup _NET_WM_WINDOW_TYPE_TOOLBAR 320
musca.c 3621 setup _NET_WM_WINDOW_TYPE_MENU 280
musca.c 3621 setup _NET_WM_WINDOW_TYPE_UTILITY 321
musca.c 3621 setup _NET_WM_WINDOW_TYPE_SPLASH 322
musca.c 3621 setup _NET_WM_WINDOW_TYPE_DIALOG 281
musca.c 3621 setup _NET_WM_WINDOW_TYPE_DROPDOWN_MENU 323
musca.c 3621 setup _NET_WM_WINDOW_TYPE_POPUP_MENU 324
musca.c 3621 setup _NET_WM_WINDOW_TYPE_TOOLTIP 325
musca.c 3621 setup _NET_WM_WINDOW_TYPE_NOTIFICATION 326
musca.c 3621 setup _NET_WM_WINDOW_TYPE_COMBO 327
musca.c 3621 setup _NET_WM_WINDOW_TYPE_DND 328
musca.c 3621 setup _NET_WM_WINDOW_TYPE_NORMAL 329
musca.c 3621 setup _NET_WM_STATE 330
musca.c 3621 setup _NET_WM_STATE_MODAL 331
musca.c 3621 setup _NET_WM_STATE_STICKY 332
musca.c 3621 setup _NET_WM_STATE_MAXIMIZED_VERT 333
musca.c 3621 setup _NET_WM_STATE_MAXIMIZED_HORZ 334
musca.c 3621 setup _NET_WM_STATE_SHADED 335
musca.c 3621 setup _NET_WM_STATE_SKIP_TASKBAR 336
musca.c 3621 setup _NET_WM_STATE_SKIP_PAGER 337
musca.c 3621 setup _NET_WM_STATE_HIDDEN 338
musca.c 3621 setup _NET_WM_STATE_FULLSCREEN 339
musca.c 3621 setup _NET_WM_STATE_ABOVE 340
musca.c 3621 setup _NET_WM_STATE_BELOW 341
musca.c 3621 setup _NET_WM_STATE_DEMANDS_ATTENTION 342
musca.c 3621 setup _NET_WM_PID 343
musca.c 3621 setup _NET_WM_DESKTOP 344

Maybe they are errors, because when I add the "2>/dev/null" suffix, they disappeared.
If anyone could help me, I would be very appreciated.
(Sorry for my poor english)

Army · 2011-07-03 08:50:23

Those are no errors, simply messages. And of course they disappear with "2>/dev/null", that's what that line is for: send all messages to hell.

Last edited by Army (2011-07-03 08:51:24)

whenov · 2011-07-03 12:34:19

Thanks for your reply, but I remember that '2' stands for the "standard error".
If they are just messages, I don't think they should be printed, who needs them?

Army · 2011-07-03 12:55:28

Oh sorry, I think you are right! But still, those aren't errors!

whenov · 2011-07-03 13:46:28

@Army
Thanks so much.

mhertz · 2011-07-03 15:32:23

Those are debug messages, as you are running a dev-build... Btw, it can be disabled in musca.c_ by changing '#define DEBUG 1' to '#define DEBUG 0'...,

cmlr · 2011-07-26 19:34:04

thehodapp wrote:

cool! well I'm looking at the code and no promises but I'll see what I can do.

Thanks! Here's a request. My biggest problem is that I have a wide screen, so I use "pad" to center windows. However, if there are several programs open, only the top one gets resized. The others stick out the sides. So my request is to resize all program windows when pad is used.

nem · 2011-07-30 19:23:21

good day.

anyone else who's having problems with the dmenu implementation - here's what's causing it: dmenu-4.4 with musca
i attatched a patch to my comment which can be applied by entering the source-directory and executing

patch -p1 < musca-0.9.24_patch_dmenufix

before make (or makepkg if you work with abs). i'll add an aur-package if the package gets removed from community. else just patch it manually or use dmenu-4.3.

regards,
nem

edit: beware that the configline for dmenu changed with this patch! you only pass dmenu arguments now. no binary or whatever anymore. so remember to ADJUST YOUR CONFIGFILE before you restart musca!

Last edited by nem (2011-07-30 20:51:25)

cmlr · 2011-08-05 15:52:48

Here's another way to fix the dmenu problem. In ~/.musca_start, change

set dmenu dmenu ...

to

set dmenu dmenu_run ...

nem · 2011-08-05 18:19:22

cmlr wrote:

Here's another way to fix the dmenu problem. In ~/.musca_start, change
set dmenu dmenu ...
to
set dmenu dmenu_run ...

it may fix it for the normal dmenu functionality but it still breaks the musca-command interface because dmenu_path is hardcoded (which is no longer in dmenu-4.4).

tum · 2011-08-06 19:14:12

cmlr wrote:

Here's another way to fix the dmenu problem. In ~/.musca_start, change
set dmenu dmenu ...
to
set dmenu dmenu_run ...

This way breaks Mod4+w , Mod4+g and Mod4+m commands .

mhertz · 2011-08-06 23:21:22

@nem & tum

I've also just changed the default Mod4+x shortcut in .musca_start to instead run 'dmenu_run -b', the day the problematic new dmenu version vas released, and I can still do everything you're talking about fine, like e.g. Mod4+w/g/m...

nem · 2011-08-07 00:53:36

mhertz wrote:

@nem & tum
I've also just changed the default Mod4+x shortcut in .musca_start to instead run 'dmenu_run -b', the day the problematic new dmenu version vas released, and I can still do everything you're talking about fine, like e.g. Mod4+w/g/m...

that's not the same. even though i keep getting 'could not execute: dmenu_run' with your method i'm sure i do something wrong and it works that way. but it's not the most clean solution.

Last edited by nem (2011-08-07 00:54:25)

mhertz · 2011-08-07 01:55:33

Huh? What's not the same?

Anyway...

bind on Mod4+x exec dmenu_run -b

If the above keybind dosen't work for you, then somethings really not right on your end unfortunetly...

Imho, it's indeed a clean solution, i.e. just a single line needs to be added into the external config file .musca_start, instead of having to go patching the musca source files...

Last edited by mhertz (2011-08-07 02:02:33)

tum · 2011-08-07 07:12:46

mhertz wrote:

@nem & tum
I've also just changed the default Mod4+x shortcut in .musca_start to instead run 'dmenu_run -b', the day the problematic new dmenu version vas released, and I can still do everything you're talking about fine, like e.g. Mod4+w/g/m...

I know , this workaround is on the musca archwiki .

nem · 2011-08-07 11:36:08

mhertz wrote:

Huh? What's not the same?
Anyway...
bind on Mod4+x exec dmenu_run -b
If the above keybind dosen't work for you, then somethings really not right on your end unfortunetly...
Imho, it's indeed a clean solution, i.e. just a single line needs to be added into the external config file .musca_start, instead of having to go patching the musca source files...

missed the 'exec' in the bind. i don't use musca startfile usually.
this bind-solution is not the same as the 'set dmenu dmenu_run' solution (obviously) which breaks musca-command.
if you say, a clean solution is just a matter of "makeup", then fine still having invalid calls in a binary is far from clean for my taste. but that's probably just the two different views from a coder and a user.

mhertz · 2011-08-07 13:02:14

@nem & tum

Doh! I apologise, I don't know what I was thinking! (set dmenu... vs bind on...)

@nem

Yeah, I agree! It's imho a clean workaround, not a clean solution

Arch Linux

#551 2011-06-11 15:57:10

Re: Musca (Tiling Window Manager)

#552 2011-06-24 06:36:26

Re: Musca (Tiling Window Manager)

#553 2011-06-24 07:30:15

Re: Musca (Tiling Window Manager)

#554 2011-06-24 07:58:56

Re: Musca (Tiling Window Manager)

#555 2011-06-24 08:32:25

Re: Musca (Tiling Window Manager)

#556 2011-06-24 18:19:16

Re: Musca (Tiling Window Manager)

#557 2011-06-29 15:25:22

Re: Musca (Tiling Window Manager)

#558 2011-07-02 23:29:33

Re: Musca (Tiling Window Manager)

#559 2011-07-03 07:15:16

Re: Musca (Tiling Window Manager)

#560 2011-07-03 08:50:23

Re: Musca (Tiling Window Manager)

#561 2011-07-03 12:34:19

Re: Musca (Tiling Window Manager)

#562 2011-07-03 12:55:28

Re: Musca (Tiling Window Manager)

#563 2011-07-03 13:46:28

Re: Musca (Tiling Window Manager)

#564 2011-07-03 15:32:23

Re: Musca (Tiling Window Manager)

#565 2011-07-26 19:34:04

Re: Musca (Tiling Window Manager)

#566 2011-07-30 19:23:21

Re: Musca (Tiling Window Manager)

#567 2011-08-05 15:52:48

Re: Musca (Tiling Window Manager)

#568 2011-08-05 18:19:22

Re: Musca (Tiling Window Manager)

#569 2011-08-06 19:14:12

Re: Musca (Tiling Window Manager)

#570 2011-08-06 23:21:22

Re: Musca (Tiling Window Manager)

#571 2011-08-07 00:53:36

Re: Musca (Tiling Window Manager)

#572 2011-08-07 01:55:33

Re: Musca (Tiling Window Manager)

#573 2011-08-07 07:12:46

Re: Musca (Tiling Window Manager)

#574 2011-08-07 11:36:08

Re: Musca (Tiling Window Manager)

#575 2011-08-07 13:02:14

Re: Musca (Tiling Window Manager)

Board footer