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.
Thanks for the git trick. So something like:
cd to ~/NSM\ Sessions/my-session-folder
git init
touch .gitignore
echo *.wav >> .gitignore
git add --all
git commit --all
One thing that could improve in the non-session-manager probably is TAB
autocomplete. Most of us know the names of the applications, but most
(new) users would expect to be able to use TAB autocomplete. I think
this feature could help users and developers adopting NSM.
I think it would also fasten things up, if I could use the keybinding
'a' to add new client to the session.
Regards,
\r
