llogick

No guarantees but you could try adding `HostkeyAlgorithms +ssh-rsa` to `~\.ssh\config`.

Client side (edit or create the file `%USERPROFILE%\.ssh\config`), feel like libssh should be checking it.

```zig // Test for `fnCall(.{.})` and `fnCall(Parser.Node{. .some})` because they are handled in different places // Test for completions after `.{` and every `,` pub fn gamma(p: Parser) void {...

Upkeep's been quite light, the only change being https://github.com/ziglang/zig/commit/f258a391daa31b3ba2c37d879db96fadc0c058f3

> Isn't only the `Parse.zig` and the `parse` function from `Ast.zig` needed? That could all be moved into `Parse.zig` to have only a single file. The intention is to keep...

EDIT: Did a ` offsets.tokenToLoc(handle.tree, el_dot_context.identifier_token_index).end,` > Oh yeah, sorry, forgot about this PR - I realised that nested completions don't currently work here, i.e. `@Type(.{ .` will complete but...

> > It'd require some rework but should this be extended to anon struct inits? > > Could give an explanation on how completions would look like with anon struct...

> im messing around with this branch a bit and noticed if i tab thru the list of completions it pastes the text including the snippet placeholders  this doesnt...

Hmm, hmm, hmm ... still undecided if the label should be `name` or `{ .name =` 

> ... `.{ .` should also complete it does, as long as it is after the `const exe = b.addExecutable(...`  The amount of times I've spent back and forth...