On 11/24/18 6:33 PM, Daniel Kian Mc Kiernan (the best Daniel of the bunch) wrote: > On 11/24/18 1:05 PM, paolo m. wrote: >> >> As i change a lyx file name (say test1.lyx ) with a new name (say >> test2.lyx) , by the command 'file -> save as', the new file created has >> the usual access mode, but, when saved, its mode change so that is >> inaccessible to groups and to the world. >> That does not happen when test1.lyx is opened by a text editor, e.g. >> kate, then saved with a new name (say test3.lyx) >> >> Here is the result: >> % ll *lyx >> pol pol test3.lyx 1745 21:54 -rw-rw-r-- >> pol pol test2.lyx 1746 21:53 -rw------- >> pol pol test1.lyx 1745 21:52 -rw-rw-r-- >> >> Any ideas? > > Curious, I checked my own .lyx files, and found that most were 600, > many were 644, and some were 664. There was no clear relationship > between dates and permissions, and at least two files with the same > date had different permissions. > > I blame global warming.
I do not believe LyX sets file permissions itself. The write routine simply uses basic_ofstream, which just creates the file using the current umask, or whatever other default permissions are in place. Riki
