Llewellyn/exa
1
0
Fork 0
mirror of https://github.com/Llewellynvdm/exa.git synced 2024-11-14 16:34:06 +00:00
Code Issues Projects Releases Wiki Activity
513ec51358
exa/Cargo.lock

452 lines
20 KiB
Plaintext
Raw Normal View History

Upgrade to latest ansi_term Yeah, I broke my own code again.
2014-11-26 07:36:09 +00:00
[root]
name = "exa"
Version bump to 0.7.0
2017-07-07 10:47:47 +00:00
version = "0.7.0"
Upgrade to latest ansi_term Yeah, I broke my own code again.
2014-11-26 07:36:09 +00:00
dependencies = [
Update dependencies * Also remove bitflags as it isn't used. * Don't update ansi_term as ANSIString is no longer Clone.
2017-03-30 19:23:14 +00:00
"ansi_term 0.8.0 (registry+https://github.com/rust-lang/crates.io-index)",
Versions bump. Oh, and checksums!
2016-10-05 17:50:29 +00:00
"datetime 0.4.4 (registry+https://github.com/rust-lang/crates.io-index)",
Update rust-tz, amongst others
2015-09-02 22:23:23 +00:00
"getopts 0.2.14 (registry+https://github.com/rust-lang/crates.io-index)",
Update dependencies
2017-06-11 08:34:02 +00:00
"git2 0.6.6 (registry+https://github.com/rust-lang/crates.io-index)",
Basic glob ignoring See #97 and recently #130 too. This allows the user to pass in options such as "--ignore '*.pyc'" to not list any files ending in '.pyc' in the output. It uses the Rust glob crate and currently does a simple split on pipe, without any escaping, so it’s not really *complete*, but is at least something.
2016-10-30 14:43:33 +00:00
"glob 0.2.11 (registry+https://github.com/rust-lang/crates.io-index)",
Fix bug where colours were incorrectly applied exa assumed that the COLUMNS environment variable being present always meant that the output was to a terminal, so it should use colours. But because this variable can be overridden, colours were being incorrectly set! The ‘fix’ is to stop trying to be clever while only calculating the terminal width once, and instead just stick it in a lazy_static so it’s usable everywhere.
2017-06-25 13:51:44 +00:00
"lazy_static 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)",
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
"libc 0.2.29 (registry+https://github.com/rust-lang/crates.io-index)",
Update dependencies
2017-06-11 08:34:02 +00:00
"locale 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)",
Versions bump
2015-08-25 17:25:48 +00:00
"natord 1.0.9 (registry+https://github.com/rust-lang/crates.io-index)",
Fix bug where colours were incorrectly applied exa assumed that the COLUMNS environment variable being present always meant that the output was to a terminal, so it should use colours. But because this variable can be overridden, colours were being incorrectly set! The ‘fix’ is to stop trying to be clever while only calculating the terminal width once, and instead just stick it in a lazy_static so it’s usable everywhere.
2017-06-25 13:51:44 +00:00
"num_cpus 1.6.2 (registry+https://github.com/rust-lang/crates.io-index)",
Versions bump. Oh, and checksums!
2016-10-05 17:50:29 +00:00
"number_prefix 0.2.7 (registry+https://github.com/rust-lang/crates.io-index)",
Update Cargo dependencies
2016-03-13 15:12:33 +00:00
"scoped_threadpool 0.1.7 (registry+https://github.com/rust-lang/crates.io-index)",
Versions bump. Oh, and checksums!
2016-10-05 17:50:29 +00:00
"term_grid 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
Use term_size crate to fetch terminal size. Should be cross-platform, one step closer to Windows support.
2017-08-05 06:09:26 +00:00
"term_size 0.3.0 (registry+https://github.com/rust-lang/crates.io-index)",
The first versions bump in AGES
2017-03-26 16:03:24 +00:00
"unicode-width 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)",
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
"users 0.5.3 (registry+https://github.com/rust-lang/crates.io-index)",
Improve system time zone detection
2016-02-10 19:02:20 +00:00
"zoneinfo_compiled 0.2.1 (git+https://github.com/rust-datetime/zoneinfo-compiled.git)",
Versions bump
2015-08-25 17:25:48 +00:00
]
Upgrade to latest ansi_term Yeah, I broke my own code again.
2014-11-26 07:36:09 +00:00
[[package]]
name = "ansi_term"
Update dependencies * Also remove bitflags as it isn't used. * Don't update ansi_term as ANSIString is no longer Clone.
2017-03-30 19:23:14 +00:00
version = "0.8.0"
Display dates with the host's timezone Fixes #54 using the datetime crate's spiffy new time zone ability.
2015-06-04 14:15:39 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade to latest ansi_term Yeah, I broke my own code again.
2014-11-26 07:36:09 +00:00
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
[[package]]
name = "bitflags"
version = "0.7.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Preliminary Git support! This is something that I've long wanted to add. It uses libgit2 as an optional dependency.
2015-01-27 15:01:17 +00:00
[[package]]
name = "bitflags"
Update dependencies
2017-06-11 08:34:02 +00:00
version = "0.9.1"
Preliminary Git support! This is something that I've long wanted to add. It uses libgit2 as an optional dependency.
2015-01-27 15:01:17 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Improve system time zone detection
2016-02-10 19:02:20 +00:00
[[package]]
name = "byteorder"
version = "0.4.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
Versions bump
2015-08-25 17:25:48 +00:00
[[package]]
name = "cmake"
Update dependencies
2017-06-11 08:34:02 +00:00
version = "0.1.24"
Versions bump
2015-08-25 17:25:48 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
Fix bug where colours were incorrectly applied exa assumed that the COLUMNS environment variable being present always meant that the output was to a terminal, so it should use colours. But because this variable can be overridden, colours were being incorrectly set! The ‘fix’ is to stop trying to be clever while only calculating the terminal width once, and instead just stick it in a lazy_static so it’s usable everywhere.
2017-06-25 13:51:44 +00:00
"gcc 0.3.51 (registry+https://github.com/rust-lang/crates.io-index)",
Versions bump
2015-08-25 17:25:48 +00:00
]
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
[[package]]
name = "conv"
version = "0.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"custom_derive 0.1.7 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "custom_derive"
version = "0.1.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
Display dates with the host's timezone Fixes #54 using the datetime crate's spiffy new time zone ability.
2015-06-04 14:15:39 +00:00
[[package]]
name = "datetime"
Versions bump. Oh, and checksums!
2016-10-05 17:50:29 +00:00
version = "0.4.4"
Start using threadpool crate
2015-06-05 02:04:56 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Initial work on date/time columns for files Using the datetime crate, add an extra column to the --long view that prints out the modified, accessed, or created timestamp for each file. Also, let the user pick which one they want to see based on the --time command-line option.
2015-02-09 16:33:27 +00:00
dependencies = [
Update packages to latest versions - Users v0.5.1, which renames OSUsers to UsersCache - Locale v0.2, which returns to libc v0.1 - Datetime v0.4.2, which mimics the locale update, and puts timezone definitions in: - Zoneinfo-data, which is needed to obtain the current timezone
2016-02-10 15:22:43 +00:00
"iso8601 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
"libc 0.2.29 (registry+https://github.com/rust-lang/crates.io-index)",
Update dependencies
2017-06-11 08:34:02 +00:00
"locale 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)",
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
"num 0.1.40 (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)",
Initial work on date/time columns for files Using the datetime crate, add an extra column to the --long view that prints out the modified, accessed, or created timestamp for each file. Also, let the user pick which one they want to see based on the --time command-line option.
2015-02-09 16:33:27 +00:00
]
[[package]]
name = "gcc"
Fix bug where colours were incorrectly applied exa assumed that the COLUMNS environment variable being present always meant that the output was to a terminal, so it should use colours. But because this variable can be overridden, colours were being incorrectly set! The ‘fix’ is to stop trying to be clever while only calculating the terminal width once, and instead just stick it in a lazy_static so it’s usable everywhere.
2017-06-25 13:51:44 +00:00
version = "0.3.51"
Initial work on date/time columns for files Using the datetime crate, add an extra column to the --long view that prints out the modified, accessed, or created timestamp for each file. Also, let the user pick which one they want to see based on the --time command-line option.
2015-02-09 16:33:27 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade to Rust alpha - uint -> usize - getopts Cargo library - replace feature gates with unstable APIs
2015-01-12 00:31:24 +00:00
[[package]]
name = "getopts"
Update rust-tz, amongst others
2015-09-02 22:23:23 +00:00
version = "0.2.14"
Upgrade to Rust alpha - uint -> usize - getopts Cargo library - replace feature gates with unstable APIs
2015-01-12 00:31:24 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Preliminary Git support! This is something that I've long wanted to add. It uses libgit2 as an optional dependency.
2015-01-27 15:01:17 +00:00
[[package]]
name = "git2"
Update dependencies
2017-06-11 08:34:02 +00:00
version = "0.6.6"
Pin to git2-rs version 0.3 This should prove more stable than relying on a Git version.
2015-10-01 23:56:39 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Preliminary Git support! This is something that I've long wanted to add. It uses libgit2 as an optional dependency.
2015-01-27 15:01:17 +00:00
dependencies = [
Update dependencies
2017-06-11 08:34:02 +00:00
"bitflags 0.9.1 (registry+https://github.com/rust-lang/crates.io-index)",
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
"libc 0.2.29 (registry+https://github.com/rust-lang/crates.io-index)",
"libgit2-sys 0.6.13 (registry+https://github.com/rust-lang/crates.io-index)",
Fix bug where colours were incorrectly applied exa assumed that the COLUMNS environment variable being present always meant that the output was to a terminal, so it should use colours. But because this variable can be overridden, colours were being incorrectly set! The ‘fix’ is to stop trying to be clever while only calculating the terminal width once, and instead just stick it in a lazy_static so it’s usable everywhere.
2017-06-25 13:51:44 +00:00
"url 1.5.1 (registry+https://github.com/rust-lang/crates.io-index)",
Preliminary Git support! This is something that I've long wanted to add. It uses libgit2 as an optional dependency.
2015-01-27 15:01:17 +00:00
]
Basic glob ignoring See #97 and recently #130 too. This allows the user to pass in options such as "--ignore '*.pyc'" to not list any files ending in '.pyc' in the output. It uses the Rust glob crate and currently does a simple split on pipe, without any escaping, so it’s not really *complete*, but is at least something.
2016-10-30 14:43:33 +00:00
[[package]]
name = "glob"
version = "0.2.11"
source = "registry+https://github.com/rust-lang/crates.io-index"
Update packages to latest versions - Users v0.5.1, which renames OSUsers to UsersCache - Locale v0.2, which returns to libc v0.1 - Datetime v0.4.2, which mimics the locale update, and puts timezone definitions in: - Zoneinfo-data, which is needed to obtain the current timezone
2016-02-10 15:22:43 +00:00
[[package]]
Update dependencies * Also remove bitflags as it isn't used. * Don't update ansi_term as ANSIString is no longer Clone.
2017-03-30 19:23:14 +00:00
name = "idna"
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
version = "0.1.4"
Update packages to latest versions - Users v0.5.1, which renames OSUsers to UsersCache - Locale v0.2, which returns to libc v0.1 - Datetime v0.4.2, which mimics the locale update, and puts timezone definitions in: - Zoneinfo-data, which is needed to obtain the current timezone
2016-02-10 15:22:43 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
Update dependencies
2017-06-11 08:34:02 +00:00
"matches 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
"unicode-bidi 0.3.4 (registry+https://github.com/rust-lang/crates.io-index)",
Fix bug where colours were incorrectly applied exa assumed that the COLUMNS environment variable being present always meant that the output was to a terminal, so it should use colours. But because this variable can be overridden, colours were being incorrectly set! The ‘fix’ is to stop trying to be clever while only calculating the terminal width once, and instead just stick it in a lazy_static so it’s usable everywhere.
2017-06-25 13:51:44 +00:00
"unicode-normalization 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
Versions bump
2015-12-15 21:38:56 +00:00
]
The first versions bump in AGES
2017-03-26 16:03:24 +00:00
[[package]]
Update dependencies * Also remove bitflags as it isn't used. * Don't update ansi_term as ANSIString is no longer Clone.
2017-03-30 19:23:14 +00:00
name = "iso8601"
version = "0.1.1"
The first versions bump in AGES
2017-03-26 16:03:24 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
Update dependencies * Also remove bitflags as it isn't used. * Don't update ansi_term as ANSIString is no longer Clone.
2017-03-30 19:23:14 +00:00
"nom 1.2.4 (registry+https://github.com/rust-lang/crates.io-index)",
The first versions bump in AGES
2017-03-26 16:03:24 +00:00
]
Use term_size crate to fetch terminal size. Should be cross-platform, one step closer to Windows support.
2017-08-05 06:09:26 +00:00
[[package]]
name = "kernel32-sys"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"winapi 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi-build 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
]
Fix bug where colours were incorrectly applied exa assumed that the COLUMNS environment variable being present always meant that the output was to a terminal, so it should use colours. But because this variable can be overridden, colours were being incorrectly set! The ‘fix’ is to stop trying to be clever while only calculating the terminal width once, and instead just stick it in a lazy_static so it’s usable everywhere.
2017-06-25 13:51:44 +00:00
[[package]]
name = "lazy_static"
version = "0.2.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
Update to most recent versions of libraries
2015-02-04 01:34:21 +00:00
[[package]]
name = "libc"
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
version = "0.2.29"
Pin versions to those we know work
2015-11-04 17:01:05 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Preliminary Git support! This is something that I've long wanted to add. It uses libgit2 as an optional dependency.
2015-01-27 15:01:17 +00:00
[[package]]
name = "libgit2-sys"
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
version = "0.6.13"
Pin to git2-rs version 0.3 This should prove more stable than relying on a Git version.
2015-10-01 23:56:39 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Preliminary Git support! This is something that I've long wanted to add. It uses libgit2 as an optional dependency.
2015-01-27 15:01:17 +00:00
dependencies = [
Update dependencies
2017-06-11 08:34:02 +00:00
"cmake 0.1.24 (registry+https://github.com/rust-lang/crates.io-index)",
Fix bug where colours were incorrectly applied exa assumed that the COLUMNS environment variable being present always meant that the output was to a terminal, so it should use colours. But because this variable can be overridden, colours were being incorrectly set! The ‘fix’ is to stop trying to be clever while only calculating the terminal width once, and instead just stick it in a lazy_static so it’s usable everywhere.
2017-06-25 13:51:44 +00:00
"gcc 0.3.51 (registry+https://github.com/rust-lang/crates.io-index)",
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
"libc 0.2.29 (registry+https://github.com/rust-lang/crates.io-index)",
Fix bug where colours were incorrectly applied exa assumed that the COLUMNS environment variable being present always meant that the output was to a terminal, so it should use colours. But because this variable can be overridden, colours were being incorrectly set! The ‘fix’ is to stop trying to be clever while only calculating the terminal width once, and instead just stick it in a lazy_static so it’s usable everywhere.
2017-06-25 13:51:44 +00:00
"libz-sys 1.0.16 (registry+https://github.com/rust-lang/crates.io-index)",
The first versions bump in AGES
2017-03-26 16:03:24 +00:00
"pkg-config 0.3.9 (registry+https://github.com/rust-lang/crates.io-index)",
Preliminary Git support! This is something that I've long wanted to add. It uses libgit2 as an optional dependency.
2015-01-27 15:01:17 +00:00
]
[[package]]
name = "libz-sys"
Fix bug where colours were incorrectly applied exa assumed that the COLUMNS environment variable being present always meant that the output was to a terminal, so it should use colours. But because this variable can be overridden, colours were being incorrectly set! The ‘fix’ is to stop trying to be clever while only calculating the terminal width once, and instead just stick it in a lazy_static so it’s usable everywhere.
2017-06-25 13:51:44 +00:00
version = "1.0.16"
Preliminary Git support! This is something that I've long wanted to add. It uses libgit2 as an optional dependency.
2015-01-27 15:01:17 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
Fix bug where colours were incorrectly applied exa assumed that the COLUMNS environment variable being present always meant that the output was to a terminal, so it should use colours. But because this variable can be overridden, colours were being incorrectly set! The ‘fix’ is to stop trying to be clever while only calculating the terminal width once, and instead just stick it in a lazy_static so it’s usable everywhere.
2017-06-25 13:51:44 +00:00
"gcc 0.3.51 (registry+https://github.com/rust-lang/crates.io-index)",
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
"libc 0.2.29 (registry+https://github.com/rust-lang/crates.io-index)",
The first versions bump in AGES
2017-03-26 16:03:24 +00:00
"pkg-config 0.3.9 (registry+https://github.com/rust-lang/crates.io-index)",
Fix bug where colours were incorrectly applied exa assumed that the COLUMNS environment variable being present always meant that the output was to a terminal, so it should use colours. But because this variable can be overridden, colours were being incorrectly set! The ‘fix’ is to stop trying to be clever while only calculating the terminal width once, and instead just stick it in a lazy_static so it’s usable everywhere.
2017-06-25 13:51:44 +00:00
"vcpkg 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)",
Preliminary Git support! This is something that I've long wanted to add. It uses libgit2 as an optional dependency.
2015-01-27 15:01:17 +00:00
]
Format file size in bytes with the user's locale Use the `locale` crate as a dependency to read in the set thousands-separator character, and pass this to the file size column, which uses it to add the separators in. en_GB uses "," fr_FR uses "" and just displays the numbers in one go.
2015-02-10 16:08:10 +00:00
[[package]]
name = "locale"
Update dependencies
2017-06-11 08:34:02 +00:00
version = "0.2.2"
Format file size in bytes with the user's locale Use the `locale` crate as a dependency to read in the set thousands-separator character, and pass this to the file size column, which uses it to add the separators in. en_GB uses "," fr_FR uses "" and just displays the numbers in one go.
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 = [
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
"libc 0.2.29 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "magenta"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"conv 0.3.3 (registry+https://github.com/rust-lang/crates.io-index)",
"magenta-sys 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "magenta-sys"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"bitflags 0.7.0 (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
]
Format file size in bytes with the user's locale Use the `locale` crate as a dependency to read in the set thousands-separator character, and pass this to the file size column, which uses it to add the separators in. en_GB uses "," fr_FR uses "" and just displays the numbers in one go.
2015-02-10 16:08:10 +00:00
Preliminary Git support! This is something that I've long wanted to add. It uses libgit2 as an optional dependency.
2015-01-27 15:01:17 +00:00
[[package]]
name = "matches"
Update dependencies
2017-06-11 08:34:02 +00:00
version = "0.1.6"
Preliminary Git support! This is something that I've long wanted to add. It uses libgit2 as an optional dependency.
2015-01-27 15:01:17 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
The feature flags wheel keeps on turning...
2015-06-21 11:52:53 +00:00
[[package]]
Update packages to latest versions - Users v0.5.1, which renames OSUsers to UsersCache - Locale v0.2, which returns to libc v0.1 - Datetime v0.4.2, which mimics the locale update, and puts timezone definitions in: - Zoneinfo-data, which is needed to obtain the current timezone
2016-02-10 15:22:43 +00:00
name = "natord"
version = "1.0.9"
The feature flags wheel keeps on turning...
2015-06-21 11:52:53 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Use the natord library instead of our own sorter I'm serious, the more functionality I can use external crates for, the better.
2014-12-12 11:26:18 +00:00
[[package]]
Update packages to latest versions - Users v0.5.1, which renames OSUsers to UsersCache - Locale v0.2, which returns to libc v0.1 - Datetime v0.4.2, which mimics the locale update, and puts timezone definitions in: - Zoneinfo-data, which is needed to obtain the current timezone
2016-02-10 15:22:43 +00:00
name = "nom"
Versions bump. Oh, and checksums!
2016-10-05 17:50:29 +00:00
version = "1.2.4"
Switch to Crates dependencies format
2015-01-12 00:20:28 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Use the natord library instead of our own sorter I'm serious, the more functionality I can use external crates for, the better.
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"
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
version = "0.1.40"
Versions bump. Oh, and checksums!
2016-10-05 17:50:29 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
"num-bigint 0.1.40 (registry+https://github.com/rust-lang/crates.io-index)",
"num-complex 0.1.40 (registry+https://github.com/rust-lang/crates.io-index)",
"num-integer 0.1.35 (registry+https://github.com/rust-lang/crates.io-index)",
"num-iter 0.1.34 (registry+https://github.com/rust-lang/crates.io-index)",
"num-rational 0.1.39 (registry+https://github.com/rust-lang/crates.io-index)",
"num-traits 0.1.40 (registry+https://github.com/rust-lang/crates.io-index)",
Versions bump. Oh, and checksums!
2016-10-05 17:50:29 +00:00
]
[[package]]
name = "num-bigint"
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
version = "0.1.40"
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 = [
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
"num-integer 0.1.35 (registry+https://github.com/rust-lang/crates.io-index)",
"num-traits 0.1.40 (registry+https://github.com/rust-lang/crates.io-index)",
"rand 0.3.16 (registry+https://github.com/rust-lang/crates.io-index)",
Versions bump
2017-04-28 17:13:39 +00:00
"rustc-serialize 0.3.24 (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
]
Versions bump. Oh, and checksums!
2016-10-05 17:50:29 +00:00
[[package]]
name = "num-complex"
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
version = "0.1.40"
Versions bump. Oh, and checksums!
2016-10-05 17:50:29 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
"num-traits 0.1.40 (registry+https://github.com/rust-lang/crates.io-index)",
Versions bump
2017-04-28 17:13:39 +00:00
"rustc-serialize 0.3.24 (registry+https://github.com/rust-lang/crates.io-index)",
Versions bump. Oh, and checksums!
2016-10-05 17:50:29 +00:00
]
[[package]]
name = "num-integer"
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
version = "0.1.35"
Versions bump. Oh, and checksums!
2016-10-05 17:50:29 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
"num-traits 0.1.40 (registry+https://github.com/rust-lang/crates.io-index)",
Versions bump. Oh, and checksums!
2016-10-05 17:50:29 +00:00
]
[[package]]
name = "num-iter"
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
version = "0.1.34"
Versions bump. Oh, and checksums!
2016-10-05 17:50:29 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
"num-integer 0.1.35 (registry+https://github.com/rust-lang/crates.io-index)",
"num-traits 0.1.40 (registry+https://github.com/rust-lang/crates.io-index)",
Versions bump. Oh, and checksums!
2016-10-05 17:50:29 +00:00
]
[[package]]
name = "num-rational"
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
version = "0.1.39"
Versions bump. Oh, and checksums!
2016-10-05 17:50:29 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
"num-bigint 0.1.40 (registry+https://github.com/rust-lang/crates.io-index)",
"num-integer 0.1.35 (registry+https://github.com/rust-lang/crates.io-index)",
"num-traits 0.1.40 (registry+https://github.com/rust-lang/crates.io-index)",
Versions bump
2017-04-28 17:13:39 +00:00
"rustc-serialize 0.3.24 (registry+https://github.com/rust-lang/crates.io-index)",
Versions bump. Oh, and checksums!
2016-10-05 17:50:29 +00:00
]
[[package]]
name = "num-traits"
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
version = "0.1.40"
Versions bump. Oh, and checksums!
2016-10-05 17:50:29 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade to latest Rust Still missing a few Beta features, but it compiles! - Copy requires Clone - current_dir returns a Path now - num_cpus moved to a crate
2015-04-03 22:14:49 +00:00
[[package]]
name = "num_cpus"
Fix bug where colours were incorrectly applied exa assumed that the COLUMNS environment variable being present always meant that the output was to a terminal, so it should use colours. But because this variable can be overridden, colours were being incorrectly set! The ‘fix’ is to stop trying to be clever while only calculating the terminal width once, and instead just stick it in a lazy_static so it’s usable everywhere.
2017-06-25 13:51:44 +00:00
version = "1.6.2"
Upgrade to latest Rust Still missing a few Beta features, but it compiles! - Copy requires Clone - current_dir returns a Path now - num_cpus moved to a crate
2015-04-03 22:14:49 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
"libc 0.2.29 (registry+https://github.com/rust-lang/crates.io-index)",
Upgrade to latest Rust Still missing a few Beta features, but it compiles! - Copy requires Clone - current_dir returns a Path now - num_cpus moved to a crate
2015-04-03 22:14:49 +00:00
]
Use number_prefix crate for number prefixes
2014-12-18 07:00:31 +00:00
[[package]]
name = "number_prefix"
Versions bump. Oh, and checksums!
2016-10-05 17:50:29 +00:00
version = "0.2.7"
Switch to Crates dependencies format
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 = [
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
"num-traits 0.1.40 (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
]
Use number_prefix crate for number prefixes
2014-12-18 07:00:31 +00:00
Initial work on date/time columns for files Using the datetime crate, add an extra column to the --long view that prints out the modified, accessed, or created timestamp for each file. Also, let the user pick which one they want to see based on the --time command-line option.
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"
Initial work on date/time columns for files Using the datetime crate, add an extra column to the --long view that prints out the modified, accessed, or created timestamp for each file. Also, let the user pick which one they want to see based on the --time command-line option.
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 = [
The first versions bump in AGES
2017-03-26 16:03:24 +00:00
"unicode-width 0.1.4 (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
]
Initial work on date/time columns for files Using the datetime crate, add an extra column to the --long view that prints out the modified, accessed, or created timestamp for each file. Also, let the user pick which one they want to see based on the --time command-line option.
2015-02-09 16:33:27 +00:00
Fix bug where colours were incorrectly applied exa assumed that the COLUMNS environment variable being present always meant that the output was to a terminal, so it should use colours. But because this variable can be overridden, colours were being incorrectly set! The ‘fix’ is to stop trying to be clever while only calculating the terminal width once, and instead just stick it in a lazy_static so it’s usable everywhere.
2017-06-25 13:51:44 +00:00
[[package]]
name = "percent-encoding"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Preliminary Git support! This is something that I've long wanted to add. It uses libgit2 as an optional dependency.
2015-01-27 15:01:17 +00:00
[[package]]
name = "pkg-config"
The first versions bump in AGES
2017-03-26 16:03:24 +00:00
version = "0.3.9"
Initial work on date/time columns for files Using the datetime crate, add an extra column to the --long view that prints out the modified, accessed, or created timestamp for each file. Also, let the user pick which one they want to see based on the --time command-line option.
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
[[package]]
name = "rand"
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
version = "0.3.16"
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 = [
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
"libc 0.2.29 (registry+https://github.com/rust-lang/crates.io-index)",
"magenta 0.1.1 (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
]
Preliminary Git support! This is something that I've long wanted to add. It uses libgit2 as an optional dependency.
2015-01-27 15:01:17 +00:00
[[package]]
name = "rustc-serialize"
Versions bump
2017-04-28 17:13:39 +00:00
version = "0.3.24"
Preliminary Git support! This is something that I've long wanted to add. It uses libgit2 as an optional dependency.
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 = "scoped_threadpool"
Update Cargo dependencies
2016-03-13 15:12:33 +00:00
version = "0.1.7"
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"
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]]
Update dependencies * Also remove bitflags as it isn't used. * Don't update ansi_term as ANSIString is no longer Clone.
2017-03-30 19:23:14 +00:00
name = "term_grid"
version = "0.1.5"
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 = [
Update dependencies * Also remove bitflags as it isn't used. * Don't update ansi_term as ANSIString is no longer Clone.
2017-03-30 19:23:14 +00:00
"unicode-width 0.1.4 (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
]
Use term_size crate to fetch terminal size. Should be cross-platform, one step closer to Windows support.
2017-08-05 06:09:26 +00:00
[[package]]
name = "term_size"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"kernel32-sys 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.29 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)",
]
Use term_grid crate for grid formatting Fixes #39!
2015-06-23 09:54:57 +00:00
[[package]]
Update dependencies * Also remove bitflags as it isn't used. * Don't update ansi_term as ANSIString is no longer Clone.
2017-03-30 19:23:14 +00:00
name = "unicode-bidi"
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
version = "0.3.4"
Use term_grid crate for grid formatting Fixes #39!
2015-06-23 09:54:57 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
Update dependencies
2017-06-11 08:34:02 +00:00
"matches 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
Use term_grid crate for grid formatting Fixes #39!
2015-06-23 09:54:57 +00:00
]
Update dependencies * Also remove bitflags as it isn't used. * Don't update ansi_term as ANSIString is no longer Clone.
2017-03-30 19:23:14 +00:00
[[package]]
name = "unicode-normalization"
Fix bug where colours were incorrectly applied exa assumed that the COLUMNS environment variable being present always meant that the output was to a terminal, so it should use colours. But because this variable can be overridden, colours were being incorrectly set! The ‘fix’ is to stop trying to be clever while only calculating the terminal width once, and instead just stick it in a lazy_static so it’s usable everywhere.
2017-06-25 13:51:44 +00:00
version = "0.1.5"
Update dependencies * Also remove bitflags as it isn't used. * Don't update ansi_term as ANSIString is no longer Clone.
2017-03-30 19:23:14 +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
[[package]]
name = "unicode-width"
The first versions bump in AGES
2017-03-26 16:03:24 +00:00
version = "0.1.4"
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"
Preliminary Git support! This is something that I've long wanted to add. It uses libgit2 as an optional dependency.
2015-01-27 15:01:17 +00:00
[[package]]
name = "url"
Fix bug where colours were incorrectly applied exa assumed that the COLUMNS environment variable being present always meant that the output was to a terminal, so it should use colours. But because this variable can be overridden, colours were being incorrectly set! The ‘fix’ is to stop trying to be clever while only calculating the terminal width once, and instead just stick it in a lazy_static so it’s usable everywhere.
2017-06-25 13:51:44 +00:00
version = "1.5.1"
Preliminary Git support! This is something that I've long wanted to add. It uses libgit2 as an optional dependency.
2015-01-27 15:01:17 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
"idna 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)",
Update dependencies
2017-06-11 08:34:02 +00:00
"matches 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
Fix bug where colours were incorrectly applied exa assumed that the COLUMNS environment variable being present always meant that the output was to a terminal, so it should use colours. But because this variable can be overridden, colours were being incorrectly set! The ‘fix’ is to stop trying to be clever while only calculating the terminal width once, and instead just stick it in a lazy_static so it’s usable everywhere.
2017-06-25 13:51:44 +00:00
"percent-encoding 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)",
Preliminary Git support! This is something that I've long wanted to add. It uses libgit2 as an optional dependency.
2015-01-27 15:01:17 +00:00
]
Replare Unix module with users crate Feels good turning all that code into a dependency!
2014-12-12 11:17:55 +00:00
[[package]]
name = "users"
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
version = "0.5.3"
Switch to Crates dependencies format
2015-01-12 00:20:28 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update to most recent versions of libraries
2015-02-04 01:34:21 +00:00
dependencies = [
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
"libc 0.2.29 (registry+https://github.com/rust-lang/crates.io-index)",
Update to most recent versions of libraries
2015-02-04 01:34:21 +00:00
]
Replare Unix module with users crate Feels good turning all that code into a dependency!
2014-12-12 11:17:55 +00:00
Fix bug where colours were incorrectly applied exa assumed that the COLUMNS environment variable being present always meant that the output was to a terminal, so it should use colours. But because this variable can be overridden, colours were being incorrectly set! The ‘fix’ is to stop trying to be clever while only calculating the terminal width once, and instead just stick it in a lazy_static so it’s usable everywhere.
2017-06-25 13:51:44 +00:00
[[package]]
name = "vcpkg"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
Use term_size crate to fetch terminal size. Should be cross-platform, one step closer to Windows support.
2017-08-05 06:09:26 +00:00
[[package]]
name = "winapi"
version = "0.2.8"
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"
Improve system time zone detection
2016-02-10 19:02:20 +00:00
[[package]]
name = "zoneinfo_compiled"
version = "0.2.1"
Finally upgrade to a working zoneinfo_compiled Travis didn't like the old versions.
2016-02-10 21:33:25 +00:00
source = "git+https://github.com/rust-datetime/zoneinfo-compiled.git#f56921ea5e9f7cf065b1480ff270a1757c1f742f"
Improve system time zone detection
2016-02-10 19:02:20 +00:00
dependencies = [
"byteorder 0.4.2 (registry+https://github.com/rust-lang/crates.io-index)",
Versions bump. Oh, and checksums!
2016-10-05 17:50:29 +00:00
"datetime 0.4.4 (registry+https://github.com/rust-lang/crates.io-index)",
Improve system time zone detection
2016-02-10 19:02:20 +00:00
]
Versions bump. Oh, and checksums!
2016-10-05 17:50:29 +00:00
[metadata]
Update dependencies * Also remove bitflags as it isn't used. * Don't update ansi_term as ANSIString is no longer Clone.
2017-03-30 19:23:14 +00:00
"checksum ansi_term 0.8.0 (registry+https://github.com/rust-lang/crates.io-index)" = "c877397e09fec7a240af5fa74ad0124054b8066149d6544cd1ace93f8de3be68"
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
"checksum bitflags 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)" = "aad18937a628ec6abcd26d1489012cc0e18c21798210f491af69ded9b881106d"
Update dependencies
2017-06-11 08:34:02 +00:00
"checksum bitflags 0.9.1 (registry+https://github.com/rust-lang/crates.io-index)" = "4efd02e230a02e18f92fc2735f44597385ed02ad8f831e7c1c1156ee5e1ab3a5"
Versions bump. Oh, and checksums!
2016-10-05 17:50:29 +00:00
"checksum byteorder 0.4.2 (registry+https://github.com/rust-lang/crates.io-index)" = "96c8b41881888cc08af32d47ac4edd52bc7fa27fef774be47a92443756451304"
Update dependencies
2017-06-11 08:34:02 +00:00
"checksum cmake 0.1.24 (registry+https://github.com/rust-lang/crates.io-index)" = "b8ebbb35d3dc9cd09497168f33de1acb79b265d350ab0ac34133b98f8509af1f"
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
"checksum conv 0.3.3 (registry+https://github.com/rust-lang/crates.io-index)" = "78ff10625fd0ac447827aa30ea8b861fead473bb60aeb73af6c1c58caf0d1299"
"checksum custom_derive 0.1.7 (registry+https://github.com/rust-lang/crates.io-index)" = "ef8ae57c4978a2acd8b869ce6b9ca1dfe817bff704c220209fdef2c0b75a01b9"
Versions bump. Oh, and checksums!
2016-10-05 17:50:29 +00:00
"checksum datetime 0.4.4 (registry+https://github.com/rust-lang/crates.io-index)" = "2d425bf1f6bbd57cf833081c1e60ac294fd74e7edd66acc91c3fca2e496bcee9"
Fix bug where colours were incorrectly applied exa assumed that the COLUMNS environment variable being present always meant that the output was to a terminal, so it should use colours. But because this variable can be overridden, colours were being incorrectly set! The ‘fix’ is to stop trying to be clever while only calculating the terminal width once, and instead just stick it in a lazy_static so it’s usable everywhere.
2017-06-25 13:51:44 +00:00
"checksum gcc 0.3.51 (registry+https://github.com/rust-lang/crates.io-index)" = "120d07f202dcc3f72859422563522b66fe6463a4c513df062874daad05f85f0a"
Versions bump. Oh, and checksums!
2016-10-05 17:50:29 +00:00
"checksum getopts 0.2.14 (registry+https://github.com/rust-lang/crates.io-index)" = "d9047cfbd08a437050b363d35ef160452c5fe8ea5187ae0a624708c91581d685"
Update dependencies
2017-06-11 08:34:02 +00:00
"checksum git2 0.6.6 (registry+https://github.com/rust-lang/crates.io-index)" = "aa01936ac96555c083c0e8553f672616274408d9d3fc5b8696603fbf63ff43ee"
Basic glob ignoring See #97 and recently #130 too. This allows the user to pass in options such as "--ignore '*.pyc'" to not list any files ending in '.pyc' in the output. It uses the Rust glob crate and currently does a simple split on pipe, without any escaping, so it’s not really *complete*, but is at least something.
2016-10-30 14:43:33 +00:00
"checksum glob 0.2.11 (registry+https://github.com/rust-lang/crates.io-index)" = "8be18de09a56b60ed0edf84bc9df007e30040691af7acd1c41874faac5895bfb"
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
"checksum idna 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)" = "014b298351066f1512874135335d62a789ffe78a9974f94b43ed5621951eaf7d"
Versions bump. Oh, and checksums!
2016-10-05 17:50:29 +00:00
"checksum iso8601 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "11dc464f8c6f17595d191447c9c6559298b2d023d6f846a4a23ac7ea3c46c477"
Use term_size crate to fetch terminal size. Should be cross-platform, one step closer to Windows support.
2017-08-05 06:09:26 +00:00
"checksum kernel32-sys 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)" = "7507624b29483431c0ba2d82aece8ca6cdba9382bff4ddd0f7490560c056098d"
Fix bug where colours were incorrectly applied exa assumed that the COLUMNS environment variable being present always meant that the output was to a terminal, so it should use colours. But because this variable can be overridden, colours were being incorrectly set! The ‘fix’ is to stop trying to be clever while only calculating the terminal width once, and instead just stick it in a lazy_static so it’s usable everywhere.
2017-06-25 13:51:44 +00:00
"checksum lazy_static 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)" = "3b37545ab726dd833ec6420aaba8231c5b320814b9029ad585555d2a03e94fbf"
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
"checksum libc 0.2.29 (registry+https://github.com/rust-lang/crates.io-index)" = "8a014d9226c2cc402676fbe9ea2e15dd5222cd1dd57f576b5b283178c944a264"
"checksum libgit2-sys 0.6.13 (registry+https://github.com/rust-lang/crates.io-index)" = "0f1641ccb55181967a3e5ee4ae2911c0563492f016383ea67a27886181de088c"
Fix bug where colours were incorrectly applied exa assumed that the COLUMNS environment variable being present always meant that the output was to a terminal, so it should use colours. But because this variable can be overridden, colours were being incorrectly set! The ‘fix’ is to stop trying to be clever while only calculating the terminal width once, and instead just stick it in a lazy_static so it’s usable everywhere.
2017-06-25 13:51:44 +00:00
"checksum libz-sys 1.0.16 (registry+https://github.com/rust-lang/crates.io-index)" = "3fdd64ef8ee652185674455c1d450b83cbc8ad895625d543b5324d923f82e4d8"
Update dependencies
2017-06-11 08:34:02 +00:00
"checksum locale 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)" = "5fdbe492a9c0238da900a1165c42fc5067161ce292678a6fe80921f30fe307fd"
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
"checksum magenta 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "4bf0336886480e671965f794bc9b6fce88503563013d1bfb7a502c81fe3ac527"
"checksum magenta-sys 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "40d014c7011ac470ae28e2f76a02bfea4a8480f73e701353b49ad7a8d75f4699"
Update dependencies
2017-06-11 08:34:02 +00:00
"checksum matches 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)" = "100aabe6b8ff4e4a7e32c1c13523379802df0772b82466207ac25b013f193376"
Versions bump. Oh, and checksums!
2016-10-05 17:50:29 +00:00
"checksum natord 1.0.9 (registry+https://github.com/rust-lang/crates.io-index)" = "308d96db8debc727c3fd9744aac51751243420e46edf401010908da7f8d5e57c"
"checksum nom 1.2.4 (registry+https://github.com/rust-lang/crates.io-index)" = "a5b8c256fd9471521bcb84c3cdba98921497f1a331cbc15b8030fc63b82050ce"
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
"checksum num 0.1.40 (registry+https://github.com/rust-lang/crates.io-index)" = "a311b77ebdc5dd4cf6449d81e4135d9f0e3b153839ac90e648a8ef538f923525"
"checksum num-bigint 0.1.40 (registry+https://github.com/rust-lang/crates.io-index)" = "8fd0f8dbb4c0960998958a796281d88c16fbe68d87b1baa6f31e2979e81fd0bd"
"checksum num-complex 0.1.40 (registry+https://github.com/rust-lang/crates.io-index)" = "503e668405c5492d67cf662a81e05be40efe2e6bcf10f7794a07bd9865e704e6"
"checksum num-integer 0.1.35 (registry+https://github.com/rust-lang/crates.io-index)" = "d1452e8b06e448a07f0e6ebb0bb1d92b8890eea63288c0b627331d53514d0fba"
"checksum num-iter 0.1.34 (registry+https://github.com/rust-lang/crates.io-index)" = "7485fcc84f85b4ecd0ea527b14189281cf27d60e583ae65ebc9c088b13dffe01"
"checksum num-rational 0.1.39 (registry+https://github.com/rust-lang/crates.io-index)" = "288629c76fac4b33556f4b7ab57ba21ae202da65ba8b77466e6d598e31990790"
"checksum num-traits 0.1.40 (registry+https://github.com/rust-lang/crates.io-index)" = "99843c856d68d8b4313b03a17e33c4bb42ae8f6610ea81b28abe076ac721b9b0"
Fix bug where colours were incorrectly applied exa assumed that the COLUMNS environment variable being present always meant that the output was to a terminal, so it should use colours. But because this variable can be overridden, colours were being incorrectly set! The ‘fix’ is to stop trying to be clever while only calculating the terminal width once, and instead just stick it in a lazy_static so it’s usable everywhere.
2017-06-25 13:51:44 +00:00
"checksum num_cpus 1.6.2 (registry+https://github.com/rust-lang/crates.io-index)" = "aec53c34f2d0247c5ca5d32cca1478762f301740468ee9ee6dcb7a0dd7a0c584"
Versions bump. Oh, and checksums!
2016-10-05 17:50:29 +00:00
"checksum number_prefix 0.2.7 (registry+https://github.com/rust-lang/crates.io-index)" = "59a14be9c211cb9c602bad35ac99f41e9a84b44d71b8cbd3040e3bd02a214902"
"checksum pad 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)" = "d1bf3336e626b898e7263790d432a711d4277e22faea20dd9f70e0cab268fa58"
Fix bug where colours were incorrectly applied exa assumed that the COLUMNS environment variable being present always meant that the output was to a terminal, so it should use colours. But because this variable can be overridden, colours were being incorrectly set! The ‘fix’ is to stop trying to be clever while only calculating the terminal width once, and instead just stick it in a lazy_static so it’s usable everywhere.
2017-06-25 13:51:44 +00:00
"checksum percent-encoding 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)" = "de154f638187706bde41d9b4738748933d64e6b37bdbffc0b47a97d16a6ae356"
The first versions bump in AGES
2017-03-26 16:03:24 +00:00
"checksum pkg-config 0.3.9 (registry+https://github.com/rust-lang/crates.io-index)" = "3a8b4c6b8165cd1a1cd4b9b120978131389f64bdaf456435caa41e630edba903"
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
"checksum rand 0.3.16 (registry+https://github.com/rust-lang/crates.io-index)" = "eb250fd207a4729c976794d03db689c9be1d634ab5a1c9da9492a13d8fecbcdf"
Versions bump
2017-04-28 17:13:39 +00:00
"checksum rustc-serialize 0.3.24 (registry+https://github.com/rust-lang/crates.io-index)" = "dcf128d1287d2ea9d80910b5f1120d0b8eede3fbf1abe91c40d39ea7d51e6fda"
Versions bump. Oh, and checksums!
2016-10-05 17:50:29 +00:00
"checksum scoped_threadpool 0.1.7 (registry+https://github.com/rust-lang/crates.io-index)" = "3ef399c8893e8cb7aa9696e895427fab3a6bf265977bb96e126f24ddd2cda85a"
"checksum term_grid 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)" = "ccc202875496cf72a683a1ecd66f0742a830e73c202bdbd21867d73dfaac8343"
Use term_size crate to fetch terminal size. Should be cross-platform, one step closer to Windows support.
2017-08-05 06:09:26 +00:00
"checksum term_size 0.3.0 (registry+https://github.com/rust-lang/crates.io-index)" = "e2b6b55df3198cc93372e85dd2ed817f0e38ce8cc0f22eb32391bfad9c4bf209"
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
"checksum unicode-bidi 0.3.4 (registry+https://github.com/rust-lang/crates.io-index)" = "49f2bd0c6468a8230e1db229cff8029217cf623c767ea5d60bfbd42729ea54d5"
Fix bug where colours were incorrectly applied exa assumed that the COLUMNS environment variable being present always meant that the output was to a terminal, so it should use colours. But because this variable can be overridden, colours were being incorrectly set! The ‘fix’ is to stop trying to be clever while only calculating the terminal width once, and instead just stick it in a lazy_static so it’s usable everywhere.
2017-06-25 13:51:44 +00:00
"checksum unicode-normalization 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)" = "51ccda9ef9efa3f7ef5d91e8f9b83bbe6955f9bf86aec89d5cce2c874625920f"
The first versions bump in AGES
2017-03-26 16:03:24 +00:00
"checksum unicode-width 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)" = "bf3a113775714a22dcb774d8ea3655c53a32debae63a063acc00a91cc586245f"
Fix bug where colours were incorrectly applied exa assumed that the COLUMNS environment variable being present always meant that the output was to a terminal, so it should use colours. But because this variable can be overridden, colours were being incorrectly set! The ‘fix’ is to stop trying to be clever while only calculating the terminal width once, and instead just stick it in a lazy_static so it’s usable everywhere.
2017-06-25 13:51:44 +00:00
"checksum url 1.5.1 (registry+https://github.com/rust-lang/crates.io-index)" = "eeb819346883532a271eb626deb43c4a1bb4c4dd47c519bd78137c3e72a4fe27"
Versions bump Testing that a recent PR to rust-users (https://github.com/ogham/rust-users/issues/12) didn’t cause any regressions after updating to v0.5.3 of it.
2017-08-04 02:17:11 +00:00
"checksum users 0.5.3 (registry+https://github.com/rust-lang/crates.io-index)" = "e7d8fb16f17ce0e6a18a25ce39f08edb5fbe9a25f3f346c9dca5e6ffc0485cdf"
Fix bug where colours were incorrectly applied exa assumed that the COLUMNS environment variable being present always meant that the output was to a terminal, so it should use colours. But because this variable can be overridden, colours were being incorrectly set! The ‘fix’ is to stop trying to be clever while only calculating the terminal width once, and instead just stick it in a lazy_static so it’s usable everywhere.
2017-06-25 13:51:44 +00:00
"checksum vcpkg 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)" = "9e0a7d8bed3178a8fb112199d466eeca9ed09a14ba8ad67718179b4fd5487d0b"
Use term_size crate to fetch terminal size. Should be cross-platform, one step closer to Windows support.
2017-08-05 06:09:26 +00:00
"checksum winapi 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)" = "167dc9d6949a9b857f3451275e911c3f44255842c1f7a76f33c55103a909087a"
"checksum winapi-build 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "2d315eee3b34aca4797b2da6b13ed88266e6d612562a0c46390af8299fc699bc"
Versions bump. Oh, and checksums!
2016-10-05 17:50:29 +00:00
"checksum zoneinfo_compiled 0.2.1 (git+https://github.com/rust-datetime/zoneinfo-compiled.git)" = "<none>"
Reference in New Issue Copy Permalink