Richard, seriously though, if you have any coherent thoughts on the matter it would be interesting to hear them. It's a much more complicated issue than people assume and it overlaps with another complicated issue that I don't want to even bring up.
Personally, I have some scripts that import symlink'd files, remove unused sources and things like that, but this is all specific to Non. Making something that would work for all clients is a much bigger problem. On Sun, Jan 3, 2021 at 5:50 PM Richard <[email protected]> wrote: > On Mon, 4 Jan 2021 01:32:47 +0000 > Filipe Coelho <[email protected]> wrote: > > > I really think these sorta things belong in a GUI, not in a script. > > And I really think this discussion does not belong in a community > thread which provides an opportunity for the community to express > thanks for the Non suite of programs. By the way, as there is obviously > a lot of doubt around about what "community" means here, it is, of > course, the NON user community. > > Now, as to your singularly fine suggestion that NON project export > needs a GUI, I agree. I had to pause after writing that because it > surprised me that I should agree to a suggestion to add more bloat to > an admirably lean session management system. There is only one thing > missing from your necessarily brief conclusion; you will write this > export GUI program yourself and make it an NSM-compliant helper > program. > > By the way, if you do get around to this, I really hope that your idea > of what is required to "export" a session is pretty damn close to my > thoughts on the subject. But even if your view differs from mine, I > can always use your solution as the basis for my preferred form of > "export" and we would gain so much more flexibility in how or what to > export than any "jack of all trades" solution which doesn't really > belong in NSM (imho, of course). > > -- > Richard <[email protected]> > > >
