Re: lyx changes the file access privileges
On 11/24/18 7:11 PM, Richard Kimberly Heck wrote: On 11/24/18 6:33 PM, Daniel Kian Mc Kiernan 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. Well, all of my LyX files were created with LyX or with cp, and I've not run chmod on them. I've never played with my configuration to change the default permissions. And, as I said, there was no clear relationship between dates and permissions, which would be expected if defaults changed with updates to my OS. I could be very mistaken, but I'm inclined to think both that LyX has at times selected permissions, and that it has selected differently for “Save As…” from what it has selected for “Save”. There is no practical problem for me here, and a practical problem could be addressed by chmod. But the situation is puzzling.
Re: lyx changes the file access privileges
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
Re: lyx changes the file access privileges
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.
lyx changes the file access privileges
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? thank you paolo m.
Re: navigation trouble with 'include' documents
On 11/18/18 10:47 PM, Majzoub, Eric wrote: Hello, I'm not sure if this is a LyX bug or if I'm not using 'include' documents correctly. I have attached a screen shot. The document has about 10 sections. Two of the sections are stand alone .lyx files that I have 'included' in the master document. The first stand alone section has its own reference section in a branch that I have turned off (so it doesn't conflict with the master document reference section). When I go to navigate it shows only the first section heading, and then the branch that is deactivated. When mousing over the deactivated branch it shows the rest of the navigation headings. Have I done something wrong, or is this a bug? Document structure: section 1 --new page-- include file .lyx containing section headings and at the end a branch (deactivated) that has a references section --new page-- include file .lyx containing section headings --new page-- section 3 section 4 section 5 ... Thanks for any help. Eric Just to be sure we're following this correctly, could you post a minimum working example (MWE). We don't need the actual content; an occasional "blah blah blah" will suffice. We do need child documents (again, minus any particular content) and the parent document with the deactivated branch. My initial inclination is to call it a bug, but it might hinge on exactly where the branch boundary is or something else that would be easier to spot in an MWE. Paul
