Auto-generated tar.nu has a syntax error

[RReverser]

Error: nu::parser::parse_mismatch (link)

  × Parse mismatch during operation.
    ╭─[C:\Users\me\Documents\nu_scripts\custom-completions\auto-generate\completions\tar.nu:10:1]
 10 │   --get(-x)                                       # Extract from archive
 11 │   --help(-\?)                                     # Display short option summary
    ·  ─────┬─────
    ·       ╰── expected short flag
 12 │   --usage                                 # List available options
    ╰────

[fdncred]

ya, i don't think \? is a thing in nushell. prs welcome of course.

[RReverser]

Perhaps it's worth automatically checking generated .nu files for validity, and automatically removing the invalid ones from the repo for now?

[fdncred]

that would be nice but we don't have a clippy or fmt checker for nushell. all we have now is nu-highlight. we might just change the auto-gen script to handle ? correctly, whatever "correctly" is.

[RReverser]

Hm. Wouldn't it be possible to literally launch another instance of nu just with the use ...generated module... and check the exit code?

[fdncred]

I'm not sure. I've seen that running nu inside of nu sometimes can give weird results. Maybe that's been fixed? There is a pr now for nu-check which I just saw this morning. Maybe that'll land soon.

[AucaCoyan]

Hi! This was fixed in #783 and later exported in #815 I think this can be closed