Not sure I understand this but... You open a stack, and then try to change the permissions of the directory that it resides in so that you then can't save it? Since the file is already open and "in use" i'm not sure its actually possible to change the permissions under those circumstances. If you create a new folder (empty, or not) and change the permissions on that one (with no open stack or file inside) does the change stick? >>quote livecode seems to be gratuitously unlocking directories.
I launch live code, and then "chmod -w" the directory of the stack. On quit, it restores write permission! If I use shell (chmod -w someDir), it apparently unlocks it before returning from shell! I'm trying to put in a failsafe that prevents overwriting older files. Do I need to change the owner of the files for this??? On Fri, Dec 2, 2016 at 12:20 PM, J. Landman Gay <jac...@hyperactivesw.com> wrote: > On 12/2/16 12:55 PM, Dr. Hawkins wrote: > >> *--livecode's own stacks* >> >> *case* char 1 to 3 of stkNm="Rev" >> >> *case* stkNm="Message Box" >> > > This is no longer the case. Some of LC's stacks no longer start with > "rev". It probably doesn't matter if you back those up anyway, but just so > you know. > > -- > Jacqueline Landman Gay | jac...@hyperactivesw.com > HyperActive Software | http://www.hyperactivesw.com > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
