[Octave-bug-tracker] [bug #62467] Severe problem: Octave 7.1.0 destroys actual *.m file

[Michael Leitner]

Follow-up Comment #1, bug #62467 (project octave):

As far as I remember, some text editors for exactly this reason implement the
command typically called just "save" as first saving to a file with a name
that is obviously related to the actual name (like appending an underscore to
the extension), deleting the original file, and renaming the saved file to the
correct filename. This is not really friendly to the metadata of the file (it
always gets a new created timestamp) and directory (it is always changed), but
does not have this problem -- at the worst, the users end up with an
additional underscore in the filename and can rectify themselves. Or are there
some OSes/filesystems that guarantee atomicity for such cases, like via
journalled filesystems?


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?62467>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/