Problems with files editing after build #5411

You have encountered a problem using Far Manager? Here you can get help.
Post Reply
bOOT
Posts: 4
Joined: Thu 13 Sep, 2012 18:55

Problems with files editing after build #5411

Post by bOOT » Fri 21 Jun, 2019 13:19

After invent "a new method of saving files: in build #5411 I have many troubles to save changes in files which I was able to edit and save before this invention. The problem is especially when I have no rights to create new file in a given directory or if I have no right to delete edited file. Another problem was with hardlinks, when the data was referenced from more then one paths (hardlinks count > 1) - the edited files defined by its path becomes pretty new file after saving an so leaving original data untouched (and of course the rest of original hardlinks still pointed to old data). The only option was to downgrade to previous version where files editing is working as expected.

I think whole concept of new method of saving files is misleading. If there is a necessity of safer file editing, just make the copy of original file in the same directory as the original file is, or in the %TEMP% or another special local folder if the first method failed for whatever reason (insufficient rights (not only to create and modify but also to delete created file), to long path name, name conflict, etc.). Then rewrites original file (save changes) and if changes have been successfully written, then delete the backup of original file.

bOOT

pepak
Posts: 444
Joined: Sun 13 Jul, 2008 11:18
Has thanked: 9 times
Been thanked: 25 times

Problems with files editing after build #5411

Post by pepak » Fri 21 Jun, 2019 15:09

You may want to write in my bugreport here that #5411 really should be optional. There seems to be a doubt on part of the developers that it is so.

You will also find a patch that fixes the problem by providing an option to use the original behavior. Unfortunately, you need to compile your own FAR to make use of that.

Post Reply

Return to “Support and Troubleshooting”