2014-11-26 07:36:09 +00:00
|
|
|
[root]
|
|
|
|
|
name = "exa"
|
2015-10-18 19:34:46 +00:00
|
|
|
version = "0.4.0"
|
2014-11-26 07:36:09 +00:00
|
|
|
dependencies = [
|
Replace Cells with growable TextCells
A recent change to ansi-term [1] means that `ANSIString`s can now hold either
owned *or* borrowed data (Rust calls this the Cow type). This means that we
can delay formatting ANSIStrings into ANSI-control-code-formatted strings
until it's absolutely necessary. The process for doing this was:
1. Replace the `Cell` type with a `TextCell` type that holds a vector of
`ANSIString` values instead of a formatted string. It still does the
width tracking.
2. Rework the details module's `render` functions to emit values of this
type.
3. Similarly, rework the functions that produce cells containing filenames
to use a `File` value's `name` field, which is an owned `String` that
can now be re-used.
4. Update the printing, formatting, and width-calculating code in the
details and grid-details views to produce a table by adding vectors
together instead of adding strings together, delaying the formatting as
long as it can.
This results in fewer allocations (as fewer `String` values are produced), and
makes the API tidier (as fewer `String` values are being passed around without
having their contents specified).
This also paves the way to Windows support, or at least support for
non-ANSI terminals: by delaying the time until strings are formatted,
it'll now be easier to change *how* they are formatted.
Casualties include:
- Bump to ansi_term v0.7.1, which impls `PartialEq` and `Debug` on
`ANSIString`.
- The grid_details and lines views now need to take a vector of files, rather
than a borrowed slice, so the filename cells produced now own the filename
strings that get taken from files.
- Fixed the signature of `File#link_target` to specify that the
file produced refers to the same directory, rather than some phantom
directory with the same lifetime as the file. (This was wrong from the
start, but it broke nothing until now)
References:
[1]: ansi-term@f6a6579ba8174de1cae64d181ec04af32ba2a4f0
2015-12-17 00:25:20 +00:00
|
|
|
"ansi_term 0.7.1 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-02-21 22:59:38 +00:00
|
|
|
"bitflags 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
|
2016-02-10 15:22:43 +00:00
|
|
|
"datetime 0.4.2 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-09-02 22:23:23 +00:00
|
|
|
"getopts 0.2.14 (registry+https://github.com/rust-lang/crates.io-index)",
|
2016-01-22 02:11:34 +00:00
|
|
|
"git2 0.3.4 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-11-15 19:26:58 +00:00
|
|
|
"lazy_static 0.1.15 (registry+https://github.com/rust-lang/crates.io-index)",
|
2016-02-10 15:22:43 +00:00
|
|
|
"libc 0.2.7 (registry+https://github.com/rust-lang/crates.io-index)",
|
|
|
|
|
"locale 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-08-25 17:25:48 +00:00
|
|
|
"natord 1.0.9 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-12-15 21:38:56 +00:00
|
|
|
"num_cpus 0.2.10 (registry+https://github.com/rust-lang/crates.io-index)",
|
|
|
|
|
"number_prefix 0.2.5 (registry+https://github.com/rust-lang/crates.io-index)",
|
Parallelise the details view!
This commit removes the threadpool in `main.rs` that stats each command-line argument separately, and replaces it with a *scoped* threadpool in `options/details.rs` that builds the table in parallel! Running this on my machine halves the execution time when tree-ing my entire home directory (which isn't exactly a common occurrence, but it's the only way to give exa a large running time)
The statting will be added back in parallel at a later stage. This was facilitated by the previous changes to recursion that made it easier to deal with.
There's a lot of large sweeping architectural changes. Here's a smattering of them:
- In `main.rs`, the files are now passed around as vectors of files rather than array slices of files. This is because `File`s aren't `Clone`, and the `Vec` is necessary to give away ownership of the files at the appropriate point.
- In the details view, files are now sorted *all* the time, rather than obeying the command-line order. As they're run in parallel, they have no guaranteed order anyway, so we *have* to sort them again. (I'm not sure if this should be the intended behaviour or not!) This means that the `Details` struct has to have the filter *all* the time, not only while recursing, so it's been moved out of the `recurse` field.
- We use `scoped_threadpool` over `threadpool`, a recent addition. It's only safely used on Nightly, which we're using anyway, so that's OK!
- Removed a bunch of out-of-date comments.
This also fixes #77, mainly by accident :)
2015-09-02 22:19:10 +00:00
|
|
|
"scoped_threadpool 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-12-15 21:38:56 +00:00
|
|
|
"term_grid 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-08-25 17:25:48 +00:00
|
|
|
"unicode-width 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)",
|
2016-02-10 15:22:43 +00:00
|
|
|
"users 0.5.1 (registry+https://github.com/rust-lang/crates.io-index)",
|
|
|
|
|
"zoneinfo_data 0.1.0 (git+https://github.com/rust-datetime/zoneinfo-data.git)",
|
2015-08-25 17:25:48 +00:00
|
|
|
]
|
|
|
|
|
|
|
|
|
|
[[package]]
|
|
|
|
|
name = "advapi32-sys"
|
|
|
|
|
version = "0.1.2"
|
|
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
dependencies = [
|
2015-11-15 19:26:58 +00:00
|
|
|
"winapi 0.2.5 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-08-25 17:25:48 +00:00
|
|
|
"winapi-build 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-06-21 11:52:53 +00:00
|
|
|
]
|
|
|
|
|
|
2014-11-26 07:36:09 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "ansi_term"
|
Replace Cells with growable TextCells
A recent change to ansi-term [1] means that `ANSIString`s can now hold either
owned *or* borrowed data (Rust calls this the Cow type). This means that we
can delay formatting ANSIStrings into ANSI-control-code-formatted strings
until it's absolutely necessary. The process for doing this was:
1. Replace the `Cell` type with a `TextCell` type that holds a vector of
`ANSIString` values instead of a formatted string. It still does the
width tracking.
2. Rework the details module's `render` functions to emit values of this
type.
3. Similarly, rework the functions that produce cells containing filenames
to use a `File` value's `name` field, which is an owned `String` that
can now be re-used.
4. Update the printing, formatting, and width-calculating code in the
details and grid-details views to produce a table by adding vectors
together instead of adding strings together, delaying the formatting as
long as it can.
This results in fewer allocations (as fewer `String` values are produced), and
makes the API tidier (as fewer `String` values are being passed around without
having their contents specified).
This also paves the way to Windows support, or at least support for
non-ANSI terminals: by delaying the time until strings are formatted,
it'll now be easier to change *how* they are formatted.
Casualties include:
- Bump to ansi_term v0.7.1, which impls `PartialEq` and `Debug` on
`ANSIString`.
- The grid_details and lines views now need to take a vector of files, rather
than a borrowed slice, so the filename cells produced now own the filename
strings that get taken from files.
- Fixed the signature of `File#link_target` to specify that the
file produced refers to the same directory, rather than some phantom
directory with the same lifetime as the file. (This was wrong from the
start, but it broke nothing until now)
References:
[1]: ansi-term@f6a6579ba8174de1cae64d181ec04af32ba2a4f0
2015-12-17 00:25:20 +00:00
|
|
|
version = "0.7.1"
|
2015-06-04 14:15:39 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2014-11-26 07:36:09 +00:00
|
|
|
|
2015-01-27 15:01:17 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "bitflags"
|
2015-02-09 19:40:49 +00:00
|
|
|
version = "0.1.1"
|
2015-01-27 15:01:17 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
|
2015-08-25 17:25:48 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "cmake"
|
2016-01-22 02:11:34 +00:00
|
|
|
version = "0.1.12"
|
2015-08-25 17:25:48 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
dependencies = [
|
2016-02-10 15:22:43 +00:00
|
|
|
"gcc 0.3.22 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-08-25 17:25:48 +00:00
|
|
|
]
|
|
|
|
|
|
2015-06-04 14:15:39 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "datetime"
|
2016-02-10 15:22:43 +00:00
|
|
|
version = "0.4.2"
|
2015-06-05 02:04:56 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2015-02-09 16:33:27 +00:00
|
|
|
dependencies = [
|
2016-02-10 15:22:43 +00:00
|
|
|
"iso8601 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
|
|
|
|
|
"libc 0.2.7 (registry+https://github.com/rust-lang/crates.io-index)",
|
|
|
|
|
"locale 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)",
|
2016-01-22 02:11:34 +00:00
|
|
|
"num 0.1.30 (registry+https://github.com/rust-lang/crates.io-index)",
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
"pad 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-02-09 16:33:27 +00:00
|
|
|
]
|
|
|
|
|
|
|
|
|
|
[[package]]
|
|
|
|
|
name = "gcc"
|
2016-02-10 15:22:43 +00:00
|
|
|
version = "0.3.22"
|
2015-02-09 16:33:27 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2015-08-25 17:25:48 +00:00
|
|
|
dependencies = [
|
|
|
|
|
"advapi32-sys 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-11-15 19:26:58 +00:00
|
|
|
"winapi 0.2.5 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-08-25 17:25:48 +00:00
|
|
|
]
|
2015-02-09 16:33:27 +00:00
|
|
|
|
2016-01-22 02:11:34 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "gdi32-sys"
|
|
|
|
|
version = "0.1.1"
|
|
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
dependencies = [
|
|
|
|
|
"winapi 0.2.5 (registry+https://github.com/rust-lang/crates.io-index)",
|
|
|
|
|
]
|
|
|
|
|
|
2015-01-12 00:31:24 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "getopts"
|
2015-09-02 22:23:23 +00:00
|
|
|
version = "0.2.14"
|
2015-01-12 00:31:24 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
|
2015-01-27 15:01:17 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "git2"
|
2016-01-22 02:11:34 +00:00
|
|
|
version = "0.3.4"
|
2015-10-01 23:56:39 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2015-01-27 15:01:17 +00:00
|
|
|
dependencies = [
|
2015-02-09 19:40:49 +00:00
|
|
|
"bitflags 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
|
2016-02-10 15:22:43 +00:00
|
|
|
"libc 0.2.7 (registry+https://github.com/rust-lang/crates.io-index)",
|
|
|
|
|
"libgit2-sys 0.3.10 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-11-18 18:32:40 +00:00
|
|
|
"url 0.2.38 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-01-27 15:01:17 +00:00
|
|
|
]
|
|
|
|
|
|
2016-02-10 15:22:43 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "iso8601"
|
|
|
|
|
version = "0.1.1"
|
|
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
dependencies = [
|
|
|
|
|
"nom 1.2.0 (registry+https://github.com/rust-lang/crates.io-index)",
|
|
|
|
|
]
|
|
|
|
|
|
2015-12-15 21:38:56 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "kernel32-sys"
|
|
|
|
|
version = "0.2.1"
|
|
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
dependencies = [
|
|
|
|
|
"winapi 0.2.5 (registry+https://github.com/rust-lang/crates.io-index)",
|
|
|
|
|
"winapi-build 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
|
|
|
|
|
]
|
|
|
|
|
|
2015-11-15 19:26:58 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "lazy_static"
|
|
|
|
|
version = "0.1.15"
|
|
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
|
2015-02-04 01:34:21 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "libc"
|
2015-10-30 10:40:56 +00:00
|
|
|
version = "0.1.12"
|
2015-02-04 01:34:21 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
|
2015-11-04 17:01:05 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "libc"
|
2016-02-10 15:22:43 +00:00
|
|
|
version = "0.2.7"
|
2015-11-04 17:01:05 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
|
2015-01-27 15:01:17 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "libgit2-sys"
|
2016-02-10 15:22:43 +00:00
|
|
|
version = "0.3.10"
|
2015-10-01 23:56:39 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2015-01-27 15:01:17 +00:00
|
|
|
dependencies = [
|
2016-01-22 02:11:34 +00:00
|
|
|
"cmake 0.1.12 (registry+https://github.com/rust-lang/crates.io-index)",
|
2016-02-10 15:22:43 +00:00
|
|
|
"libc 0.2.7 (registry+https://github.com/rust-lang/crates.io-index)",
|
|
|
|
|
"libssh2-sys 0.1.35 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-12-15 21:38:56 +00:00
|
|
|
"libz-sys 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)",
|
2016-02-10 15:22:43 +00:00
|
|
|
"openssl-sys 0.7.5 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-10-30 10:40:56 +00:00
|
|
|
"pkg-config 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-01-27 15:01:17 +00:00
|
|
|
]
|
|
|
|
|
|
|
|
|
|
[[package]]
|
|
|
|
|
name = "libressl-pnacl-sys"
|
2015-07-15 19:53:16 +00:00
|
|
|
version = "2.1.6"
|
2015-01-27 15:01:17 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
dependencies = [
|
2015-08-25 17:25:48 +00:00
|
|
|
"pnacl-build-helper 1.4.10 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-01-27 15:01:17 +00:00
|
|
|
]
|
|
|
|
|
|
|
|
|
|
[[package]]
|
|
|
|
|
name = "libssh2-sys"
|
2016-02-10 15:22:43 +00:00
|
|
|
version = "0.1.35"
|
2015-01-27 15:01:17 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
dependencies = [
|
2016-01-22 02:11:34 +00:00
|
|
|
"cmake 0.1.12 (registry+https://github.com/rust-lang/crates.io-index)",
|
2016-02-10 15:22:43 +00:00
|
|
|
"libc 0.2.7 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-12-15 21:38:56 +00:00
|
|
|
"libz-sys 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)",
|
2016-02-10 15:22:43 +00:00
|
|
|
"openssl-sys 0.7.5 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-10-30 10:40:56 +00:00
|
|
|
"pkg-config 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-11-18 18:32:40 +00:00
|
|
|
"winapi 0.2.5 (registry+https://github.com/rust-lang/crates.io-index)",
|
|
|
|
|
"ws2_32-sys 0.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-01-27 15:01:17 +00:00
|
|
|
]
|
|
|
|
|
|
|
|
|
|
[[package]]
|
|
|
|
|
name = "libz-sys"
|
2015-12-15 21:38:56 +00:00
|
|
|
version = "1.0.0"
|
2015-01-27 15:01:17 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
dependencies = [
|
2016-02-10 15:22:43 +00:00
|
|
|
"gcc 0.3.22 (registry+https://github.com/rust-lang/crates.io-index)",
|
|
|
|
|
"libc 0.2.7 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-10-30 10:40:56 +00:00
|
|
|
"pkg-config 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-01-27 15:01:17 +00:00
|
|
|
]
|
|
|
|
|
|
2015-02-10 16:08:10 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "locale"
|
2016-02-10 15:22:43 +00:00
|
|
|
version = "0.2.0"
|
2015-02-10 16:08:10 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
dependencies = [
|
2015-10-30 10:40:56 +00:00
|
|
|
"libc 0.1.12 (registry+https://github.com/rust-lang/crates.io-index)",
|
2016-01-22 02:11:34 +00:00
|
|
|
"num 0.1.30 (registry+https://github.com/rust-lang/crates.io-index)",
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
]
|
2015-02-10 16:08:10 +00:00
|
|
|
|
2015-01-27 15:01:17 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "matches"
|
|
|
|
|
version = "0.1.2"
|
|
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
|
2015-06-21 11:52:53 +00:00
|
|
|
[[package]]
|
2016-02-10 15:22:43 +00:00
|
|
|
name = "natord"
|
|
|
|
|
version = "1.0.9"
|
2015-06-21 11:52:53 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
|
2014-12-12 11:26:18 +00:00
|
|
|
[[package]]
|
2016-02-10 15:22:43 +00:00
|
|
|
name = "nom"
|
|
|
|
|
version = "1.2.0"
|
2015-01-12 00:20:28 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2014-12-12 11:26:18 +00:00
|
|
|
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "num"
|
2016-01-22 02:11:34 +00:00
|
|
|
version = "0.1.30"
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
dependencies = [
|
2016-01-22 02:11:34 +00:00
|
|
|
"rand 0.3.13 (registry+https://github.com/rust-lang/crates.io-index)",
|
2016-02-10 15:22:43 +00:00
|
|
|
"rustc-serialize 0.3.17 (registry+https://github.com/rust-lang/crates.io-index)",
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
]
|
|
|
|
|
|
2015-04-03 22:14:49 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "num_cpus"
|
2015-12-15 21:38:56 +00:00
|
|
|
version = "0.2.10"
|
2015-04-03 22:14:49 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
dependencies = [
|
2015-12-15 21:38:56 +00:00
|
|
|
"kernel32-sys 0.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
|
2016-02-10 15:22:43 +00:00
|
|
|
"libc 0.2.7 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-12-15 21:38:56 +00:00
|
|
|
"winapi 0.2.5 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-04-03 22:14:49 +00:00
|
|
|
]
|
|
|
|
|
|
2014-12-18 07:00:31 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "number_prefix"
|
2015-12-15 21:38:56 +00:00
|
|
|
version = "0.2.5"
|
2015-01-12 00:20:28 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
dependencies = [
|
2016-01-22 02:11:34 +00:00
|
|
|
"num 0.1.30 (registry+https://github.com/rust-lang/crates.io-index)",
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
]
|
2014-12-18 07:00:31 +00:00
|
|
|
|
2015-01-27 15:01:17 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "openssl-sys"
|
2016-02-10 15:22:43 +00:00
|
|
|
version = "0.7.5"
|
2015-01-27 15:01:17 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
dependencies = [
|
2016-01-22 02:11:34 +00:00
|
|
|
"gdi32-sys 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
|
2016-02-10 15:22:43 +00:00
|
|
|
"libc 0.2.7 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-07-15 19:53:16 +00:00
|
|
|
"libressl-pnacl-sys 2.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-10-30 10:40:56 +00:00
|
|
|
"pkg-config 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)",
|
2016-01-22 02:11:34 +00:00
|
|
|
"user32-sys 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-01-27 15:01:17 +00:00
|
|
|
]
|
|
|
|
|
|
2015-02-09 16:33:27 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "pad"
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
version = "0.1.4"
|
2015-02-09 16:33:27 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
dependencies = [
|
2015-08-25 17:25:48 +00:00
|
|
|
"unicode-width 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)",
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
]
|
2015-02-09 16:33:27 +00:00
|
|
|
|
2015-01-27 15:01:17 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "pkg-config"
|
2015-10-30 10:40:56 +00:00
|
|
|
version = "0.3.6"
|
2015-02-09 16:33:27 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
|
2015-01-27 15:01:17 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "pnacl-build-helper"
|
2015-08-25 17:25:48 +00:00
|
|
|
version = "1.4.10"
|
2015-01-27 15:01:17 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
dependencies = [
|
|
|
|
|
"tempdir 0.3.4 (registry+https://github.com/rust-lang/crates.io-index)",
|
|
|
|
|
]
|
|
|
|
|
|
|
|
|
|
[[package]]
|
|
|
|
|
name = "rand"
|
2016-01-22 02:11:34 +00:00
|
|
|
version = "0.3.13"
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
dependencies = [
|
2015-08-25 17:25:48 +00:00
|
|
|
"advapi32-sys 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
|
2016-02-10 15:22:43 +00:00
|
|
|
"libc 0.2.7 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-11-15 19:26:58 +00:00
|
|
|
"winapi 0.2.5 (registry+https://github.com/rust-lang/crates.io-index)",
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
]
|
2015-01-27 15:01:17 +00:00
|
|
|
|
|
|
|
|
[[package]]
|
|
|
|
|
name = "rustc-serialize"
|
2016-02-10 15:22:43 +00:00
|
|
|
version = "0.3.17"
|
2015-01-27 15:01:17 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
|
Parallelise the details view!
This commit removes the threadpool in `main.rs` that stats each command-line argument separately, and replaces it with a *scoped* threadpool in `options/details.rs` that builds the table in parallel! Running this on my machine halves the execution time when tree-ing my entire home directory (which isn't exactly a common occurrence, but it's the only way to give exa a large running time)
The statting will be added back in parallel at a later stage. This was facilitated by the previous changes to recursion that made it easier to deal with.
There's a lot of large sweeping architectural changes. Here's a smattering of them:
- In `main.rs`, the files are now passed around as vectors of files rather than array slices of files. This is because `File`s aren't `Clone`, and the `Vec` is necessary to give away ownership of the files at the appropriate point.
- In the details view, files are now sorted *all* the time, rather than obeying the command-line order. As they're run in parallel, they have no guaranteed order anyway, so we *have* to sort them again. (I'm not sure if this should be the intended behaviour or not!) This means that the `Details` struct has to have the filter *all* the time, not only while recursing, so it's been moved out of the `recurse` field.
- We use `scoped_threadpool` over `threadpool`, a recent addition. It's only safely used on Nightly, which we're using anyway, so that's OK!
- Removed a bunch of out-of-date comments.
This also fixes #77, mainly by accident :)
2015-09-02 22:19:10 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "rustc_version"
|
2016-02-10 15:22:43 +00:00
|
|
|
version = "0.1.6"
|
Parallelise the details view!
This commit removes the threadpool in `main.rs` that stats each command-line argument separately, and replaces it with a *scoped* threadpool in `options/details.rs` that builds the table in parallel! Running this on my machine halves the execution time when tree-ing my entire home directory (which isn't exactly a common occurrence, but it's the only way to give exa a large running time)
The statting will be added back in parallel at a later stage. This was facilitated by the previous changes to recursion that made it easier to deal with.
There's a lot of large sweeping architectural changes. Here's a smattering of them:
- In `main.rs`, the files are now passed around as vectors of files rather than array slices of files. This is because `File`s aren't `Clone`, and the `Vec` is necessary to give away ownership of the files at the appropriate point.
- In the details view, files are now sorted *all* the time, rather than obeying the command-line order. As they're run in parallel, they have no guaranteed order anyway, so we *have* to sort them again. (I'm not sure if this should be the intended behaviour or not!) This means that the `Details` struct has to have the filter *all* the time, not only while recursing, so it's been moved out of the `recurse` field.
- We use `scoped_threadpool` over `threadpool`, a recent addition. It's only safely used on Nightly, which we're using anyway, so that's OK!
- Removed a bunch of out-of-date comments.
This also fixes #77, mainly by accident :)
2015-09-02 22:19:10 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
dependencies = [
|
|
|
|
|
"semver 0.1.20 (registry+https://github.com/rust-lang/crates.io-index)",
|
|
|
|
|
]
|
|
|
|
|
|
|
|
|
|
[[package]]
|
|
|
|
|
name = "scoped_threadpool"
|
|
|
|
|
version = "0.1.6"
|
|
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
dependencies = [
|
2016-02-10 15:22:43 +00:00
|
|
|
"rustc_version 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
|
Parallelise the details view!
This commit removes the threadpool in `main.rs` that stats each command-line argument separately, and replaces it with a *scoped* threadpool in `options/details.rs` that builds the table in parallel! Running this on my machine halves the execution time when tree-ing my entire home directory (which isn't exactly a common occurrence, but it's the only way to give exa a large running time)
The statting will be added back in parallel at a later stage. This was facilitated by the previous changes to recursion that made it easier to deal with.
There's a lot of large sweeping architectural changes. Here's a smattering of them:
- In `main.rs`, the files are now passed around as vectors of files rather than array slices of files. This is because `File`s aren't `Clone`, and the `Vec` is necessary to give away ownership of the files at the appropriate point.
- In the details view, files are now sorted *all* the time, rather than obeying the command-line order. As they're run in parallel, they have no guaranteed order anyway, so we *have* to sort them again. (I'm not sure if this should be the intended behaviour or not!) This means that the `Details` struct has to have the filter *all* the time, not only while recursing, so it's been moved out of the `recurse` field.
- We use `scoped_threadpool` over `threadpool`, a recent addition. It's only safely used on Nightly, which we're using anyway, so that's OK!
- Removed a bunch of out-of-date comments.
This also fixes #77, mainly by accident :)
2015-09-02 22:19:10 +00:00
|
|
|
]
|
|
|
|
|
|
|
|
|
|
[[package]]
|
|
|
|
|
name = "semver"
|
|
|
|
|
version = "0.1.20"
|
|
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "tempdir"
|
|
|
|
|
version = "0.3.4"
|
|
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
dependencies = [
|
2016-01-22 02:11:34 +00:00
|
|
|
"rand 0.3.13 (registry+https://github.com/rust-lang/crates.io-index)",
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
]
|
|
|
|
|
|
2015-06-23 09:54:57 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "term_grid"
|
2015-12-15 21:38:56 +00:00
|
|
|
version = "0.1.3"
|
2015-06-23 09:54:57 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
dependencies = [
|
2015-08-25 17:25:48 +00:00
|
|
|
"unicode-width 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-06-23 09:54:57 +00:00
|
|
|
]
|
|
|
|
|
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "unicode-width"
|
2015-08-25 17:25:48 +00:00
|
|
|
version = "0.1.3"
|
Use new io + path + fs libraries (LOTS OF CHANGES)
Exa now uses the new IO, Path, and Filesystem libraries that have been out for a while now.
Unfortunately, the new libraries don't *entirely* cover the range of the old libraries just yet: in particular, to become more cross-platform, the data in `UnstableFileStat` isn't available in the Unix `MetadataExt` yet. Much of this is contained in rust-lang/rfcs#1044 (which is due to be implemented in rust-lang/rust#14711), but it's not *entirely* there yet.
As such, this commits a serious loss of functionality: no symlink viewing, no hard links or blocks, or users or groups. Also, some of the code could now be optimised. I just wanted to commit this to sort out most of the 'teething problems' of having a different path system in advance.
Here's an example problem that took ages to fix for you, just because you read this far: when I first got exa to compile, it worked mostly fine, except calling `exa` by itself didn't list the current directory. I traced where the command-line options were being generated, to where files and directories were sorted, to where the threads were spawned... and the problem turned out to be that it was using the full path as the file name, rather than just the last component, and these paths happened to begin with `.`, so it thought they were dotfiles.
2015-04-23 12:00:34 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
|
2015-01-27 15:01:17 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "url"
|
2015-11-18 18:32:40 +00:00
|
|
|
version = "0.2.38"
|
2015-01-27 15:01:17 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
dependencies = [
|
|
|
|
|
"matches 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
|
2016-02-10 15:22:43 +00:00
|
|
|
"rustc-serialize 0.3.17 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-11-18 18:32:40 +00:00
|
|
|
"uuid 0.1.18 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-01-27 15:01:17 +00:00
|
|
|
]
|
|
|
|
|
|
2016-01-22 02:11:34 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "user32-sys"
|
|
|
|
|
version = "0.1.2"
|
|
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
dependencies = [
|
|
|
|
|
"winapi 0.2.5 (registry+https://github.com/rust-lang/crates.io-index)",
|
|
|
|
|
"winapi-build 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
|
|
|
|
|
]
|
|
|
|
|
|
2014-12-12 11:17:55 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "users"
|
2016-02-10 15:22:43 +00:00
|
|
|
version = "0.5.1"
|
2015-01-12 00:20:28 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
2015-02-04 01:34:21 +00:00
|
|
|
dependencies = [
|
2016-02-10 15:22:43 +00:00
|
|
|
"libc 0.2.7 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-02-04 01:34:21 +00:00
|
|
|
]
|
2014-12-12 11:17:55 +00:00
|
|
|
|
2015-11-18 18:32:40 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "uuid"
|
|
|
|
|
version = "0.1.18"
|
|
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
dependencies = [
|
2016-01-22 02:11:34 +00:00
|
|
|
"rand 0.3.13 (registry+https://github.com/rust-lang/crates.io-index)",
|
2016-02-10 15:22:43 +00:00
|
|
|
"rustc-serialize 0.3.17 (registry+https://github.com/rust-lang/crates.io-index)",
|
2015-11-18 18:32:40 +00:00
|
|
|
]
|
|
|
|
|
|
2015-08-25 17:25:48 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "winapi"
|
2015-11-15 19:26:58 +00:00
|
|
|
version = "0.2.5"
|
2015-08-25 17:25:48 +00:00
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
|
|
|
|
|
[[package]]
|
|
|
|
|
name = "winapi-build"
|
|
|
|
|
version = "0.1.1"
|
|
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
|
2015-11-18 18:32:40 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "ws2_32-sys"
|
|
|
|
|
version = "0.2.1"
|
|
|
|
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
|
|
|
dependencies = [
|
|
|
|
|
"winapi 0.2.5 (registry+https://github.com/rust-lang/crates.io-index)",
|
|
|
|
|
"winapi-build 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
|
|
|
|
|
]
|
|
|
|
|
|
2016-02-10 15:22:43 +00:00
|
|
|
[[package]]
|
|
|
|
|
name = "zoneinfo_data"
|
|
|
|
|
version = "0.1.0"
|
|
|
|
|
source = "git+https://github.com/rust-datetime/zoneinfo-data.git#2ad3b0ea2a64676b529c79e9a381ce7fbf43aa94"
|
|
|
|
|
dependencies = [
|
|
|
|
|
"datetime 0.4.2 (registry+https://github.com/rust-lang/crates.io-index)",
|
|
|
|
|
"locale 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)",
|
|
|
|
|
]
|
|
|
|
|
|
