Douglas

@fdncred Fair enough I'll try to experiment with various flavors of this (via hard-coded `source` and `use` statements in `config.nu` for now) to see if I can flesh out the...

Keep in mind that this only covers the "second case" from this issue. The first case is still very valid, and I can't think of a workaround for it. Also...

@melMass Oh yeah ... forgot about that!😆 ```Nushell $env.config.hooks.display_output = { let output = $in # Set $env.lol to false to disable let lolSetting = ($env.lol? | default true) let...

[Related Discord discussion](https://discord.com/channels/601130461678272522/1194025952917856288/1194025952917856288) -- You aren't the only one :-) Also, slight improvement suggested. Instead of: ```Nushell def clsterm [] { $"(ansi esc)c(ansi clsb)(ansi cls)(ansi reset)(ansi home)" } ``` It's...

> not the number of arguments I've provided. Deleted previous response. I think you may be saying that if you provide two directory names as arguments to `rm -rv`, that...

Got it. Also, if that code is being touched, it sure would be nice if the results were returned as a list, I would think.

I get your point; I just wish more of the filesystems commands returned structured data (like the rest of Nushell) that could be useful for logging/debugging/etc. Something like a table...

It looks to me like your first one is greedy-matching up-to-and-*including* the `\r`, which is why you are never seeing it in the resulting `end` match-group. This seems to work...

I agree it would make a good built-in, but I also realized that the `str indices-of` function I put in Discord the other day could probably handle this with some...

Ran into some similar problems with `fzf` passing a preview command-line to `nu`. In that case, it was differences in quoting between POSIX/Fish vs. Nushell. I think there's a case...