On Sun, Dec 16, 2018 at 05:56:26PM +0100, paolo m. wrote:
> 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
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 is not only true wh
On Sat, Nov 24, 2018 at 10:11:37PM -0500, Richard Kimberly Heck wrote:
> > 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
On 30/11/2018 14:33, Daniel wrote:
On 24/11/2018 22:05, 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 g
On 24/11/2018 22:05, 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 no
Le 28/11/2018 à 18:13, Richard Kimberly Heck a écrit :
Yes, QFile::setPermissions:
http://doc.qt.io/archives/qt-4.8/qfile.html#setPermissions
We can use QFile::permissions to get the permissions of the original
file, if we want to do that. Presumably, we could create simple wrappers
around
On 11/28/18 11:01 AM, Jean-Marc Lasgouttes wrote:
> Le 28/11/2018 à 15:23, Kornel Benko a écrit :
>> I fear, we have to wait until the c++17 is available.
>> What we do now, is calling
>> ofstream ofs(encoded_fname.c_str(), ios::out|ios::trunc);
>> write(ofs);
>> We are unable to set own pe
Le 28/11/2018 à 15:23, Kornel Benko a écrit :
I fear, we have to wait until the c++17 is available.
What we do now, is calling
ofstream ofs(encoded_fname.c_str(), ios::out|ios::trunc);
write(ofs);
We are unable to set own permissions. With c++17 it will be available to set
them.
Am Dienstag, 27. November 2018 16:23:51 CET schrieb Daniel Kian Mc Kiernan (the
best Daniel of the bunch) :
>
> On 11/26/18 11:23 PM, paolo m. wrote:
> >
> > Daniel Kian Mc Kiernan (the best Daniel of the bunch) wrote:
> >
> >> There is no practical problem for me here, and a practical problem
On 11/26/18 11:23 PM, paolo m. wrote:
Daniel Kian Mc Kiernan (the best Daniel of the bunch) wrote:
There is no practical problem for me here, and a practical problem
could be addressed by chmod. But the situation is puzzling.
Files with access mode: -rw cannot be synced with
Daniel Kian Mc Kiernan (the best Daniel of the bunch) wrote:
> There is no practical problem for me here, and a practical problem
> could be addressed by chmod. But the situation is puzzling.
Files with access mode: -rw cannot be synced with the dropbox
paolo m.
Le 25/11/2018 à 04:11, Richard Kimberly Heck a écrit :
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.
We should probably remember the permis
On 11/25/18 12:00 AM, Daniel Kian Mc Kiernan (the best Daniel of the
bunch) wrote:
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
tes
On 25/11/2018 06:00, Daniel Kian Mc Kiernan (the best Daniel of the
bunch) wrote:
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
test
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 acc
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
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 n
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
18 matches
Mail list logo
