Paul Smith
Paul Smith
https://github.com/marketplace/actions/install-nix
Yes, I desire this, too. It needs a design discussion. Probably the easiest thing to do would be a well-known file in the project directory named like `config.go` or something...
References: * [Overview](https://microsoft.github.io/language-server-protocol/overviews/lsp/overview/) * [Spec](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/) * [VS Code extension guide](https://code.visualstudio.com/api/language-extensions/language-server-extension-guide)
Will need to make the Pushup parser more error-tolerant, since most changes will leave the current document in a broken state.
`^` is interesting: it doesn't look like I need to escape it if I just type it directly in to my Bash shell as part of a filename, but if...
`^` is actually fine in Bash except for as the first character of a command, when it is used for "Quick Substitution" as part of [history expansion](https://www.gnu.org/software/bash/manual/html_node/Event-Designators.html), like: ```sh ^string1^string2...
Another option would be `[`/`]`, as in `[id].up`. Looks like only minimal interaction with shells, mainly in regexes.
This should be fairly straightforward, we need to plumb the name through the build process.
Yes, I think this is a solid improvement and the kind of thing we should take advantage of by having a template language we control.
[Docs](https://caddyserver.com/docs/extending-caddy)