-
-
Notifications
You must be signed in to change notification settings - Fork 660
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
ls & exa differ for -t
#696
Comments
For those interested; in exa the analogous command is exa -lrm; m is short for --sort=modification |
Also note the sorting order differs between ls & exa, which is why you had to provide I'm quite sure following commands should sort the files in same order, yet they're opposite:
|
I find the lack of support for Excellent software otherwise 👍 |
This comment has been minimized.
This comment has been minimized.
@mschilli87 is there a more supported fork ? |
This comment has been minimized.
This comment has been minimized.
Not supporting the same switches that ls does is kind of a big deal. It's not just muscle memory and the inconvenience of having to remember which system you're shelled in on to use which switches. Imagine you are working in a team that uses a deployment script that does LATEST_BUILD=$(cd |
When running "exa -l --sort=newest" files with the same modified time seem to be randomly ordered, where "ls -latr" is consistent. |
+1 I wish Especially since the It would be great if:
|
Closing this in favor of #519. |
Here are the contents of
man ls
for -there are the contents of
man exa
for -tSince exa uses
-t
as the same flag for--time
it means I cannot copy over some muscle memory filters like:(sort by time reverse chronological)
I ran into this because I alias exa to ls since I really have enjoyed exa that much ! (Thanks!)
The text was updated successfully, but these errors were encountered: