On 2/25/2013 9:38 AM, Terry Brown wrote:
On Mon, 25 Feb 2013 08:02:06 -0600
"Edward K. Ream" <edream...@gmail.com> wrote:
On Mon, Feb 25, 2013 at 7:38 AM, Edward K. Ream <edream...@gmail.com> wrote:
On Sun, Feb 24, 2013 at 10:56 AM, Josef <joe...@gmx.net> wrote:
I just noticed, when opening a file with @auto via a soft link (on Linux)
Leo reads in the file correctly,
but after modifying the content leo replaces the link with an actual
file, which means the original file,
is not modified and you end up with two different versions on disk.
Thanks for this report. Please file an official bug report. This will be
fixed sooner rather than later.
Rev 5605 attempts a fix. All unit tests pass, but it has not been tested
on Linux, where it matters.
The fix has some chance of working: it calls os.path.realpath in
g.os_path_finalize, an important helper used in the write logic, and in
lots of other places.
Terry, Josef, could you test this purported fix and report your results?
Thanks.
Does not appear to be working, sorry.
echo test >d.txt
rm -f l.txt
ln -s d.txt l.txt
(edit l.txt in Leo, adding the word 'here')
grep '' d.txt l.txt
d.txt:test
l.txt:test
l.txt:here
Cheers -Terry
Just a thought - does Leo use os.unlink() to delete files and write them
fresh? Because that would delete the link and write a new file in it's
place.
-->Jake
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at http://groups.google.com/group/leo-editor?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
