Using Vivaldi on Mac:
- Cursor jumps
- Copying text from the web editor into Drafts removes all line breaks.
Web editor remains unusable for me for any but the shortest posts.
same for me since August, for both. using Brave & Safari
Most of the cursor jump problems should be fixed now. There is still a known issue with using the arrow keys around block quotes.
For copying and pasting text… I don’t use Drafts on the Mac but I tested pasting into BBEdit and TextEdit and all line breaks are preserved.
I have not seen the cursor jumping today. Thank you for that fix. I am still seeing problems with cut-and-pasting removing line breaks and adding extra line breaks, but it’s intermittent and I haven’t been able to suss out a pattern.
I also don’t use Drafts, and I’ve also never seen this from neovim, VS Code, or iA Writer. I do see some weirdness with Obsidian, but that’s because it hides what you’re doing and the same “issues” are apparently when you open the raw text file in any other program or paste to any other text editor. So that’s not a bug, that’s just Obsidian’s styling sometimes not making clear where things are being wrapped versus explicit new lines.
Scheduling is broken from the web. I schedule a post, hit “publish” and the post publishes right away.
Also, I’m still seeing the jumping-cursor problem. It’s not as bad as before, but the cursor jumps a few characters after pasting text.
You’re right, something is wrong. When scheduling, the button is supposed to change to “Schedule Post” instead of “Publish”. I’m trying to figure this out now and will post an update.
On a second look, scheduling is working for me. The date field has to be set after clicking “Schedule Post…” from the menu. The button name is wrong, though, and I’ll have a fix ready for that shortly.
1 Like
not having a blank new line when you terminate the first code fence may be an issue. I’m pretty sure commonmark requires new line separation for consistent behavior in that case.
1 Like
I’m afraid it didn’t help. It renders well so not really a problem.
Does micro.blog follow CommonMark? Can’t find that specified anywhere.
Your site will be built with Hugo, which uses Goldmark– which is compliant with CommonMark 0.31.2 and provides extensions/plugins that are configurable via Hugo configs.
1 Like
In the microblog-react repo I can find markdown-it but it seems to only be used to calculate post lengths? I can’t figure out where the conversion from html/markdown as stored in micro.blog’s database(?) to html happens though. Not that good at React though.
What are the settings there? I would be very interested to see that documented so it’s clear what parts of the spec is always supported on micro.blog.
It has nothing to do with the React part. Your actual blog is built using Hugo. That component of Micro.blog is not open sourced, but it works just like regular Hugo (the MB server part is the db components for storing data and moving files around and producing what Hugo needs to then run and generate the site, among other special sauce) but the actual conversion from your content to HTML is entirely stock what Hugo can do.
You can review here (though note you’ll want docs from the current version of Hugo your blog is on, visible on the Design page) to know what options are available. You can edit them by editing your config.json as a custom design element.
Adding on here. Using double quotes around words in the title field does something odd. It seems to save the title properly but if you go to edit the post what’s displayed there stops at the first double quote in the title.
So this:
This is a “test” post
becomes:
This is a
Thanks for the bug report, sorry about the titles. I’m fixing the problem now and the change should be live shortly.
But is Hugo used for the transformation in the post preview when posting or editing on site? Is it used for the posts on the timeline from other micro.blog users?
Hugo is not used for the preview, so sometimes there are some minor Markdown inconsistencies. Is there any particular Markdown you’re using that isn’t previewing like you expect?
No, just curious 