On 30-01-2020 02:09, J. Liles wrote:
My thoughts on this:
1) Seems silly not to support the NSM session format, given how easy
it is to read and write.
2) I use git with NSM (and have done so from the start). I recommend
everyone to do so (with a .gitignore file ignoring *.wav files). I
find using git on the commandline easy enough, so that's what I do (I
usually only make a commit before doing something radical, like
switching from recording to mixing phases). But if someone wanted e.g
to have saving the NSM session automatically create a git commit, one
could write a trivial NSM client to do so (just a bash script +
zenity would do)---I see no reason that something so orthogonal
should be built into the server or server GUI.
3) Window placement persistence is better left to the WM. If your WM
doesn't permit this kind of thing, I suggest using a better WM. I
personally use StumpWM and use a fixed frame arrangement with window
placement rules for all the software I use.
Just a reminder: Being very integrated with/embedded in various
orthogonal systems was a major part of what made all the previous SMs
suck.
Yeah certainly not my cup of tea the whole raysession thing, to put it
mildly...
There is a other alternative now, which seems to use nsmd. So it's 100%
compatible with NSM and stays that way according to the description on
the website. So for people who desperately wants a QT GUI, that one
looks to be a better alternative.
https://laborejo.org/argodejo/
Still early in development though, so I would strongly recommend to use
the default Non-Session-Manager. Does what it should do and does it well
and reliable for already more then 7 years now. My 0.02$
