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
When using a defaults profile to export a document, Zettlr 3.1.1 (on Windows 11) defaults to that profile in the next export. When using a custom command, however, Zettlr defaults to a blank export. If this blank export is run (say, because the user inattentively doesn't select something else), Zettlr replaces the existing markdown file with a new markdown file with many (or all) of the markdown characters escaped. Defaulting to the same custom command would both provide an added convenience and avoid potentially overwriting an existing markdown file with a new file where the markdown is "broken."
Proposed Changes
The behavior to default to custom export commands should be the same as the behavior of currently defaulting to exports specified via defaults files.
Caveats
I don't believe there are any, and there's the additional negative outcome of overwriting an existing markdown file that's avoided. Of course, if one wants to overwrite an existing file, one can create an export to do just that separately.
Do you Wish to Attempt Implementing this Yourself?
No
Zettlr Version
Stable (most recent version)
Your Platform
Windows
macOS
Linux
Operating System Version
Windows 10 and 11
Additional Information
The existing UI would work great as shown in the screenshots above---provided that Zettlr remembers and defaults to the most recently run export (whether that's based on a defaults file or a custom command).
The text was updated successfully, but these errors were encountered:
Description
When using a defaults profile to export a document, Zettlr 3.1.1 (on Windows 11) defaults to that profile in the next export. When using a custom command, however, Zettlr defaults to a blank export. If this blank export is run (say, because the user inattentively doesn't select something else), Zettlr replaces the existing markdown file with a new markdown file with many (or all) of the markdown characters escaped. Defaulting to the same custom command would both provide an added convenience and avoid potentially overwriting an existing markdown file with a new file where the markdown is "broken."
Proposed Changes
The behavior to default to custom export commands should be the same as the behavior of currently defaulting to exports specified via defaults files.
Caveats
I don't believe there are any, and there's the additional negative outcome of overwriting an existing markdown file that's avoided. Of course, if one wants to overwrite an existing file, one can create an export to do just that separately.
Do you Wish to Attempt Implementing this Yourself?
No
Zettlr Version
Stable (most recent version)
Your Platform
Operating System Version
Windows 10 and 11
Additional Information
The existing UI would work great as shown in the screenshots above---provided that Zettlr remembers and defaults to the most recently run export (whether that's based on a defaults file or a custom command).
The text was updated successfully, but these errors were encountered: