Andrew Dupont

There are four SQL parsers linked from the Tree-sitter homepage: * SQL (SQLite) leads to a repo that is archived. * SQL (BigQuery) is optimized for Google's BigQuery SQL dialect,...

I'd like to hold off on this, if it's OK, for a couple of reasons: * upgrading this far would make it so that @DeeDeeG can no longer run PulsarNext...

OK, I grabbed a lightweight Ubuntu-flavored distro and did some testing on VirtualBox. The script needed some tweaks because of typos and my Bash naïvete, but now it works solidly...

Failing editor test is the one that's known to be flaky. Not going to bother with re-running it for now.

> I'm not sure if `pulsar.sh` was ever expected to work for `.tar.gz` bundles, as it's just as easy to call the `pulsar` binary directly by absolute (full) path as...

Looking back through my commits on the PulsarNext branch, I see that https://github.com/pulsar-edit/pulsar/commit/d9ef212837192666f6400eba2b06c144fc08f559 was supposed to simplify all of this by using the version number as the source of truth:...

After some investigation, here's what I think: * It looks like `yargs` has a shortcut method for `--version` that pre-empts later logic and simply returns specific output if `--version` is...

An update: * #1063 is the best fix for this issue on Windows; it bypasses `Pulsar.exe` altogether. * #1054 improves the situation in all cases where the main Pulsar executable...

I'm digging into the AppImage stuff. The AppImage spec envisions that you might want to set an arbitrary script as the entry point for an AppImage. [It's called AppRun](https://docs.appimage.org/reference/appdir.html?highlight=apprun); you...

The AppImage docs have [this section](https://docs.appimage.org/user-guide/run-appimages.html#extract-the-contents-of-an-appimage) about extracting an AppImage, and it's just what we need. It would allow us to edit the `AppRun.sh` script and then use [appimagetool](https://docs.appimage.org/user-guide/run-appimages.html#extract-the-contents-of-an-appimage) to...