Expected behaviour
When saving changes to an existing, previously created file, Pluma should only modify the modified date timestamp, not any other file metadata that isn't explicitly modified in the edit.
Actual behaviour
'Upstream': https://gitlab.gnome.org/World/gedit/gedit/-/issues/464
gedit and Pluma saves any changes as a new file every time, which stomps over file creation timestamps and other metadata.
Other editor frameworks such as Featherpad (Qt), Scite, atom/Pulsar and VS Code do not have this problem.
Steps to reproduce the behaviour
- Save text to a new file.
- observe file properties in Files / Caja, specifically the timestamps
- Wait one minute
- make one byte change to the file. Save change/modification with Ctrl+S
- observe the file properties. The creation and access timestamps are updated along with the modified timestamp.
MATE general version
All
Package version
All
Linux Distribution
Affects all
Link to bugreport of your Distribution (requirement)
n/a
Expected behaviour
When saving changes to an existing, previously created file, Pluma should only modify the modified date timestamp, not any other file metadata that isn't explicitly modified in the edit.
Actual behaviour
'Upstream': https://gitlab.gnome.org/World/gedit/gedit/-/issues/464
gedit and Pluma saves any changes as a new file every time, which stomps over file creation timestamps and other metadata.
Other editor frameworks such as Featherpad (Qt), Scite, atom/Pulsar and VS Code do not have this problem.
Steps to reproduce the behaviour
MATE general version
All
Package version
All
Linux Distribution
Affects all
Link to bugreport of your Distribution (requirement)
n/a