-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't Modify File Just by Viewing #1966
Comments
The automatic changes issue is discussed at #1354 . For now MarkText would parse the file before showing it in editor, which cause some automatic changes. |
Solution: Offer and "Open for Viewing" menu option, that opens the file as read only. From there the user could switch to "editing mode" if they want. This allows you to keep parsing and changing your internal buffer the way that you already do - just the buffer won't be treated as a file to be saved unless user switches to "edit mode". Thank You. |
@Greg-McPherran As a suggestion, you might close this issue and follow up to #1354 to get latest update related to automatic changes. The dev team are discussing possible option there. I'm also a user who wants the read-but-not-auto-change behavior. |
I'm closing this issue in favour of #2189. You may want to subscribe there for further updates. |
Description
When open existing file just to view, it becomes modified, and because I use AutoSave, it saves the changes. The changes made relate to adding blank line after SetExt heading (e.g. heading 2). When I edit it as text I have no blank line after the SetExt "-----------------" but MarkText adds it. Even if this or other sytnax is not right, I don't want MarkText to change the file automatically (i.e. unless I want it to.)
Great Markdown tool, by the way!!
Steps to reproduce
1 .Edit with normal text editor:
Expected behavior:
File should not be modified and saved automatically (e.g. with blank line added).
Actual behavior:
Blank line is added triggering file save because AutoSave is on.
Versions
The text was updated successfully, but these errors were encountered: