-
-
Notifications
You must be signed in to change notification settings - Fork 41
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
Generated Markdown is not markdown spec compatible #55
Comments
Hello does your "journal.tpl-entry": match the default one "journal.tpl-entry":# ${weekday}, ${localDate}\n\n## Tasks\n\n## Notes\n\n It seem your config lack the "\n\n" after ${localDate} and Tasks and note note. You must edit the vscode settings.json directly. |
I changed it manually at some point and added the \n\n, so I cannot answer this question anymore. I will close this issue until somebody else has this problem. |
Taken your example, the issue seems to be where the memo is placed (directly after the header in this case), correct? I am looking into it (hopefully in the weekend, quite busy atm) |
I have added the current prerelease to this project, can you please download it from here and test it? To test, use the option "Install from VSIX..." in the Extension View of Visual Studio Code. |
The generated markdown is not compatible with the markdownlint default settings (see here).
Maybe spacing after headings etc. should be configurable?
I know I can change my markdownlint settings, but it should really be the other way round I think and a lot of people might be using markdownlint anyway so we should give an option to make vscode journal compatible.
Solutions I could suggest:
A. make spacing after headings configurable
B. make a setting ("fix markdown automatically") that triggers the "fix all all violations in documents" (
markdownlint.fixAll
) of markdownlint if markdownlint is installedThe text was updated successfully, but these errors were encountered: