Dave Abrahams

This took forever to track down! With `flx` and `flx-ido` in your `load-path`, if put the following in `/tmp/x.el` and run `emacs -Q -l /tmp/x.el`, then type "TypeCheck," emacs will...

Build instructions don't work for me

2

``` ➜ iosevka-comfy git:(master) npm run build -- ttf::iosevka-comfy npm ERR! code ENOENT npm ERR! syscall open npm ERR! path /private/tmp/iosevka-comfy/package.json npm ERR! errno -2 npm ERR! enoent ENOENT: no...

Consider making += the default

9

Given that clobbering the existing macro or file is rather a special case, it might be good to swap things around and make appending be the default. I'd suggest `!`...

This looks awesome, but how do I use it?

8

This project looks _extremely_ promising to me; I'm so excited! But I'm not fluent in the idioms of go, so it's not obvious how to build, install, and invoke it....

This method of getting `TOOLCHAINS` set up is obviously too fragile and hacky in the long run, but seems to be working for now. Please squash-merge

$env:Path left with the wrong link.exe being found first

3

[This run](https://github.com/hylo-lang/Swifty-LLVM/actions/runs/8207602540/workflow) demonstrates. Follow the link to the workflow file if you need to reproduce elsewhere. Maybe you could use this as a unit test case for this action.

In my workflow I had: ```yml - uses: seanmiddleditch/gha-setup-vsdevenv@main # ...a bunch of steps... - uses: seanmiddleditch/gha-setup-vsdevenv@main with: host_arch: amd64 toolset_version: 14.37.32822 components: 'Microsoft.VisualStudio.Component.VC.14.37.17.7.x86.x64;Microsoft.VisualStudio.Component.VC.14.37.17.7.ARM64' arch: arm64 # ...more steps... ```...

I mistakenly passed `x86_64` where I should have passed `amd64` and no error occurred in my workflow until much later in my build when I discovered I had incompatible binaries....

Right now only url callbacks are supported. It would be great to be able to click through the notification and bring up the appropriate part of the application.