Jakub Žádník

The use case for stripping ansi sequences is if you want to do something like `ls | find blah | each {|it| rm $it.name }`

`extern-wrapped` could be used for this purpose, as it forces `...rest` to be strings. Similarly, `extern` also forces all undefined args to be strings.

The second part of the problem is being able to pass flags to custom commands. We still don't have a mechanism for that, see https://github.com/nushell/nushell/issues/9116

Passing flags to externals seems to be solved with `def --wrapped` and the spread operator, so I'll close it. The remaining issue of passing named flags to Nushell commands is...

It shows a bug in `export alias`, it shouldn't fail like that. But the issue can be closed, the correct way to activate the environment is `overlay use`.

I think the problem is related to command queues. The kernel 1 is on the remote server CQ while the enqueued migration and kernel 2 are on the host device...

I believe that currently, both input and output types are required, and also `:`. The parser currently is not tight enough and does not report wrongly typed input/output types. I...

Yes, definitely the docs need to be updated, I was just clarifying the syntax. The issue could live in https://github.com/nushell/nushell.github.io but here is also OK because we should update the...

You can now import a whole directory as a module, see https://www.nushell.sh/book/modules.html#modules-from-directories, https://github.com/nushell/nushell/pull/9066. I think this fulfills the requirement of "source all files in a directory" as in Nushell we...

OK, so the activation command being a list is no longer necessary?