Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with tree
Search options not deleted
user 904401
1
vote
1
answer
22
views
Why are UTF-8 paths (differently) escaped in outputs across core CLI utilities?
shell (sh, of course, but also bash, in Fedora 40) shall be able to interpret it without issue:
ls "$PWD"
' [-]'$'\t''`{title: "Non-Metadata",'$'\t''id: "s4a4ji"}`{.JSON5}.dir'
Octet
However, tree … I would expect ls, tree, and file to at least operate identically, considering that - to my knowledge - these are GNU CoreUtils. …
