Nicolas Goy

For reference, here is a list of common codes: from `sysexits.h` ``` #define EX_OK 0 /* successful termination */ #define EX__BASE 64 /* base value for error messages */ #define...

I also use: ``` addCSourceFile addIncludeDir addSystemIncludeDir want_lto ``` I currently just use `exe.inner` I don't know if we need to wrap all of those.

I just had to do the following: ``` var buf: [100]u8 = .{0} ** 100; const date = std.fmt.bufPrint( &buf, "{d}", .{std.time.timestamp()}, ) catch unreachable; const options = b.addOptions(); options.addOption([]const...

Yeah, a language server would be require for more advanced features. And yes, my plugin only does basic syntax highlighting for now. -- Nicolas Goy

I didn't really do any more work on it, it provides really minimal features for syntax highlight. At present, I am working on another project, and I don't have time...

I am curious, what is your workaround for this?

I think both behaviour should be supported. Default at `/` and default at `/`. My current workaround is to set the default language to something my website does not support.

This is my template that validate: ```xml {{ config.title }} {%- if term %} - {{ term.name }} {%- elif section.title %} - {{ section.title }} {%- endif -%} {%-...

I have a laird dev kit and it has everything on board: https://www.mouser.ch/new/laird-connectivity/laird-bl654-kits/

I stumbled onto this issue. Did you find a work around? let g:formatdef_custom_standard = '"standard --fix --stdin 2>/dev/null"' Don't work because standard return code isn't 1.