Re: [LAD] Interoperability between session management systems

I was tinkering with saving sessions in a format that is just a directory with a shell script with a standard name (and perhaps some standard arguments) which you call to restore or do other things. Not sure if that's a really feasible solution in general, but it's basically the only way to save sessions in a way that don't require a specific session manager to load, and doesn't impose any file formats. Actually being able to restore sessions decently from a script requires a few more sophisticated jack command line utilities (like a jack_connect that can wait for clients and so on), but those are useful anyway. I like the lowest common denominator, and UNIXeyness, and zero imposition of syntax and so on, of this idea, but haven't really investigated it or done much of an implementation. Being based purely on classic UNIXisms (directory and a script that calls some utilities is all that's going on) is probably the only way to actually get everybody to agree on such a thing. Standardization of such a spec would only involved command line utilities/arguments, paths, and environment variables. Thanks to the shebang mechanism, it would be language agnostic as well. Personally I have no plans to prioritize this, but I think it's an interesting area to explore.