Nushell core team meeting 2023-03-08

Attendees

• JT
• Reilly
• Stefan
• Michael
• Andres
• Jakub

Agenda

• fix else if https://github.com/nushell/nushell/pull/8274 but it may be dependent on Restrict closure to {|| blah } https://github.com/nushell/nushell/pull/8290 - Need to find a way forward on these because it's a pain not being able to have else if work reliably.
• auto cd behavior?
  • we have/had parts implemented. feel broken
  • ignored tests
  • cooperation with the completion necessary
  • PR: not there yet https://github.com/nushell/nushell/pull/8261
• rules for hooks
  • Should hooks be a part of nushell outside the interactive use?
    • Relevant for the cratification to have clear boundaries
  • review what we have and what the limitations are.
  • command not found hook
    • https://github.com/nushell/nushell/pull/8314
    • Implementation not yet sane as it introduces a circular dependency between command and cli
  • pre execution hook around atuin
    • some shenanigans in https://github.com/nushell/nushell/pull/8207 about the commnad line buffer
      • Darren's vote is to land as this alone may enable atuin and tests guarantee previous functionality still exists
• output semantics
  • echo vs. print
  • System stdout and stderr are second class citizens in nushell!
  • Goals
    • No noise from scripts
    • But scripts and functions should be usable both interactively and programmatically.
    • empty indicators seem fancy but shouldn't be annoying even when configurable
  • Side topic: when writing this down we should also specify the behavior of what gets put out to external commands in the pipeline. Also behavior when calling nu or nu -c
• alias of parser keywords, need help
• question for andres re: nu! macro

Discussed Topics

Alias refactor

Jakub hit a roadblock for the parser keywords

PR's