Bahex

Finally took a second look at this. As far as I can tell, the problem stems from the fact `each` is a **streaming command**. It doesn't process all of its...

If the answer isn't accurately describing the problem and the `collect` does not solve the issue, feel free to reply.

@fdncred I'll take a proper look tomorrow but I already have some guesses.

I think there is two separate bugs here: - switches are typed `any`: - type widening on table columns results in `nothing` instead of `any`:

@fdncred Found the cause of the incorrect table typing too: - \ - \ I'm going to fix it at the call site for now, but we should reconsider if...

I'm thinking of a more general solution for handling terminal interactions (see [Terminal Event Hooks for Reedline](https://hackmd.io/@nucore/vibesmap#Terminal-Event-Hooks-for-Reedline)) that would make querying the terminal much more robust, which solves half of...

My workaround is to just embed the text directly using `mkLiteral`. The attr key has to start with `//` to become a comment in the final file. ``` extraConfig =...

@fdncred 1. GitHub accounts can be linked on discord profiles 2. It uses the GitHub accounts linked to commits, so different names an emails shouldn't matter as long as they...

From what I can tell, this is related to how externals' stdout and stderr are handled, and positions where their output is collected. ### Solution ```nushell seq 1 1 |...

Because this is just the inevitable result of how various nushell features interact, I feel like the actual problem is a lack of documentation. I will close this issue after...