Darren Schroeder

i'm not good with many of these.

seems like the 'to pipe' is quite a bit like fish shell's psub. seems like a custom command may be able to work this way similar to @RGBCube's. https://fishshell.com/docs/current/cmds/psub.html https://github.com/fish-shell/fish-shell/blob/master/share/functions/psub.fish

You may also use bench. This starts up nushell 100 times and gathers stats. ```nushell ❯ use std/bench * ❯ bench { nu -n --no-std-lib -c '$nu.startup-time' } --rounds 100...

Another thing you can do is run `nu --log-level info`. Running it with `info` triggers the `perf!()` macros to run in the code and display startup performance log lines showing...

Ya, I've always thought the pipes belong on the right side for the same reasons. I have this in my keybindings because the problem with alt-enter is that it's not...

It should fail like this. not sure why it doesn't. ```nushell ❯ def foo [] { ::: foo ::: } ❯ foo Error: nu::shell::recursion_limit_reached × Recursion limit (50) reached ╭─[entry...

@bartoszwjn if you have time, it would be good to test #14114 in your real-world scenario to see if that fix works for you.

I think this should do it. You can change `use_ansi_coloring` in your config.nu ``` $env.config.use_ansi_coloring = false ``` https://github.com/nushell/nushell/blob/55a5652a9112a2ed7db2cacd914a378c7e68ea53/crates/nu-utils/src/default_files/doc_config.nu#L255-L269

My prompt is monochrome with oh-my.nu in nu_script repo.

As a Windows user part of the time, it seems reasonable to me. I agree that 100% of commands don't have --help but meh 🤷🏻 I'm not really worried about...