As explained in the title, when one opens an existing document with Xed and then saves the document, instead of just an update of the content of the file and of the modification time, the document is in fact saved in a brand new file, with a new inode number and an updated creation time.
This renders unreliable the creation time for the document.
The problem does not occur with other editors like nano for instance.
Steps to reproduce
Check the timestamps of a document in a file explorer
and/or
Check the inode and timestamps in command line using:
1- stat /path/to/document
2- sudo debugfs -R 'stat /full/path/to/document' /dev/sdXn | grep crtime
Open the document with Xed
Save it as is
Check the inode number and timestamps again
Expected behaviour
The inode number should be unchanged.
The creation time should stay unchaged too.
Other information
I have also tested with gedit in Manjaro 18.02 and the problem occurs there too, so maybe the problem is in a package on which both Xed and gedit depend, but this is hard to tell from the user's side.
Issue
As explained in the title, when one opens an existing document with Xed and then saves the document, instead of just an update of the content of the file and of the modification time, the document is in fact saved in a brand new file, with a new inode number and an updated creation time.
This renders unreliable the creation time for the document.
The problem does not occur with other editors like nano for instance.
Steps to reproduce
Expected behaviour
The inode number should be unchanged. The creation time should stay unchaged too.
Other information
I have also tested with gedit in Manjaro 18.02 and the problem occurs there too, so maybe the problem is in a package on which both Xed and gedit depend, but this is hard to tell from the user's side.