fwcd
fwcd
Ran into this pretty frequently in a new Swift package... would love to see @redsun82's fix upstream. Even if it doesn't work on Windows, we could just scope it to...
Perhaps it would make sense to split out the update to `tree-sitter` 0.22.6 into a separate PR (or we could just merge #121), so we can then address the CI...
They spawn another (regular) editor containing the expansion:
I agree, haven't dug in too deep what APIs VSCode exposes in this regard, but I think it would be really cool if we could use an "inline editor" for...
The peeked editor approach seems to work well and looks nice too (check the PR description for a screenshot).
Fwiw, my workaround is to run the workflow in a `swift:6` container, but since that's not always feasible, it would be really nice to have this action updated too.
I was mostly just looking for some minor issue to contribute 😄 The sentiment in the aforementioned issue sounded like that was desired and apparently this was the only blocker...
[`llama.cpp`](https://github.com/ggerganov/llama.cpp) and [`llama.swift`](https://github.com/alexrozanski/llama.swift) would be worth investigating, even though the latter might be primarily targeting Apple platforms.
Yeah, I'm still personally interested in this feature and will take a look at getting this PR up to speed once I find some time
Well, forks usually don't need to enable GitHub Actions (and no longer do by default), since pushing to a PR already triggers the `pull_request` event for workflows. Since `mixxxdj/mixxx` currently...