bug? ##-style headers?
john
HTML getting exposed right after doc re-saved! Version 1.4 (221).
- Create a document with a ##-style header. Example:
Expressing Postgres timestamps without zones in local time
You properly save your data in Postgres in UTC. But you want to write some SQL reports
- Save it and open it. Looks fine. Now with an editor change the header to ### and save. I see:
3
id="expressingpostgrestimestampswithoutzonesinlocaltime">Expressing
Postgres timestamps without zones in local time
You properly save your data in Postgres in UTC. But you want to
write some S
-
Switch styles. E.g., from github to Swiss. Now it looks ok. Switch back to github. Looks OK. Switch back to Swiss. OK.
-
Now change the header back to: ##
Now I see:
2
id="expressingpostgrestimestampswithoutzonesinlocaltime">Expressing
Postgres timestamps without zones in local time
You properly save your data in Postgres in UTC. But you want to
write some SQL reports that should express those UTC dates in the
local time, taking into account Daylight Savings Time. One of the
reasons you might do this is because you
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Brett on Aug 26, 2012 @ 08:44 PM
Had a horrible experience today when I realized that over 50 posts had been moved to the spam folder and I wasn't checking it frequently. I apologize sincerely for the delay in response. Please update this issue and let me know if it still exists and I'll respond as quickly as possible.
What I believe you're seeing is a bug in the part of Marked that scans for the last edit. It inserts markup to allow changing the scroll position, but if the edit is at the very beginning of the file it sometimes misses the opening tag and breaks it with inserted markup. Re-saving the file you're editing with a change anywhere else in the document will generally clear it up, or inserting a blank line at the top and saving.
I have this mostly fixed for the next version and will continue testing before release.