This patch adds a Makefile that will build and install exa along with
its recently added manual page. This provides a little bit of a nicer
installation path while we wait for Cargo to, hopefully, provide its own
built-in installation method for packages that contain binaries.
Signed-off-by: David Celis <me@davidcel.is>
In cases where symlink targets were more than a single directory down,
exa did not print the '/' targets when separating directories, resulting
in the following output:
symlink => dirAdirBdirC/file
Instead of
symlink => dirA/dirB/dirC/file
By adding a '/' character after each component of the filename, this
error is fixed.
This patch adds a manual page that can be parsed and outputted by the
`man` command. The help command is useful, but many UNIX users have a
certain reflex to check for manual pages. It would be awesome to be able
to type `man exa` and see some output! Some notes:
* This manual page was hand crafted. I had hoped to find some Rust
utility that could generate manual pages to prevent having to change
this file whenever changes to options are made. There are tools to
write manual pages in a nicer syntax and then convert them into the
groff syntax, but I hesitated to add more tools to the build process.
This might make the file more difficult to maintain, but unless exa's
signature changes frequently, it should be okay.
* The manual page isn't automatically copied into the
/usr/local/share/man/man1 directory, where it would need to be for
`man` to read it. My first inkling to have installation be a nice
process would be to craft a Makefile that will run `cargo build
--release`, copy the binary into /usr/local/bin, and copy the man
page into the aforementioned directory. I can handle that in this PR
or another one if you like the idea of a Makefile to ease
installation!
Signed-off-by: David Celis <me@davidcel.is>
The old implementation blindly assumed that a symlink target would have a directory compoment, which the current directory, parent directory, and root directory technically don't have.
Fixes#20.
The logic of the previous version wasn't correct. Also, presuming
natural ordering of full filenames is still reasonable when the
extensions are identical.
The challenge is that the paths returned from libgit2's status listing
are from the perspective of the Git repository and thus effectively
relative to the working tree root, while the other paths we're
manipulating are (potentially) relative to our current working
directory. So, if those two aren't identical (if running from outside
the working tree, or from a subdirectory), the paths won't match up.
A reasonably reliable way around this is to resolve both types of paths
to absolute paths before comparing them. This fixes#15 at a basic
level, anyway.
What still doesn't work: referring to the working tree or one of its
descendants via a symlink. For that, we'd probably need to fully resolve
symlinks in the file path.
(The unwrap_or()'s are messy and will probably just result in missing
status information, but then, what information could you hope to get
without having both a current working directory and a Git working tree?)
