With nushell's "ls", ripgrep return sufix-result, which may caused by hyperlink

[Kiri2002]

~/Desktop/test> ls                                                                           05/11/2024 11:17:20 AM AM
╭───┬───────────────────┬──────┬──────┬───────────────╮
│ # │       name        │ type │ size │   modified    │
├───┼───────────────────┼──────┼──────┼───────────────┤
│ 0 │ apple_on_tree.txt │ file │  3 B │ 2 minutes ago │
╰───┴───────────────────┴──────┴──────┴───────────────╯
~/Desktop/test> ls |grep on                                                                  05/11/2024 11:17:23 AM AM
│ 0 │ apple_on_tree.txt │ file │  3 B │ 3 minutes ago │
~/Desktop/test> ls |rg on                                                                    05/11/2024 11:17:28 AM AM
│ 0 │ on_tree.txtapple_on_tree.txt │ file │  3 B │ 3 minutes ago │
~/Desktop/test> bash                                                                         05/11/2024 11:17:38 AM AM
[kiri@kiri-laptop test]$ ls |rg on
apple_on_tree.txt
[kiri@kiri-laptop test]$ ls |grep on
apple_on_tree.txt
[kiri@kiri-laptop test]$ ls --hyperlink |grep on
on_tree.txtapple_on_tree.txt

the file name is apple_on_tree.txt.
when I try to use ls|rg to search "pattern"
it will return the "pattern to end" as suffix to the result,

ls |rg on
on_tree.txtapple_on_tree.txt

but grep works well.
(in nushell, use "^ls|rg" works well)
Does it is expected?

[ltrzesniewski]

That's a duplicate of #2762. It's caused by the fact that nushell's ls sends ANSI escapes even when piped to another tool.

In nushell, you can write the following though:

ls | ansi strip | rg on

[BurntSushi]

And also, it's likely that the difference between grep and rg can be explained by the fact that colors aren't enabled for grep (the default) but are for ripgrep (the default). When colors aren't enabled, the hyperlink ANSI escapes will passthrough untouched. But if colors are added, they will likely mess up the hyperlink ANSI escapes.

[Kiri2002]

Thank you all, I totally understand!