Live data from Hacker News

Eza: A modern, maintained replacement for ls

github.com

201–210 of 250 posts

Re: Eza: A modern, maintained replacement for ls

#201

Earlier quoted context omitted.

You can hover over the date for an exact timestamp. Maybe someone can write a userscript to replace the relative dates to exact ones.

the point is that you should not need to hover over the dates to get the exact ones. it hinders fast viewing of the data, when it is more than a small amount.

Depends on the application and your personal preference. It's way "faster" for me to see a HN comment was posted "1 hour ago" than it is for me to see the absolute time string and do the math myself. Further, I don't care about the exact time a HN comment was made. I care about roughly how long ago it was posted so I know if the conversation is still going.

Re: Eza: A modern, maintained replacement for ls

#202

There is also 'lsd' but I still prefer eza. For everyone interested there is a lot of modern command line tools I nowadays prefer over the old stuff: bat - cat with highlight difftastic - better diff gdu - ncdu for ssds (disk space analyser) zoxide - modern cd fd - find alternative rg - ripgrep (grep) fzf - fuzzy finder jless - json viewer with mouse folding dra - download and install release assets lazygit - git TUI…

As someone who defaults to lsd, is there any reason why you prefer eza to it?

Re: Eza: A modern, maintained replacement for ls

#203
post #68
post #14

What's the point, though? You still have to rely on POSIX and / or GNU tools in most scenarios, and if already knowing / using those, then why bother to switch to anything else?

The only time you have to care about GNU tools vs your own preference of tool is when writing scripts to run on computers running some Linux distributions, and per [1] you shouldn’t be using ls for that. [1]: https://www.shellcheck.net/wiki/SC2045

Yes but if you work professionally as a software engineer, chances are that you don't only use your PC. Being that a server that you connect remotely to develop on, or a production system where you connect to investigate a bug, or the PC of a coworker you are helping, or getting inside a container, etc.

Getting to know and use a standard setup makes you efficient in that situations, that is also the reason why I learned to use vim (since vim or at least vi you can take for granted there is on every system).

The only concession that I make is the shell, since zsh is much more convenient to use than bash, even if every time I use a system with bash I of course write some code that works in zsh and have to remember that in bash you can't do it. That is annoying, but to me it's worth it to use a better shell, not worth probably for an `ls` clone.

Re: Eza: A modern, maintained replacement for ls

#205

[flagged]

I would agree with you but in this case the author is catering to both types of users. Which is perfectly acceptable in my opinion. If they wrote eza to only accept UK spelling, then you'd have a stronger argument.

Personally while I use UK spelling all my tools will use color as an option flag.

Re: Eza: A modern, maintained replacement for ls

#206

There is also 'lsd' but I still prefer eza. For everyone interested there is a lot of modern command line tools I nowadays prefer over the old stuff: bat - cat with highlight difftastic - better diff gdu - ncdu for ssds (disk space analyser) zoxide - modern cd fd - find alternative rg - ripgrep (grep) fzf - fuzzy finder jless - json viewer with mouse folding dra - download and install release assets lazygit - git TUI…

I didn't find zellij to be better than screen. The tabs/screens are not numbered correctly so switching directly to them requires manually counting. A non-starter for me.

If you don't like the default tab bar, you can use the zjstatus plugin (https://github.com/dj95/zjstatus) to replace it with a customizable one that can show the tab index.

Re: Eza: A modern, maintained replacement for ls

#207

There is also 'lsd' but I still prefer eza. For everyone interested there is a lot of modern command line tools I nowadays prefer over the old stuff: bat - cat with highlight difftastic - better diff gdu - ncdu for ssds (disk space analyser) zoxide - modern cd fd - find alternative rg - ripgrep (grep) fzf - fuzzy finder jless - json viewer with mouse folding dra - download and install release assets lazygit - git TUI…

This link also has a large list of additional tools I hadn't heard of but look interesting. https://github.com/ibraheemdev/modern-unix

this one is maintained

https://github.com/johnalanwoods/maintained-modern-unix

Re: Eza: A modern, maintained replacement for ls

#208

How are people paging with these ls replacements? I wish with all the features it includes some guidance about which pager is suitable. more? less? something else? how does the pretty colors work with paging?

I use the --color=always option with eza. This allows it to be piped through less and still maintain the color.

To avoid having to type that option every time, I have a bash alias for ls:

  alias ls='eza -F --color=always'

Re: Eza: A modern, maintained replacement for ls

#209
post #205

[flagged]

I would agree with you but in this case the author is catering to both types of users. Which is perfectly acceptable in my opinion. If they wrote eza to only accept UK spelling, then you'd have a stronger argument. Personally while I use UK spelling all my tools will use color as an option flag.

I only looked at the repo home page. The license file was named LICENCE and the README used "colour." Looks like the author is Danish.

Re: Eza: A modern, maintained replacement for ls

#210
post #121

One pet peeve of mine is "human readable dates", especially for a directory listing. If I'm scanning for something I copied into a folder yesterday amongst other things, I don't want everything to show "1 day ago" if I'm looking for something I did around 11am. I want the dates and times. That goes for forums like HN. Show me the date/time and also "7 hours ago" or whatever if you have to. I've never understood takin…

Yeah that is such an amazing anti-feature. And how do you deal with changes? Like, when does 1 day ago become 2 days ago? According to google it becomes two days ago after 48 hours. That means if you look at your phone after 47 hours it will say 1 day ago and you'll be tricked into it happening yesterday. Human readable my ass. Or, you know the specific day because it was the day after your friends birthday or whatev…

The intent make sense (humans are better at durations than with absolute timestamps), but the lack of granularity is ridiculous. It should be "1d 20h ago" or based on the dates in question maybe more or less granual. (It's a hard UX problem, but that just means that the program ought to know what the user wants. What's important to them. Are the searching for something? What patterns to highlight? Ie. if there's a directory with a 1000 files but only 2 old ones maybe put some emphasis on them, etc.)
Post reply on HN