5 ms·

The main problem I can think of is that I'm so used to type cd and then ls... But OTOH it's as simple to fix as alias ls=exa EDIT: "exa prints human-readable

The main problem I can think of is that I'm so used to type cd and then ls... But OTOH it's as simple to fix as alias ls=exa EDIT: "exa prints human-readable file sizes by default (when would you not want that?)" I actually use bytes a lot for certain progress calculations. Also I get an error "exa: error while loading shared libraries: libhttp_parser.so.2.1: cannot open shared object file: No such file or directory" (Ubuntu 17.04)

PascLeRasc 9y ago
Yeah, the 'cd' and 'ls' combo is so easy to type too. 'exa' feels more difficult since my left middle finger has to contort a little going from e to x.
erichurkman 9y ago
Why does a directory lister need an HTTP parser?
- rrdharan 9y ago
  I am wondering that too, but FWIW `sudo apt-get install libhttp-parser2.1` will have you on your way.
  - assafmo 9y ago
    Thanks, but I wanted to report it nevertheless because it says the file is self contained.
    - steveklabnik 9y ago
      A bug was filed a week ago https://github.com/ogham/exa/issues/194 https://github.com/ogham/exa/issues/194
- steveklabnik 9y ago
  This binds to libgit2, which binds to curl. I believe that brings it in.
  - cytzol 9y ago
    You are correct. exa uses libgit2 for its Git column, and the library's networking parts must still be included when they aren't even being used anyway. I can see how it looks VERY SUSPICIOUS for a file lister to be parsing HTTP headers! I'm not going to sell your directory entries to advertisers, I promise.
    - kibwen 9y ago
      For more paranoid folks, it would be nice to have a configuration option to forego the git features and thereby remove the need for linking in any networking code. :)
      - steveklabnik 9y ago
        There is one already; it's a cargo feature.
        Pewqazz 9y ago
        I wrote the original Homebrew formula for exa and remembered adding support for the Git-less install, so I was surprised to see it wasn't there anymore! Seems like it was removed in this version bump [1] — I'll open a PR adding it back in. [1]: https://github.com/Homebrew/homebrew-core/pull/13676 https://github.com/Homebrew/homebrew-core/pull/13676
- deleted 9y ago
  [deleted]
dvfjsdhgfv 9y ago
> The main problem I can think of is that I'm so used to type cd and then ls... But OTOH it's as simple to fix as alias ls=exa Are you really sure you want to replace ls with exa? I can think of a dozen reasons it could cause trouble.
- assafmo 9y ago
  It will definitely be easier to check it out this way.
- cytzol 9y ago
  I've been aliasing "l" and "ls" to "exa" for years now. Aliases in your shell won't cause any problems, because any scripts you run won't follow the aliases and will just use ls normally. Actually replacing the binary? That would cause so many problems!
deleted 9y ago
[deleted]
NuSkooler 9y ago
⋊> ~/Downloads unzip exa-linux-x86_64-0.7.0.zip Archive: exa-linux-x86_64-0.7.0.zip inflating: exa-linux-x86_64 ⋊> ~/Downloads ./exa-linux-x86_64 --version 15:26:40 ./exa-linux-x86_64: error while loading shared libraries: libhttp_parser.so.2.1: cannot open shared object file: No such file or directory ...yup.

PascLeRasc 9y ago

Yeah, the 'cd' and 'ls' combo is so easy to type too. 'exa' feels more difficult since my left middle finger has to contort a little going from e to x.

erichurkman 9y ago

Why does a directory lister need an HTTP parser?

rrdharan 9y ago
I am wondering that too, but FWIW `sudo apt-get install libhttp-parser2.1` will have you on your way.
- assafmo 9y ago
  Thanks, but I wanted to report it nevertheless because it says the file is self contained.
  - steveklabnik 9y ago
    A bug was filed a week ago https://github.com/ogham/exa/issues/194 https://github.com/ogham/exa/issues/194
steveklabnik 9y ago
This binds to libgit2, which binds to curl. I believe that brings it in.
- cytzol 9y ago
  You are correct. exa uses libgit2 for its Git column, and the library's networking parts must still be included when they aren't even being used anyway. I can see how it looks VERY SUSPICIOUS for a file lister to be parsing HTTP headers! I'm not going to sell your directory entries to advertisers, I promise.
  - kibwen 9y ago
    For more paranoid folks, it would be nice to have a configuration option to forego the git features and thereby remove the need for linking in any networking code. :)
    - steveklabnik 9y ago
      There is one already; it's a cargo feature.
      - Pewqazz 9y ago
        I wrote the original Homebrew formula for exa and remembered adding support for the Git-less install, so I was surprised to see it wasn't there anymore! Seems like it was removed in this version bump [1] — I'll open a PR adding it back in. [1]: https://github.com/Homebrew/homebrew-core/pull/13676 https://github.com/Homebrew/homebrew-core/pull/13676
deleted 9y ago
[deleted]

dvfjsdhgfv 9y ago

> The main problem I can think of is that I'm so used to type cd and then ls... But OTOH it's as simple to fix as alias ls=exa Are you really sure you want to replace ls with exa? I can think of a dozen reasons it could cause trouble.

assafmo 9y ago
It will definitely be easier to check it out this way.
cytzol 9y ago
I've been aliasing "l" and "ls" to "exa" for years now. Aliases in your shell won't cause any problems, because any scripts you run won't follow the aliases and will just use ls normally. Actually replacing the binary? That would cause so many problems!

deleted 9y ago

[deleted]

NuSkooler 9y ago

⋊> ~/Downloads unzip exa-linux-x86_64-0.7.0.zip Archive: exa-linux-x86_64-0.7.0.zip inflating: exa-linux-x86_64 ⋊> ~/Downloads ./exa-linux-x86_64 --version 15:26:40 ./exa-linux-x86_64: error while loading shared libraries: libhttp_parser.so.2.1: cannot open shared object file: No such file or directory ...yup.