Andrew Dupont

Thanks, that's helpful. Also, you don't need to revert to 1.112; you can insert the following at the end of your `config.cson` file: ```coffeescript ".gfm.source": core: useTreeSitterParsers: false ``` That...

So I'll try to summarize the problem for anyone who might be reading. **If @Atelier-Mirai's description gives you ideas on how to reproduce this, please share them.** [The `tree-sitter-markdown` parser...

> We have added a note to config.cson, but the problem continues to occur. Make sure that the config entry is on its own line in your `config.cson` and that...

I answered you on Reddit, but for posterity, the fix is this: ```sh cd ~/.pulsar/packages/hydrogen # or the equivalent on windows npx electron-rebuild -v 12.2.3 ``` Then relaunch Pulsar or...

> Technically, this is still a bug - Pulsar should be able to do these steps for you. Yeah, that's fair. After this discussion I wondered why this wasn't happening...

I'd follow the directions and run ``` DEBUG=electron-rebuild npx electron-rebuild -v 12.2.3 ``` and see if it produces any useful output.

The subsequence provider is a barely useful fallback provider used when you don't have something smarter. It just suggests words that have already been typed in the buffer — even...

Might need more details on this one. I did a lot of work to force some `\r`s into a file in one of my (macOS) projects. I then did this...

There is a strong convention across lots of parsers to use one `comment` node for all kinds of comments. Use cases that need to distinguish between comment types can use...

There is an API for this, but it doesn't define any conventions about where the project-specific settings live. Two different packages use this API: [project-config](https://web.pulsar-edit.dev/packages/project-config) and [atomic-management](https://web.pulsar-edit.dev/packages/atomic-management). Both expect the...