Matlab creates conflict file when saving

Hello!
There is a problem when I save a script I'm editing. To be more precise: I have a script that I have saved as "rhoder2.m". I edit and save it. Then the "rhoder2.m" goes back to what it was before the edit and the changes are saved in a file "rhoder2_conflict-20190308-105811.m". And this happens every time (no need to run it) and I don't understand why. Does anyone know how it can be fixed?
Thank you in advance!

 Akzeptierte Antwort

Guillaume
Guillaume am 8 Mär. 2019

0 Stimmen

Conflict files are typically created by version control systems. They're not normally generated automatically but on commit. Perhaps, you have your version control system set to auto-commit.
Another possibility is that your folder is synchronised by some cloud client (dropbox, onedriver, etc) and the client detects that the file has been changed on another system.
Either way, it's most likely nothing to do with matlab. What happens if you save the file in a completely differrent folder?

2 Kommentare

Eve_B
Eve_B am 8 Mär. 2019
Oh, ok! I don't have a version control system (you mean like git, right?), but I do save in a cloud synchronised folder. Although it is not being changed on another system. I'll turn off the cloud and see how it goes!
Eve_B
Eve_B am 8 Mär. 2019
Paused the cloud and stopped producing conflicts.
Thank you very much!

Melden Sie sich an, um zu kommentieren.

Weitere Antworten (0)

Kategorien

Mehr zu Environment and Settings finden Sie in Hilfe-Center und File Exchange

Produkte

Version

R2017a

Gefragt:

am 8 Mär. 2019

Kommentiert:

am 8 Mär. 2019

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by