New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uniform output format when searching a parent directory #107
Comments
How about making this a flag like |
Examples? |
Normally when I'm searching for a file I am intending to do something with it such as edit it with a text editor. If the output is like the original output it is easier to copy and paste into the next command, or to include it in a script to perform some action on each file. A crude example would be:
I think the tree output is great for humans to read, perhaps the tree output could be default unless something like |
@Doxterpepper I still don't see why you don't want "../dir1/file1" (instead of "file1"), while you still tolerate "../dir2/file3". And to copy/paste "file1" is just a double click. NOTE: Your example use ".", not "..". |
I think I misunderstood the description, I thought the suggestion was to include tree style output with ascii decorators and all. Disregard my comments above. |
understanding the requirements better now, would anyone oppose me taking this on? |
No problem, I haven't started on this one. |
Ooops, while fixing #82, I inadvertently implemented this feature. :P |
Sounds good 😄. Would you like to open a PR for that? |
Some superfluous slashes and dots in the output is giving me a headache, #112 only solves part of the problem. (Linux) I need to fix that first. 🤕 |
(courtesy of @iology in #102)
Consider this directory tree:
Now, go to
dir1
and perform a search in the parent directory:The results are correct, but it would be more helpful if the output would look like this (in some order):
The text was updated successfully, but these errors were encountered: