Edit - Super User

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

It's strange this is the accepted answer as it does NOT cleanly answer the question: "How can I list files recursively with the nu shell?", but only gives convoluted examples with all kinds of filters and exceptions
– reinier
Commented Mar 2, 2023 at 12:56
@reinier I tend to answer the question asked in the body rather than just the "summary" or "title". The normal ways of recursively listing the files with nushell are covered in the question itself. My answer covers why these weren't working for the OP's specific use-case. Since it properly explained the observed behavior, the OP accepted ....
– NotTheDr01ds
Commented Mar 2, 2023 at 13:37
I found this page as I had the exact same question: How to list files recursively as ls -r doesn't exist. Stackoverflow works best if I go to the accepted answer and just read the solution without needing to find it hidden in the question itself somewhere. If I want to understand the why, and dive deep, it's great that more text and explainers are given. With google surfacing this page as the first hit for listing files recursively it might be a good edit to list the intended way to do it, and then explain with more text on why it has issues and possible workarounds....
– reinier
Commented Mar 3, 2023 at 19:27
1

@reinier See my updated answer below (or perhaps above) that address the "general" use-case now that the bug is resolved. Again, for this particular question/answer, we had to work around a bug that existed at the time, along with the OP's actual request (which was more complex than simply "recursively listing files".
– NotTheDr01ds
Commented Mar 3, 2023 at 20:12
Thats really helpful for probably most people landing on this page. Thanks
– reinier
Commented Mar 6, 2023 at 18:04

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)
<https://example.com>
[example](https://example.com)
<a href="https://example.com">example</a>

formatting help »
answering help »