Andrew Dupont

So I think I understand the problem: * When the parser has just consumed the opening `(`, it sees `li.foo` ahead of it * It can interpret that as a...

The test failure here was spurious (known flaky test) but this'll need a rebase against latest `master` for CI to start working again.

> Should I re-do the implementation to match the others, per [#982 (comment)](https://github.com/pulsar-edit/pulsar/pull/982#discussion_r1571898572)? > > Or is this good to go now that CI is green/passing? It's up to you....

Sadly, I think this is a side-effect of the new Tree-sitter CSS grammar. I described some of its difficulties in #601 — it makes bad guesses about how to do...

This is what I mean: I'm almost certainly about to type a property — something that starts with `padding` — but `tree-sitter-css` thinks it's a tag name. And though it...

Given the following assumptions: * rendering markdown can always be done synchronously * performing syntax highlighting must always be done asynchronously I can't help but think they should be separate...

To be clear, I'm fine with one method doing everything as long as it's always async. I don't have a problem with consuming a method that goes async even when...

I'm revisiting this PR because I'm working on a blog post with _lots_ of code examples in it, and `markdown-preview` is getting slower and slower to re-render at a rate...

> So, @savetheclocktower, if you can share the Markdown you were writing, or at least make an example, maybe we can discuss a way to make it work? What do...

> I do want to quickly shift some of the blame of the syntax highlighting to say that the issues experienced do likely already exist in markdown-preview since we have...