On Mon, Nov 22, 2010 at 10:33 AM, Sebastian Guttenberg
sgut...@math.ist.utl.pt wrote:
This was changed to solve bug http://www.lyx.org/trac/ticket/6587.
Now we move the file to the backup file before saving the current file.
So, we basically do not overwrite the original file, but we move away
On Mon, Nov 22, 2010 at 10:33 AM, Sebastian Guttenberg
wrote:
>> This was changed to solve bug http://www.lyx.org/trac/ticket/6587.
>>
>> Now we move the file to the backup file before saving the current file.
>> So, we basically do not overwrite the original file, but we
This was changed to solve bug http://www.lyx.org/trac/ticket/6587.
Now we move the file to the backup file before saving the current file.
So, we basically do not overwrite the original file, but we move away
the original read-only file and write a new file.
I have read the discussion
> This was changed to solve bug http://www.lyx.org/trac/ticket/6587.
>
> Now we move the file to the backup file before saving the current file.
> So, we basically do not overwrite the original file, but we move away
> the original read-only file and write a new file.
I have read the
Hi all
I have a very strange behaviour of lyx2.0. I can modify (and save)
write-only files!! Within lyx they are not indicated as being read-only
and after modifying and saving them, the old write-protected file was
indeed overwritten and its mode change to writable.
I have done the same
I have tested again, and the behavior has changed a bit. This time the
read-only file was respected. Let me give you something reproducible.
Just do the following steps:
* start a new file and save it as test.lyx (don't close it)
* open a terminal and change the file permissions to read-only:
Op 21-11-2010 22:07, Sebastian Guttenberg schreef:
I have tested again, and the behavior has changed a bit. This time the
read-only file was respected. Let me give you something reproducible.
Just do the following steps:
* start a new file and save it as test.lyx (don't close it)
* open a
On Mon, 2010-11-22 at 01:10 +0100, Vincent van Ravesteijn wrote:
So, the only bug is that when LyX2.0 opens a LyX1.6.5 file, the
read-only flag is not set correctly?
This is the same problem as reported in bug
http://www.lyx.org/trac/ticket/7035 and discussed in the following
thread
Op 22-11-2010 1:44, Sebastian Guttenberg schreef:
On Mon, 2010-11-22 at 01:10 +0100, Vincent van Ravesteijn wrote:
So, the only bug is that when LyX2.0 opens a LyX1.6.5 file, the
read-only flag is not set correctly?
This is the same problem as reported in bug
Vincent van Ravesteijn wrote:
The document ~/test.lyx could not be saved.
Do you want to rename the document and try again?
Rename Retry Cancel
This was changed to solve bug http://www.lyx.org/trac/ticket/6587.
Now we move the file to the backup file before saving the current file. So,
Am 22.11.2010 um 01:10 schrieb Vincent van Ravesteijn:
Op 21-11-2010 22:07, Sebastian Guttenberg schreef:
I have tested again, and the behavior has changed a bit. This time the
read-only file was respected. Let me give you something reproducible.
Just do the following steps:
* start a new
Hi all
I have a very strange behaviour of lyx2.0. I can modify (and save)
write-only files!! Within lyx they are not indicated as being read-only
and after modifying and saving them, the old write-protected file was
indeed overwritten and its mode change to writable.
I have done the same
I have tested again, and the behavior has changed a bit. This time the
read-only file was respected. Let me give you something reproducible.
Just do the following steps:
* start a new file and save it as test.lyx (don't close it)
* open a terminal and change the file permissions to read-only:
Op 21-11-2010 22:07, Sebastian Guttenberg schreef:
I have tested again, and the behavior has changed a bit. This time the
read-only file was respected. Let me give you something reproducible.
Just do the following steps:
* start a new file and save it as test.lyx (don't close it)
* open a
On Mon, 2010-11-22 at 01:10 +0100, Vincent van Ravesteijn wrote:
> So, the only bug is that when LyX2.0 opens a LyX1.6.5 file, the
> read-only flag is not set correctly?
>
> This is the same problem as reported in bug
> http://www.lyx.org/trac/ticket/7035 and discussed in the following
> thread
>
Op 22-11-2010 1:44, Sebastian Guttenberg schreef:
On Mon, 2010-11-22 at 01:10 +0100, Vincent van Ravesteijn wrote:
So, the only bug is that when LyX2.0 opens a LyX1.6.5 file, the
read-only flag is not set correctly?
This is the same problem as reported in bug
Vincent van Ravesteijn wrote:
>> "The document ~/test.lyx could not be saved.
>> Do you want to rename the document and try again?
>> "
>
> This was changed to solve bug http://www.lyx.org/trac/ticket/6587.
>
> Now we move the file to the backup file before saving the current file. So,
> we
Am 22.11.2010 um 01:10 schrieb Vincent van Ravesteijn:
> Op 21-11-2010 22:07, Sebastian Guttenberg schreef:
>> I have tested again, and the behavior has changed a bit. This time the
>> read-only file was respected. Let me give you something reproducible.
>> Just do the following steps:
>>
>> *
18 matches
Mail list logo