Andrew Dupont

> Status: I am reading the quite large commit message and its associated diff, taking breaks for food, etc. It may be a bit before I post more. Fire a...

> The big slowdown seems to have gotten much faster to resolve (and happens much more interactively rather than locking up the main thread) when launching Pulsar with a large...

@DeeDeeG hollered uncle (and fairly so) on having to read [that long commit message](https://github.com/pulsar-edit/pulsar/pull/1251/commits/41aea11bf5847eabe42c8f976bb595acfd31f5c0). Just to make life easier for our future selves, here's a summary of those changes that...

> If you can already get access to it, why not just make it public? I think it would be better to make everything public (since this is a hackable...

OK, I've added my work so far at [@pulsar-edit/jasmine5-test-runner](https://github.com/pulsar-edit/jasmine5-test-runner). When I'm able I'll see if I can write `@pulsar-edit/jasmine2-test-runner` in the same style, then `@pulsar-edit/jasmine1-test-runner`. Ideally I'll be able to...

After some further tests, I can confirm that VS Code's behavior here matches what it does even outside the presence of a repository. If I have a file open in...

The other unknown aspect is how Pulsar, or the `github` package, detects when the user switches branches in a Git repo. I can't find anything in the docs for [git-utils](https://www.npmjs.com/package/git-utils)...

If they don't correspond to any sort of screen display — if there isn't space reserved for them on screen — then there isn't a realistic way to highlight them....

That's true — you could certainly highlight them if you were willing to extend the highlighting to an adjacent character on one or both sides of the `\0`. If you...

Since this approach seems to satisfy you, I'm going to close this issue. Feel free to reopen it if you can describe a bug or enhancement around this problem that...