go to post Stefano Cairoli · Jul 1, 2016 While I don't know the answer, I simple wanted to add a rough Google translation, hoping that this may be of help in getting some suggestions:---Mounted on Aix7.1 root user to install cache2016.1.1.107, and create cacheusr users during the installation process; after the change umask cacheusr the operating system, modify the file compiled by the database (eg, js, csp, etc.) on the small plane permission to view unchanged (-rwxrw-r-- cacheusr cacheusr test.js).Objective: readable and writable by other users database compiled files.---
go to post Stefano Cairoli · Jun 30, 2016 Thank you Dmitry,really an interesting example, I wasn't aware of this feature in bash.Unfortunately it seems like I cannot use it 1-to-1 under MacOS, but I may try following some of the guides on how to make the Mac-bash completition-aware using "brew".
go to post Stefano Cairoli · May 30, 2016 Hi,I just add the opportunity to look back at the old Studio 5.0.x, and the Read-Only flag in the Open dialogue didn't have a registry value that would it make "sticky".I remember once coming up with an approach by using the GetStatus() method on a class extending %Studio.SourceControl.Base:one of the supported parameters is "Editable", where you could set this to 0 inside of this method to prevent editing of the open item.Not really a direct solution to your question, but if you happen to already be using Studio hooks, it may be worth a look.HTH
