You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi all, nice to see there is some movements on Marktext project from a fork.
One of the most annoying (almost making it unusable, specially if working with git) issues was about opening files, not changing anything, but appears as modified:
I was wondering if you have any plan or idea on how to solve it? This is the best Markdown project by far, but this issue make it hard to use. You dont kow if you changed something or not. Or worst, you open the file, but internally something is changed. Together with a control version system, this is hard to use.
Anyway, thanks for continuing the project. Awesome
The text was updated successfully, but these errors were encountered:
I agree marktext's behavior of modifying files on open is frustrating. Based on the discussion on the issue you linked, I think we are in good company for thinking so.
To be honest, this is beyond what I plan to contribute to marktext. I created this fork to merge together the work of others, and to (hopefully) invite development from the marktext community. If anyone would like to take this issue on, I will do my best to support them in the process.
Hi all, nice to see there is some movements on Marktext project from a fork.
One of the most annoying (almost making it unusable, specially if working with git) issues was about opening files, not changing anything, but appears as modified:
marktext#2189
I was wondering if you have any plan or idea on how to solve it? This is the best Markdown project by far, but this issue make it hard to use. You dont kow if you changed something or not. Or worst, you open the file, but internally something is changed. Together with a control version system, this is hard to use.
Anyway, thanks for continuing the project. Awesome
The text was updated successfully, but these errors were encountered: