Mirrors/nushell
2
0
Fork 0
mirror of https://github.com/nushell/nushell synced 2024-12-26 13:03:07 +00:00
Code Issues Projects Releases Packages Wiki Activity
nushell/Cargo.lock

4692 lines
108 KiB
Text
Raw Normal View History

objectshell initial commit
2019-05-10 16:59:12 +00:00
# This file is automatically @generated by Cargo.
# It is not intended for manual editing.
Bat
2019-05-18 01:24:13 +00:00
[[package]]
name = "adler32"
Fix #811 (#813)
2019-10-13 04:53:58 +00:00
version = "1.0.4"
Bat
2019-05-18 01:24:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "5d2e7343e7fc9de883d1b0341e0b13970f764c14101234857d2ddafa1cb1cac2"
Bat
2019-05-18 01:24:13 +00:00
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "aho-corasick"
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
version = "0.7.8"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
checksum = "743ad5a418686aad3b87fd14c43badd828cf26e214a00f92a384291cf22e1811"
objectshell initial commit
2019-05-10 16:59:12 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"memchr",
objectshell initial commit
2019-05-10 16:59:12 +00:00
]
Simple parsing
2019-05-11 04:45:57 +00:00
[[package]]
name = "ansi_term"
version = "0.11.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "ee49baf6cb617b853aa8d93bf420db2383fab46d314482ca2803b40d5fde979b"
Simple parsing
2019-05-11 04:45:57 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"winapi 0.3.8",
Simple parsing
2019-05-11 04:45:57 +00:00
]
Bump deps and add serde_bytes support
2019-07-15 18:34:44 +00:00
[[package]]
name = "ansi_term"
Add basic 'did you mean' support
2019-09-13 03:44:21 +00:00
version = "0.12.1"
Bump deps and add serde_bytes support
2019-07-15 18:34:44 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "d52a9bb7ec0cf484c551830a7ce27bd20d67eac647e1befb56b0be4ee39a55d2"
Bump deps and add serde_bytes support
2019-07-15 18:34:44 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"winapi 0.3.8",
Bump deps and add serde_bytes support
2019-07-15 18:34:44 +00:00
]
Merge master
2019-11-16 17:17:05 +00:00
[[package]]
name = "anyhow"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
version = "1.0.26"
Merge master
2019-11-16 17:17:05 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
checksum = "7825f6833612eb2414095684fcf6c635becf3ce97fe48cf6421321e93bfbd53c"
Merge master
2019-11-16 17:17:05 +00:00
Improve signature infrastructure The `config` command uses different kinds of named arguments, which illustrates how it works.
2019-06-01 05:50:16 +00:00
[[package]]
name = "app_dirs"
version = "1.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "e73a24bad9bd6a94d6395382a6c69fe071708ae4409f763c5475e14ee896313d"
Improve signature infrastructure The `config` command uses different kinds of named arguments, which illustrates how it works.
2019-06-01 05:50:16 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"ole32-sys",
"shell32-sys",
"winapi 0.2.8",
"xdg",
Improve signature infrastructure The `config` command uses different kinds of named arguments, which illustrates how it works.
2019-06-01 05:50:16 +00:00
]
Upgrade crossterm (#1288) * WIP * Finish porting to new crossterm * Fmt
2020-01-27 02:51:46 +00:00
[[package]]
name = "arc-swap"
version = "0.4.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d7b8a9123b8027467bce0099fe556c628a53c8d83df0507084c31e9ba2e39aff"
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
Pin semver breaking dep
2019-08-08 17:33:19 +00:00
name = "arrayref"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.3.6"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "a4c527152e37cf757a3f78aae5a06fbeefdb07ccc535c980a3208ee3060dd544"
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "arrayvec"
Fix #811 (#813)
2019-10-13 04:53:58 +00:00
version = "0.4.12"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "cd9fd44efafa8690358b7408d253adf110036b88f55672a933f01d616ad9b1b9"
objectshell initial commit
2019-05-10 16:59:12 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"nodrop",
objectshell initial commit
2019-05-10 16:59:12 +00:00
]
Merge master
2019-11-16 17:17:05 +00:00
[[package]]
name = "arrayvec"
version = "0.5.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "cff77d8686867eceff3105329d4698d96c2391c176d5d03adc90c7389162b5b8"
Merge master
2019-11-16 17:17:05 +00:00
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
[[package]]
name = "async-attributes"
version = "1.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "efd3d156917d94862e779f356c5acae312b08fd3121e792c857d7928c8088423"
dependencies = [
"quote",
"syn",
]
[[package]]
name = "async-std"
version = "1.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0bf6039b315300e057d198b9d3ab92ee029e31c759b7f1afae538145e6f18a3e"
dependencies = [
"async-attributes",
"async-task",
"crossbeam-channel 0.4.0",
"crossbeam-deque",
"crossbeam-utils 0.7.0",
"futures-core",
"futures-io",
"futures-timer 2.0.2",
"kv-log-macro",
"log",
"memchr",
"mio",
"mio-uds",
"num_cpus",
"once_cell",
"pin-project-lite",
"pin-utils",
"slab",
]
Use async-stream crate to replace most async_stream_block invocations
2019-09-26 00:22:17 +00:00
[[package]]
name = "async-stream"
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
version = "0.2.1"
Use async-stream crate to replace most async_stream_block invocations
2019-09-26 00:22:17 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
checksum = "22068c0c19514942eefcfd4daf8976ef1aad84e61539f95cd200c35202f80af5"
Use async-stream crate to replace most async_stream_block invocations
2019-09-26 00:22:17 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"async-stream-impl",
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
"futures-core",
Use async-stream crate to replace most async_stream_block invocations
2019-09-26 00:22:17 +00:00
]
[[package]]
name = "async-stream-impl"
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
version = "0.2.1"
Use async-stream crate to replace most async_stream_block invocations
2019-09-26 00:22:17 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
checksum = "25f9db3b38af870bf7e5cc649167533b493928e50744e2c30ae350230b414670"
Use async-stream crate to replace most async_stream_block invocations
2019-09-26 00:22:17 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"proc-macro2",
"quote",
"syn",
Use async-stream crate to replace most async_stream_block invocations
2019-09-26 00:22:17 +00:00
]
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
[[package]]
name = "async-task"
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
version = "1.3.1"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
checksum = "0ac2c016b079e771204030951c366db398864f5026f84a44dafb0ff20f02085d"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
dependencies = [
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
"libc",
"winapi 0.3.8",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
]
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "atty"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.2.14"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "d9b39be18770d11421cdb1b9947a45dd3f37e93092cbf377614828a319d5fee8"
objectshell initial commit
2019-05-10 16:59:12 +00:00
dependencies = [
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
"hermit-abi",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"libc",
"winapi 0.3.8",
objectshell initial commit
2019-05-10 16:59:12 +00:00
]
[[package]]
name = "autocfg"
Merge master
2019-11-16 17:17:05 +00:00
version = "0.1.7"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "1d49d90015b3c36167a20fe2810c5cd875ad504b39cff3d4eae7977e6b7c1cb2"
objectshell initial commit
2019-05-10 16:59:12 +00:00
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
[[package]]
name = "autocfg"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f8aac770f1885fd7e387acedd76065302551364496e46b3dd00860b2f8359b9d"
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "backtrace"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.3.43"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "7f80256bc78f67e7df7e36d77366f636ed976895d91fe2ab9efa3973e8fe8c4f"
objectshell initial commit
2019-05-10 16:59:12 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"backtrace-sys",
"cfg-if",
"libc",
"rustc-demangle",
objectshell initial commit
2019-05-10 16:59:12 +00:00
]
[[package]]
name = "backtrace-sys"
Merge master
2019-11-16 17:17:05 +00:00
version = "0.1.32"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "5d6575f128516de27e3ce99689419835fce9643a9b215a14d2b5b685be018491"
objectshell initial commit
2019-05-10 16:59:12 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"cc",
"libc",
objectshell initial commit
2019-05-10 16:59:12 +00:00
]
Bat
2019-05-18 01:24:13 +00:00
[[package]]
name = "base64"
version = "0.10.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "0b25d992356d2eb0ed82172f5248873db5560c4721f564b13cb5193bda5e668e"
Bat
2019-05-18 01:24:13 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"byteorder",
Bat
2019-05-18 01:24:13 +00:00
]
Bump dep versions
2019-11-10 17:48:49 +00:00
[[package]]
name = "base64"
version = "0.11.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "b41b7ea54a0c9d92199de89e20e58d49f02f8e699814ef3fdf266f6f748d15c7"
Bump dep versions
2019-11-10 17:48:49 +00:00
add some battery stats
2019-08-11 03:01:09 +00:00
[[package]]
name = "battery"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
version = "0.7.5"
add some battery stats
2019-08-11 03:01:09 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "36a698e449024a5d18994a815998bf5e2e4bc1883e35a7d7ba95b6b69ee45907"
add some battery stats
2019-08-11 03:01:09 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"cfg-if",
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
"core-foundation 0.6.4",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"lazycell",
"libc",
"mach 0.2.3",
"nix 0.15.0",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"num-traits 0.2.11",
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
"uom",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"winapi 0.3.8",
add some battery stats
2019-08-11 03:01:09 +00:00
]
Migrated numerics to BigInt/BigDecimal This commit migrates Value's numeric types to BigInt and BigDecimal. The basic idea is that overflow errors aren't great in a shell environment, and not really necessary. The main immediate consequence is that new errors can occur when serializing Nu values to other formats. You can see this in changes to the various serialization formats (JSON, TOML, etc.). There's a new `CoerceInto` trait that uses the `ToPrimitive` trait from `num_traits` to attempt to coerce a `BigNum` or `BigDecimal` into a target type, and produces a `RangeError` (kind of `ShellError`) if the coercion fails. Another possible future consequence is that certain performance-critical numeric operations might be too slow. If that happens, we can introduce specialized numeric types to help improve the performance of those situations, based on the real-world experience.
2019-09-01 16:20:31 +00:00
[[package]]
name = "bigdecimal"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "460825c9e21708024d67c07057cd5560e5acdccac85de0de624a81d3de51bacb"
Migrated numerics to BigInt/BigDecimal This commit migrates Value's numeric types to BigInt and BigDecimal. The basic idea is that overflow errors aren't great in a shell environment, and not really necessary. The main immediate consequence is that new errors can occur when serializing Nu values to other formats. You can see this in changes to the various serialization formats (JSON, TOML, etc.). There's a new `CoerceInto` trait that uses the `ToPrimitive` trait from `num_traits` to attempt to coerce a `BigNum` or `BigDecimal` into a target type, and produces a `RangeError` (kind of `ShellError`) if the coercion fails. Another possible future consequence is that certain performance-critical numeric operations might be too slow. If that happens, we can introduce specialized numeric types to help improve the performance of those situations, based on the real-world experience.
2019-09-01 16:20:31 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"num-bigint",
"num-integer",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"num-traits 0.2.11",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"serde 1.0.104",
Migrated numerics to BigInt/BigDecimal This commit migrates Value's numeric types to BigInt and BigDecimal. The basic idea is that overflow errors aren't great in a shell environment, and not really necessary. The main immediate consequence is that new errors can occur when serializing Nu values to other formats. You can see this in changes to the various serialization formats (JSON, TOML, etc.). There's a new `CoerceInto` trait that uses the `ToPrimitive` trait from `num_traits` to attempt to coerce a `BigNum` or `BigDecimal` into a target type, and produces a `RangeError` (kind of `ShellError`) if the coercion fails. Another possible future consequence is that certain performance-critical numeric operations might be too slow. If that happens, we can introduce specialized numeric types to help improve the performance of those situations, based on the real-world experience.
2019-09-01 16:20:31 +00:00
]
Bat
2019-05-18 01:24:13 +00:00
[[package]]
name = "bincode"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
version = "1.2.1"
Bat
2019-05-18 01:24:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
checksum = "5753e2a71534719bf3f4e57006c3a4f0d2c672a4b676eec84161f763eca87dbf"
Bat
2019-05-18 01:24:13 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"byteorder",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"serde 1.0.104",
Bat
2019-05-18 01:24:13 +00:00
]
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "bitflags"
Merge master
2019-11-16 17:17:05 +00:00
version = "1.2.1"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "cf1de2fe8c75bc145a2f577add951f8134889b4795d47466a54a5c846d691693"
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
Pin semver breaking dep
2019-08-08 17:33:19 +00:00
name = "blake2b_simd"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.5.10"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "d8fb2d74254a3a0b5cac33ac9f8ed0e44aa50378d9dbb2e5d83bd21ed1dc2c8a"
objectshell initial commit
2019-05-10 16:59:12 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"arrayref",
"arrayvec 0.5.1",
"constant_time_eq",
objectshell initial commit
2019-05-10 16:59:12 +00:00
]
Add clipboard support
2019-06-07 16:30:50 +00:00
[[package]]
name = "block"
version = "0.1.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "0d8c1fef690941d3e7788d328517591fecc684c084084702d6ff1641e993699a"
Add clipboard support
2019-06-07 16:30:50 +00:00
Rebase on master
2019-08-25 13:57:47 +00:00
[[package]]
name = "bson"
Update bson to 0.14
2019-08-31 14:22:45 +00:00
version = "0.14.0"
Rebase on master
2019-08-25 13:57:47 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "d61895d21e2194d1ce1d434cff69025daac1e49a8b4698eb04b05722dbc08b33"
Rebase on master
2019-08-25 13:57:47 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"byteorder",
"chrono",
"decimal",
"hex 0.3.2",
"libc",
"linked-hash-map 0.5.2",
"md5",
"rand",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"serde 1.0.104",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"serde_json",
"time",
Rebase on master
2019-08-25 13:57:47 +00:00
]
Introduced ability to open csv documents.
2019-07-19 20:11:49 +00:00
[[package]]
name = "bstr"
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
version = "0.2.11"
Introduced ability to open csv documents.
2019-07-19 20:11:49 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
checksum = "502ae1441a0a5adb8fbd38a5955a6416b9493e92b465de5e4a9bde6a539c2c48"
Introduced ability to open csv documents.
2019-07-19 20:11:49 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"lazy_static 1.4.0",
"memchr",
"regex-automata",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"serde 1.0.104",
Introduced ability to open csv documents.
2019-07-19 20:11:49 +00:00
]
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
[[package]]
name = "bumpalo"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "3.1.2"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "5fb8038c1ddc0a5f73787b130f4cc75151e96ed33e417fde765eb5a81e3532f4"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
Internals cleanup and | select ...fields
2019-05-15 18:14:51 +00:00
[[package]]
name = "byte-unit"
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
version = "3.0.3"
Internals cleanup and | select ...fields
2019-05-15 18:14:51 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "6894a79550807490d9f19a138a6da0f8830e70c83e83402dd23f16fd6c479056"
Internals cleanup and | select ...fields
2019-05-15 18:14:51 +00:00
Start rebuilding lite parser using nom
2019-06-11 05:53:04 +00:00
[[package]]
name = "bytecount"
version = "0.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "f861d9ce359f56dbcb6e0c2a1cb84e52ad732cadb57b806adeb3c7668caccbd8"
Start rebuilding lite parser using nom
2019-06-11 05:53:04 +00:00
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "byteorder"
Merge master
2019-06-22 01:38:17 +00:00
version = "1.3.2"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "a7c3dd8985a7111efc5c80b44e23ecdd8c007de8ade3b96595387e812b957cf5"
objectshell initial commit
2019-05-10 16:59:12 +00:00
Pipe external to internal Each line is a string object
2019-05-24 18:48:33 +00:00
[[package]]
name = "bytes"
version = "0.4.12"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "206fdffcfa2df7cbe15601ef46c813fce0965eb3286db6b56c583b814b51c81c"
Pipe external to internal Each line is a string object
2019-05-24 18:48:33 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"byteorder",
"iovec",
Pipe external to internal Each line is a string object
2019-05-24 18:48:33 +00:00
]
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
[[package]]
name = "bytes"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.5.4"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "130aac562c0dd69c56b3b1cc8ffd2e17be31d0b6c25b61c96b76231aa23e39e1"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
[[package]]
name = "c2-chacha"
Merge master
2019-11-16 17:17:05 +00:00
version = "0.2.3"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "214238caa1bf3a496ec3392968969cab8549f96ff30652c9e56885329315f6bb"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"ppv-lite86",
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
]
Add from_xlsx for importing excel files
2019-11-17 03:18:41 +00:00
[[package]]
name = "calamine"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
version = "0.16.1"
Add from_xlsx for importing excel files
2019-11-17 03:18:41 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "abc39da027ec520445e6e526f105170b424ca68ea9e53553d3e6a29df41713ba"
Add from_xlsx for importing excel files
2019-11-17 03:18:41 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"byteorder",
"codepage",
"encoding_rs",
"log",
"quick-xml",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"serde 1.0.104",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"zip",
Add from_xlsx for importing excel files
2019-11-17 03:18:41 +00:00
]
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "cc"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "1.0.50"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "95e28fa049fda1c330bcf9d723be7663a899c4679724b34c81e9f5a326aab8cd"
Add basic 'did you mean' support
2019-09-13 03:44:21 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"jobserver",
Add basic 'did you mean' support
2019-09-13 03:44:21 +00:00
]
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "cfg-if"
Fix #811 (#813)
2019-10-13 04:53:58 +00:00
version = "0.1.10"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "4785bdd1c96b2a846b2bd7cc02e86b6b3dbf14e7e53446c4f54c92a361040822"
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "chrono"
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
version = "0.4.11"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
checksum = "80094f509cf8b5ae86a4966a39b3ff66cd7e2a3e594accec3743ff3fabeab5b2"
objectshell initial commit
2019-05-10 16:59:12 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"num-integer",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"num-traits 0.2.11",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"serde 1.0.104",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"time",
objectshell initial commit
2019-05-10 16:59:12 +00:00
]
Bat
2019-05-18 01:24:13 +00:00
[[package]]
name = "clap"
version = "2.33.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "5067f5bb2d80ef5d68b4c87db81601f0b75bca627bc2ef76b141d7b846a3c6d9"
Bat
2019-05-18 01:24:13 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"ansi_term 0.11.0",
"atty",
"bitflags",
"strsim",
"textwrap",
"unicode-width",
"vec_map",
Bat
2019-05-18 01:24:13 +00:00
]
Add clipboard support
2019-06-07 16:30:50 +00:00
[[package]]
name = "clipboard"
version = "0.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "25a904646c0340239dcf7c51677b33928bf24fdf424b79a57909c0109075b2e7"
Add clipboard support
2019-06-07 16:30:50 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"clipboard-win",
"objc",
"objc-foundation",
"objc_id",
"x11-clipboard",
Add clipboard support
2019-06-07 16:30:50 +00:00
]
[[package]]
name = "clipboard-win"
version = "2.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "e3a093d6fed558e5fe24c3dfc85a68bb68f1c824f440d3ba5aca189e2998786b"
Add clipboard support
2019-06-07 16:30:50 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"winapi 0.3.8",
Add clipboard support
2019-06-07 16:30:50 +00:00
]
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "cloudabi"
version = "0.0.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "ddfc5b9aa5d4507acaf872de71051dfd0e309860e88966e1051e462a077aac4f"
objectshell initial commit
2019-05-10 16:59:12 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"bitflags",
objectshell initial commit
2019-05-10 16:59:12 +00:00
]
Add from_xlsx for importing excel files
2019-11-17 03:18:41 +00:00
[[package]]
name = "codepage"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "8b0e9222c0cdf2c6ac27d73f664f9520266fa911c3106329d359f8861cb8bde9"
Add from_xlsx for importing excel files
2019-11-17 03:18:41 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"encoding_rs",
Add from_xlsx for importing excel files
2019-11-17 03:18:41 +00:00
]
Add tree sink
2019-06-07 07:50:26 +00:00
[[package]]
name = "config"
version = "0.9.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "f9107d78ed62b3fa5a86e7d18e647abed48cfd8f8fab6c72f4cdb982d196f7e6"
Add tree sink
2019-06-07 07:50:26 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"lazy_static 1.4.0",
"nom 4.2.3",
"rust-ini",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"serde 1.0.104",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"serde-hjson 0.8.2",
"serde_json",
"toml 0.4.10",
"yaml-rust",
Add tree sink
2019-06-07 07:50:26 +00:00
]
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "constant_time_eq"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.1.5"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "245097e9a4535ee1e3e3931fcfcd55a796a44c643e8596ff6566d68f09b87bbc"
objectshell initial commit
2019-05-10 16:59:12 +00:00
Add opening urls
2019-06-08 18:09:17 +00:00
[[package]]
name = "core-foundation"
version = "0.6.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "25b9e03f145fd4f2bf705e07b900cd41fc636598fe5dc452fd0db1441c3f496d"
Add opening urls
2019-06-08 18:09:17 +00:00
dependencies = [
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
"core-foundation-sys 0.6.2",
"libc",
]
[[package]]
name = "core-foundation"
version = "0.7.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "57d24c7a13c43e870e37c1556b74555437870a04514f7685f5b354e090567171"
dependencies = [
"core-foundation-sys 0.7.0",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"libc",
Add opening urls
2019-06-08 18:09:17 +00:00
]
[[package]]
name = "core-foundation-sys"
version = "0.6.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "e7ca8a5221364ef15ce201e8ed2f609fc312682a8f4e0e3d4aa5879764e0fa3b"
Add opening urls
2019-06-08 18:09:17 +00:00
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
[[package]]
name = "core-foundation-sys"
version = "0.7.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b3a71ab494c0b5b860bdc8407ae08978052417070c2ced38573a9157ad75b8ac"
Bat
2019-05-18 01:24:13 +00:00
[[package]]
name = "crc32fast"
version = "1.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "ba125de2af0df55319f41944744ad91c71113bf74a4646efff39afe1f6842db1"
Bat
2019-05-18 01:24:13 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"cfg-if",
Bat
2019-05-18 01:24:13 +00:00
]
Pin semver breaking dep
2019-08-08 17:33:19 +00:00
[[package]]
name = "crossbeam-channel"
version = "0.3.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "c8ec7fcd21571dc78f96cc96243cab8d8f035247c3efd16c687be154c3fa9efa"
Pin semver breaking dep
2019-08-08 17:33:19 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"crossbeam-utils 0.6.6",
Restructure and make commands uniform
2019-05-22 07:12:03 +00:00
]
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
[[package]]
name = "crossbeam-channel"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "acec9a3b0b3559f15aee4f90746c4e5e293b701c0f7d3925d24e01645267b68c"
dependencies = [
"crossbeam-utils 0.7.0",
]
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
[[package]]
name = "crossbeam-deque"
Merge master
2019-11-16 17:17:05 +00:00
version = "0.7.2"
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "c3aa945d63861bfe624b55d153a39684da1e8c0bc8fba932f7ee3a3c16cea3ca"
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"crossbeam-epoch",
"crossbeam-utils 0.7.0",
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
]
[[package]]
name = "crossbeam-epoch"
Merge master
2019-11-16 17:17:05 +00:00
version = "0.8.0"
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "5064ebdbf05ce3cb95e45c8b086f72263f4166b29b97f6baff7ef7fe047b55ac"
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
dependencies = [
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"autocfg 0.1.7",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"cfg-if",
"crossbeam-utils 0.7.0",
"lazy_static 1.4.0",
"memoffset",
"scopeguard",
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
]
[[package]]
name = "crossbeam-queue"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
version = "0.2.1"
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
checksum = "c695eeca1e7173472a32221542ae469b3e9aac3a4fc81f7696bcad82029493db"
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
dependencies = [
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"cfg-if",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"crossbeam-utils 0.7.0",
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
]
Restructure and make commands uniform
2019-05-22 07:12:03 +00:00
[[package]]
name = "crossbeam-utils"
bump deps
2019-07-29 07:46:24 +00:00
version = "0.6.6"
Restructure and make commands uniform
2019-05-22 07:12:03 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "04973fa96e96579258a5091af6003abde64af786b860f18622b82e026cca60e6"
Restructure and make commands uniform
2019-05-22 07:12:03 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"cfg-if",
"lazy_static 1.4.0",
Restructure and make commands uniform
2019-05-22 07:12:03 +00:00
]
Merge master
2019-11-16 17:17:05 +00:00
[[package]]
name = "crossbeam-utils"
version = "0.7.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "ce446db02cdc3165b94ae73111e570793400d0794e46125cc4056c81cbb039f4"
Merge master
2019-11-16 17:17:05 +00:00
dependencies = [
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"autocfg 0.1.7",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"cfg-if",
"lazy_static 1.4.0",
Restructure and make commands uniform
2019-05-22 07:12:03 +00:00
]
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
[[package]]
name = "crossterm"
Upgrade crossterm (#1288) * WIP * Finish porting to new crossterm * Fmt
2020-01-27 02:51:46 +00:00
version = "0.14.2"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade crossterm (#1288) * WIP * Finish porting to new crossterm * Fmt
2020-01-27 02:51:46 +00:00
checksum = "5750773d74a7dc612eac2ded3f55e9cdeeaa072210cd17c0192aedb48adb3618"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
dependencies = [
Upgrade crossterm (#1288) * WIP * Finish porting to new crossterm * Fmt
2020-01-27 02:51:46 +00:00
"bitflags",
Switch stdin redirect to manual. Add test (#1367)
2020-02-10 06:55:07 +00:00
"crossterm_winapi 0.5.1",
"lazy_static 1.4.0",
"libc",
"mio",
"parking_lot",
"signal-hook",
"winapi 0.3.8",
]
[[package]]
name = "crossterm"
version = "0.16.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b8a3223215bc00c666d6be730e88aef245ad4a4f837e87a16c347e8acf701643"
dependencies = [
"bitflags",
"crossterm_winapi 0.6.1",
Upgrade crossterm (#1288) * WIP * Finish porting to new crossterm * Fmt
2020-01-27 02:51:46 +00:00
"lazy_static 1.4.0",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"libc",
Upgrade crossterm (#1288) * WIP * Finish porting to new crossterm * Fmt
2020-01-27 02:51:46 +00:00
"mio",
"parking_lot",
"signal-hook",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"winapi 0.3.8",
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
]
[[package]]
name = "crossterm_winapi"
Upgrade crossterm (#1288) * WIP * Finish porting to new crossterm * Fmt
2020-01-27 02:51:46 +00:00
version = "0.5.1"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade crossterm (#1288) * WIP * Finish porting to new crossterm * Fmt
2020-01-27 02:51:46 +00:00
checksum = "8777c700901e2d5b50c406f736ed6b8f9e43645c7e104ddb74f8bc42b8ae62f6"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"winapi 0.3.8",
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
]
Switch stdin redirect to manual. Add test (#1367)
2020-02-10 06:55:07 +00:00
[[package]]
name = "crossterm_winapi"
version = "0.6.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "057b7146d02fb50175fd7dbe5158f6097f33d02831f43b4ee8ae4ddf67b68f5c"
dependencies = [
"winapi 0.3.8",
]
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "csv"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "1.1.3"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "00affe7f6ab566df61b4be3ce8cf16bc2576bca0963ceb0955e45d514bf9a279"
objectshell initial commit
2019-05-10 16:59:12 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"bstr",
"csv-core",
"itoa",
"ryu",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"serde 1.0.104",
objectshell initial commit
2019-05-10 16:59:12 +00:00
]
[[package]]
name = "csv-core"
Introduced ability to open csv documents.
2019-07-19 20:11:49 +00:00
version = "0.1.6"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "9b5cadb6b25c77aeff80ba701712494213f4a8418fcda2ee11b6560c3ad0bf4c"
objectshell initial commit
2019-05-10 16:59:12 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"memchr",
objectshell initial commit
2019-05-10 16:59:12 +00:00
]
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
[[package]]
name = "ct-logs"
version = "0.6.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4d3686f5fa27dbc1d76c751300376e167c5a43387f44bb451fd1c24776e49113"
dependencies = [
"sct",
]
Custom lexer
2019-05-29 15:26:45 +00:00
[[package]]
name = "ctor"
Fix #811 (#813)
2019-10-13 04:53:58 +00:00
version = "0.1.12"
Custom lexer
2019-05-29 15:26:45 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "cd8ce37ad4184ab2ce004c33bf6379185d3b1c95801cab51026bd271bf68eedc"
Custom lexer
2019-05-29 15:26:45 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"quote",
"syn",
Custom lexer
2019-05-29 15:26:45 +00:00
]
Handle Ctrl-C gracefully
2019-06-07 00:31:22 +00:00
[[package]]
name = "ctrlc"
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
version = "3.1.4"
Handle Ctrl-C gracefully
2019-06-07 00:31:22 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
checksum = "7a4ba686dff9fa4c1c9636ce1010b0cf98ceb421361b0bb3d6faeec43bd217a7"
Handle Ctrl-C gracefully
2019-06-07 00:31:22 +00:00
dependencies = [
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
"nix 0.17.0",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"winapi 0.3.8",
Handle Ctrl-C gracefully
2019-06-07 00:31:22 +00:00
]
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
[[package]]
name = "curl"
Fix #811 (#813)
2019-10-13 04:53:58 +00:00
version = "0.4.25"
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "06aa71e9208a54def20792d877bc663d6aae0732b9852e612c4a933177c31283"
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"curl-sys",
"libc",
"openssl-probe",
"openssl-sys",
"schannel",
"socket2",
"winapi 0.3.8",
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
]
[[package]]
name = "curl-sys"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.4.25"
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "0c38ca47d60b86d0cc9d42caa90a0885669c2abc9791f871c81f58cdf39e979b"
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"cc",
"libc",
"libnghttp2-sys",
"libz-sys",
"openssl-sys",
"pkg-config",
"vcpkg",
"winapi 0.3.8",
Update to heim v0.0.7.
2019-08-28 15:53:59 +00:00
]
[[package]]
name = "darwin-libproc"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "ade5a88af8d9646bf770687321a9488a0f2b4610aa08b0373016cd1af37f0a31"
Update to heim v0.0.7.
2019-08-28 15:53:59 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"darwin-libproc-sys",
"libc",
"memchr",
Update to heim v0.0.7.
2019-08-28 15:53:59 +00:00
]
[[package]]
name = "darwin-libproc-sys"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "c30d1a078d74da1183b02fed8a8b07afc412d3998334b53b750d0ed03b031541"
Update to heim v0.0.7.
2019-08-28 15:53:59 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"libc",
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
]
Update bson to 0.14
2019-08-31 14:22:45 +00:00
[[package]]
name = "decimal"
version = "2.0.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "e6458723bc760383275fbc02f4c769b2e5f3de782abaf5e7e0b9b7f0368a63ed"
Update bson to 0.14
2019-08-31 14:22:45 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"bitflags",
"cc",
"libc",
"ord_subset",
"rustc-serialize",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"serde 1.0.104",
Update bson to 0.14
2019-08-31 14:22:45 +00:00
]
Add some logic for more binary formats
2019-07-05 07:53:09 +00:00
[[package]]
name = "deflate"
version = "0.7.20"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "707b6a7b384888a70c8d2e8650b3e60170dfc6a67bb4aa67b6dfca57af4bedb4"
Add some logic for more binary formats
2019-07-05 07:53:09 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"adler32",
"byteorder",
Add some logic for more binary formats
2019-07-05 07:53:09 +00:00
]
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "derive-new"
Random fixes
2019-08-31 21:19:59 +00:00
version = "0.5.8"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "71f31892cd5c62e414316f2963c5689242c43d8e7bbcaaeca97e5e28c95d91d9"
objectshell initial commit
2019-05-10 16:59:12 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"proc-macro2",
"quote",
"syn",
objectshell initial commit
2019-05-10 16:59:12 +00:00
]
Custom lexer
2019-05-29 15:26:45 +00:00
[[package]]
name = "difference"
version = "2.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "524cbf6897b527295dff137cec09ecf3a05f4fddffd7dfcd1585403449e74198"
Custom lexer
2019-05-29 15:26:45 +00:00
Bat
2019-05-18 01:24:13 +00:00
[[package]]
name = "directories"
version = "1.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "72d337a64190607d4fcca2cb78982c5dd57f4916e19696b48a575fa746b6cb0f"
Bat
2019-05-18 01:24:13 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"libc",
"winapi 0.3.8",
Bat
2019-05-18 01:24:13 +00:00
]
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "dirs"
version = "1.0.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "3fd78930633bd1c6e35c4b42b1df7b0cbc6bc191146e512bb3bedf243fcc3901"
objectshell initial commit
2019-05-10 16:59:12 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"libc",
"redox_users",
"winapi 0.3.8",
objectshell initial commit
2019-05-10 16:59:12 +00:00
]
Lots of misc improvements
2019-06-03 07:41:28 +00:00
[[package]]
name = "dirs"
bump deps
2019-07-29 07:46:24 +00:00
version = "2.0.2"
Lots of misc improvements
2019-06-03 07:41:28 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "13aea89a5c93364a98e9b37b2fa237effbb694d5cfe01c5b70941f7eb087d5e3"
Lots of misc improvements
2019-06-03 07:41:28 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"cfg-if",
"dirs-sys",
Lots of misc improvements
2019-06-03 07:41:28 +00:00
]
[[package]]
name = "dirs-sys"
bump deps
2019-07-29 07:46:24 +00:00
version = "0.3.4"
Lots of misc improvements
2019-06-03 07:41:28 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "afa0b23de8fd801745c471deffa6e12d248f962c9fd4b4c33787b055599bde7b"
Lots of misc improvements
2019-06-03 07:41:28 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"cfg-if",
"libc",
"redox_users",
"winapi 0.3.8",
Lots of misc improvements
2019-06-03 07:41:28 +00:00
]
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
[[package]]
name = "doc-comment"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "923dea538cea0aa3025e8685b20d6ee21ef99c4f77e954a30febbaac5ec73a97"
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
Lots of misc improvements
2019-06-03 07:41:28 +00:00
[[package]]
name = "dtoa"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.4.5"
Lots of misc improvements
2019-06-03 07:41:28 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "4358a9e11b9a09cf52383b451b49a169e8d797b68aa02301ff586d70d9661ea3"
Lots of misc improvements
2019-06-03 07:41:28 +00:00
A bit more infra
2019-05-11 07:00:33 +00:00
[[package]]
name = "dunce"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "d0ad6bf6a88548d1126045c413548df1453d9be094a8ab9fd59bf1fdd338da4f"
A bit more infra
2019-05-11 07:00:33 +00:00
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "either"
Fix #811 (#813)
2019-10-13 04:53:58 +00:00
version = "1.5.3"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "bb1f6b1ce1c140482ea30ddd3335fc0024ac7ee112895426e0a629a6c20adfe3"
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "encode_unicode"
Fix #811 (#813)
2019-10-13 04:53:58 +00:00
version = "0.3.6"
Add a bunch more tokens and delimited ()
2019-06-12 17:44:45 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "a357d28ed41a50f9c765dbfe56cbc04a64e53e5fc58ba79fbc34c10ef3df831f"
Add a bunch more tokens and delimited ()
2019-06-12 17:44:45 +00:00
Add from_xlsx for importing excel files
2019-11-17 03:18:41 +00:00
[[package]]
name = "encoding_rs"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
version = "0.8.22"
Add from_xlsx for importing excel files
2019-11-17 03:18:41 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
checksum = "cd8d03faa7fe0c1431609dfad7bbe827af30f82e1e2ae6f7ee4fca6bd764bc28"
Add from_xlsx for importing excel files
2019-11-17 03:18:41 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"cfg-if",
Add from_xlsx for importing excel files
2019-11-17 03:18:41 +00:00
]
Add Range and start Signature support This commit contains two improvements: - Support for a Range syntax (and a corresponding Range value) - Work towards a signature syntax Implementing the Range syntax resulted in cleaning up how operators in the core syntax works. There are now two kinds of infix operators - tight operators (`.` and `..`) - loose operators Tight operators may not be interspersed (`$it.left..$it.right` is a syntax error). Loose operators require whitespace on both sides of the operator, and can be arbitrarily interspersed. Precedence is left to right in the core syntax. Note that delimited syntax (like `( ... )` or `[ ... ]`) is a single token node in the core syntax. A single token node can be parsed from beginning to end in a context-free manner. The rule for `.` is `<token node>.<member>`. The rule for `..` is `<token node>..<token node>`. Loose operators all have the same syntactic rule: `<token node><space><loose op><space><token node>`. The second aspect of this pull request is the beginning of support for a signature syntax. Before implementing signatures, a necessary prerequisite is for the core syntax to support multi-line programs. That work establishes a few things: - `;` and newlines are handled in the core grammar, and both count as "separators" - line comments begin with `#` and continue until the end of the line In this commit, multi-token productions in the core grammar can use separators interchangably with spaces. However, I think we will ultimately want a different rule preventing separators from occurring before an infix operator, so that the end of a line is always unambiguous. This would avoid gratuitous differences between modules and repl usage. We already effectively have this rule, because otherwise `x<newline> | y` would be a single pipeline, but of course that wouldn't work.
2019-12-04 21:14:52 +00:00
[[package]]
name = "enumflags2"
version = "0.6.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "33121c8782ba948ba332dab29311b026a8716dc65a1599e5b88f392d38496af8"
dependencies = [
"enumflags2_derive",
]
[[package]]
name = "enumflags2_derive"
version = "0.6.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ecf634c5213044b8d54a46dd282cf5dd1f86bb5cb53e92c409cb4680a7fb9894"
dependencies = [
"proc-macro2",
"quote",
"syn",
]
A real parser (lalrpop)
2019-05-26 06:54:41 +00:00
[[package]]
name = "env_logger"
bump deps
2019-07-29 07:46:24 +00:00
version = "0.6.2"
A real parser (lalrpop)
2019-05-26 06:54:41 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "aafcde04e90a5226a6443b7aabdb016ba2f8307c847d524724bd9b346dd1a2d3"
A real parser (lalrpop)
2019-05-26 06:54:41 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"atty",
"humantime",
"log",
"regex",
"termcolor",
A real parser (lalrpop)
2019-05-26 06:54:41 +00:00
]
Switch stdin redirect to manual. Add test (#1367)
2020-02-10 06:55:07 +00:00
[[package]]
name = "env_logger"
version = "0.7.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "44533bbbb3bb3c1fa17d9f2e4e38bbbaf8396ba82193c4cb1b6445d711445d36"
dependencies = [
"atty",
"humantime",
"log",
"regex",
"termcolor",
]
Extract core stuff into own crates This commit extracts five new crates: - nu-source, which contains the core source-code handling logic in Nu, including Text, Span, and also the pretty.rs-based debug logic - nu-parser, which is the parser and expander logic - nu-protocol, which is the bulk of the types and basic conveniences used by plugins - nu-errors, which contains ShellError, ParseError and error handling conveniences - nu-textview, which is the textview plugin extracted into a crate One of the major consequences of this refactor is that it's no longer possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so a lot of types became more concrete (Value became a concrete type instead of Spanned<Value>, for example). This also turned a number of inherent methods in the main nu crate into plain functions (impl Value {} became a bunch of functions in the `value` namespace in `crate::data::value`).
2019-11-26 02:30:48 +00:00
[[package]]
name = "erased-serde"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.3.10"
Extract core stuff into own crates This commit extracts five new crates: - nu-source, which contains the core source-code handling logic in Nu, including Text, Span, and also the pretty.rs-based debug logic - nu-parser, which is the parser and expander logic - nu-protocol, which is the bulk of the types and basic conveniences used by plugins - nu-errors, which contains ShellError, ParseError and error handling conveniences - nu-textview, which is the textview plugin extracted into a crate One of the major consequences of this refactor is that it's no longer possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so a lot of types became more concrete (Value became a concrete type instead of Spanned<Value>, for example). This also turned a number of inherent methods in the main nu crate into plain functions (impl Value {} became a bunch of functions in the `value` namespace in `crate::data::value`).
2019-11-26 02:30:48 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "cd7d80305c9bd8cd78e3c753eb9fb110f83621e5211f1a3afffcc812b104daf9"
Extract core stuff into own crates This commit extracts five new crates: - nu-source, which contains the core source-code handling logic in Nu, including Text, Span, and also the pretty.rs-based debug logic - nu-parser, which is the parser and expander logic - nu-protocol, which is the bulk of the types and basic conveniences used by plugins - nu-errors, which contains ShellError, ParseError and error handling conveniences - nu-textview, which is the textview plugin extracted into a crate One of the major consequences of this refactor is that it's no longer possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so a lot of types became more concrete (Value became a concrete type instead of Spanned<Value>, for example). This also turned a number of inherent methods in the main nu crate into plain functions (impl Value {} became a bunch of functions in the `value` namespace in `crate::data::value`).
2019-11-26 02:30:48 +00:00
dependencies = [
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"serde 1.0.104",
Extract core stuff into own crates This commit extracts five new crates: - nu-source, which contains the core source-code handling logic in Nu, including Text, Span, and also the pretty.rs-based debug logic - nu-parser, which is the parser and expander logic - nu-protocol, which is the bulk of the types and basic conveniences used by plugins - nu-errors, which contains ShellError, ParseError and error handling conveniences - nu-textview, which is the textview plugin extracted into a crate One of the major consequences of this refactor is that it's no longer possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so a lot of types became more concrete (Value became a concrete type instead of Spanned<Value>, for example). This also turned a number of inherent methods in the main nu crate into plain functions (impl Value {} became a bunch of functions in the `value` namespace in `crate::data::value`).
2019-11-26 02:30:48 +00:00
]
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "failure"
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
version = "0.1.7"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
checksum = "b8529c2421efa3066a5cbd8063d2244603824daccb6936b079010bb2aa89464b"
objectshell initial commit
2019-05-10 16:59:12 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"backtrace",
objectshell initial commit
2019-05-10 16:59:12 +00:00
]
Add SQLite support
2019-08-27 21:45:18 +00:00
[[package]]
name = "fallible-iterator"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "4443176a9f2c162692bd3d352d745ef9413eec5782a80d8fd6f8a1ac692a07f7"
Add SQLite support
2019-08-27 21:45:18 +00:00
[[package]]
name = "fallible-streaming-iterator"
version = "0.1.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "7360491ce676a36bf9bb3c56c1aa791658183a54d2744120f27285738d90465a"
Add SQLite support
2019-08-27 21:45:18 +00:00
Add block size to du (#1341) * Add block size to du * Change blocks to physical size * Use path instead of strings for file/directory names * Why don't I just use paths instead of strings anyway? * shorten physical size and apparent size to physical and apparent resp.
2020-02-10 20:32:18 +00:00
[[package]]
name = "filesize"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3a941e39ae509cebcd46c6734c20553a9a209b92cea5fc54618fe778fea61701"
dependencies = [
"winapi 0.3.8",
]
Add tree sink
2019-06-07 07:50:26 +00:00
[[package]]
name = "fixedbitset"
version = "0.1.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "86d4de0081402f5e88cdac65c8dcdcc73118c1a7a465e2a05f0da05843a8ea33"
Add tree sink
2019-06-07 07:50:26 +00:00
Bat
2019-05-18 01:24:13 +00:00
[[package]]
name = "flate2"
Merge master
2019-11-16 17:17:05 +00:00
version = "1.0.13"
Bat
2019-05-18 01:24:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "6bd6d6f4752952feb71363cffc9ebac9411b75b87c6ab6058c40c8900cf43c0f"
Bat
2019-05-18 01:24:13 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"cfg-if",
"crc32fast",
"libc",
"miniz_oxide",
Bat
2019-05-18 01:24:13 +00:00
]
[[package]]
name = "fnv"
version = "1.0.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "2fad85553e09a6f881f739c29f0b00b0f01357c743266d478b68951ce23285f3"
Bat
2019-05-18 01:24:13 +00:00
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
[[package]]
name = "fuchsia-zircon"
version = "0.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2e9763c69ebaae630ba35f74888db465e49e259ba1bc0eda7d06f4a067615d82"
dependencies = [
"bitflags",
"fuchsia-zircon-sys",
]
[[package]]
name = "fuchsia-zircon-sys"
version = "0.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3dcaa9ae7725d12cdb85b3ad99a434db70b468c09ded17e012d86b5c1010f7a7"
Pipe external to internal Each line is a string object
2019-05-24 18:48:33 +00:00
[[package]]
name = "futures"
Fix #811 (#813)
2019-10-13 04:53:58 +00:00
version = "0.1.29"
Pipe external to internal Each line is a string object
2019-05-24 18:48:33 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "1b980f2816d6ee8673b6517b52cb0e808a180efc92e5c19d02cdda79066703ef"
Pipe external to internal Each line is a string object
2019-05-24 18:48:33 +00:00
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
[[package]]
name = "futures"
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
version = "0.3.3"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
checksum = "ad6636318d07abeb4656157ef1936c64485f066c7f9ce5d7c5b879fcb6dd5ccb"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
dependencies = [
"futures-channel",
"futures-core",
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
"futures-executor",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"futures-io",
"futures-sink",
"futures-task",
"futures-util",
]
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
[[package]]
name = "futures-channel"
Switch stdin redirect to manual. Add test (#1367)
2020-02-10 06:55:07 +00:00
version = "0.3.4"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch stdin redirect to manual. Add test (#1367)
2020-02-10 06:55:07 +00:00
checksum = "f0c77d04ce8edd9cb903932b608268b3fffec4163dc053b3b402bf47eac1f1a8"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
dependencies = [
"futures-core",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"futures-sink",
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
]
A bunch of rework I'm gonna use a VecDeque now instead of trying to get async streams working to make progress, but the intent is that we should be able to use async streams in and out to interleave the work better.
2019-05-13 17:30:51 +00:00
[[package]]
Small restructuring
2019-05-23 04:30:43 +00:00
name = "futures-channel-preview"
Bump dep versions
2019-11-10 17:48:49 +00:00
version = "0.3.0-alpha.19"
A bunch of rework I'm gonna use a VecDeque now instead of trying to get async streams working to make progress, but the intent is that we should be able to use async streams in and out to interleave the work better.
2019-05-13 17:30:51 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "d5e5f4df964fa9c1c2f8bddeb5c3611631cacd93baf810fc8bb2fb4b495c263a"
Small restructuring
2019-05-23 04:30:43 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"futures-core-preview",
"futures-sink-preview",
Small restructuring
2019-05-23 04:30:43 +00:00
]
A bunch of rework I'm gonna use a VecDeque now instead of trying to get async streams working to make progress, but the intent is that we should be able to use async streams in and out to interleave the work better.
2019-05-13 17:30:51 +00:00
--no-edit
2019-11-04 15:47:03 +00:00
[[package]]
name = "futures-core"
Switch stdin redirect to manual. Add test (#1367)
2020-02-10 06:55:07 +00:00
version = "0.3.4"
--no-edit
2019-11-04 15:47:03 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch stdin redirect to manual. Add test (#1367)
2020-02-10 06:55:07 +00:00
checksum = "f25592f769825e89b92358db00d26f965761e094951ac44d3663ef25b7ac464a"
--no-edit
2019-11-04 15:47:03 +00:00
A bunch of rework I'm gonna use a VecDeque now instead of trying to get async streams working to make progress, but the intent is that we should be able to use async streams in and out to interleave the work better.
2019-05-13 17:30:51 +00:00
[[package]]
Small restructuring
2019-05-23 04:30:43 +00:00
name = "futures-core-preview"
Bump dep versions
2019-11-10 17:48:49 +00:00
version = "0.3.0-alpha.19"
Add opening urls
2019-06-08 18:09:17 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "b35b6263fb1ef523c3056565fa67b1d16f0a8604ff12b11b08c25f28a734c60a"
Add opening urls
2019-06-08 18:09:17 +00:00
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
[[package]]
name = "futures-executor"
version = "0.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "46a5e593d77bee52393c7f3b16b8b413214096d3f7dc4f5f4c57dee01ad2bdaf"
dependencies = [
"futures-core",
"futures-task",
"futures-util",
]
Small restructuring
2019-05-23 04:30:43 +00:00
[[package]]
name = "futures-executor-preview"
Bump dep versions
2019-11-10 17:48:49 +00:00
version = "0.3.0-alpha.19"
A bunch of rework I'm gonna use a VecDeque now instead of trying to get async streams working to make progress, but the intent is that we should be able to use async streams in and out to interleave the work better.
2019-05-13 17:30:51 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "75236e88bd9fe88e5e8bfcd175b665d0528fe03ca4c5207fabc028c8f9d93e98"
A bunch of rework I'm gonna use a VecDeque now instead of trying to get async streams working to make progress, but the intent is that we should be able to use async streams in and out to interleave the work better.
2019-05-13 17:30:51 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"futures-core-preview",
"futures-util-preview",
"num_cpus",
Small restructuring
2019-05-23 04:30:43 +00:00
]
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
[[package]]
name = "futures-io"
Switch stdin redirect to manual. Add test (#1367)
2020-02-10 06:55:07 +00:00
version = "0.3.4"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch stdin redirect to manual. Add test (#1367)
2020-02-10 06:55:07 +00:00
checksum = "a638959aa96152c7a4cddf50fcb1e3fede0583b27157c26e67d6f99904090dc6"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
Small restructuring
2019-05-23 04:30:43 +00:00
[[package]]
name = "futures-io-preview"
Bump dep versions
2019-11-10 17:48:49 +00:00
version = "0.3.0-alpha.19"
Small restructuring
2019-05-23 04:30:43 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "f4914ae450db1921a56c91bde97a27846287d062087d4a652efc09bb3a01ebda"
Small restructuring
2019-05-23 04:30:43 +00:00
--no-edit
2019-11-04 15:47:03 +00:00
[[package]]
name = "futures-macro"
Switch stdin redirect to manual. Add test (#1367)
2020-02-10 06:55:07 +00:00
version = "0.3.4"
--no-edit
2019-11-04 15:47:03 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch stdin redirect to manual. Add test (#1367)
2020-02-10 06:55:07 +00:00
checksum = "9a5081aa3de1f7542a794a397cde100ed903b0630152d0973479018fd85423a7"
--no-edit
2019-11-04 15:47:03 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"proc-macro-hack",
"proc-macro2",
"quote",
"syn",
--no-edit
2019-11-04 15:47:03 +00:00
]
Small restructuring
2019-05-23 04:30:43 +00:00
[[package]]
name = "futures-preview"
Bump dep versions
2019-11-10 17:48:49 +00:00
version = "0.3.0-alpha.19"
Small restructuring
2019-05-23 04:30:43 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "3b1dce2a0267ada5c6ff75a8ba864b4e679a9e2aa44262af7a3b5516d530d76e"
Small restructuring
2019-05-23 04:30:43 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"futures-channel-preview",
"futures-core-preview",
"futures-executor-preview",
"futures-io-preview",
"futures-sink-preview",
"futures-util-preview",
Small restructuring
2019-05-23 04:30:43 +00:00
]
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
[[package]]
name = "futures-sink"
Switch stdin redirect to manual. Add test (#1367)
2020-02-10 06:55:07 +00:00
version = "0.3.4"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch stdin redirect to manual. Add test (#1367)
2020-02-10 06:55:07 +00:00
checksum = "3466821b4bc114d95b087b850a724c6f83115e929bc88f1fa98a3304a944c8a6"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
Small restructuring
2019-05-23 04:30:43 +00:00
[[package]]
name = "futures-sink-preview"
Bump dep versions
2019-11-10 17:48:49 +00:00
version = "0.3.0-alpha.19"
Small restructuring
2019-05-23 04:30:43 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "86f148ef6b69f75bb610d4f9a2336d4fc88c4b5b67129d1a340dd0fd362efeec"
Small restructuring
2019-05-23 04:30:43 +00:00
--no-edit
2019-11-04 15:47:03 +00:00
[[package]]
name = "futures-task"
Switch stdin redirect to manual. Add test (#1367)
2020-02-10 06:55:07 +00:00
version = "0.3.4"
--no-edit
2019-11-04 15:47:03 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch stdin redirect to manual. Add test (#1367)
2020-02-10 06:55:07 +00:00
checksum = "7b0a34e53cf6cdcd0178aa573aed466b646eb3db769570841fda0c7ede375a27"
--no-edit
2019-11-04 15:47:03 +00:00
Experiment with async/await-enabled ps
2019-08-30 19:07:07 +00:00
[[package]]
name = "futures-timer"
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
version = "2.0.2"
Experiment with async/await-enabled ps
2019-08-30 19:07:07 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
checksum = "a1de7508b218029b0f01662ed8f61b1c964b3ae99d6f25462d0f55a595109df6"
Experiment with async/await-enabled ps
2019-08-30 19:07:07 +00:00
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
[[package]]
name = "futures-timer"
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
version = "3.0.1"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
checksum = "3de1a2b2a2a33d9e60e17980b60ee061eeaae96a5abe9121db0fdb9af167a1c5"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
--no-edit
2019-11-04 15:47:03 +00:00
[[package]]
name = "futures-util"
Switch stdin redirect to manual. Add test (#1367)
2020-02-10 06:55:07 +00:00
version = "0.3.4"
--no-edit
2019-11-04 15:47:03 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch stdin redirect to manual. Add test (#1367)
2020-02-10 06:55:07 +00:00
checksum = "22766cf25d64306bedf0384da004d05c9974ab104fcc4528f1236181c18004c5"
--no-edit
2019-11-04 15:47:03 +00:00
dependencies = [
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
"futures 0.1.29",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"futures-channel",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"futures-core",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"futures-io",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"futures-macro",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"futures-sink",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"futures-task",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"memchr",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"pin-utils",
"proc-macro-hack",
"proc-macro-nested",
"slab",
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
"tokio-io",
--no-edit
2019-11-04 15:47:03 +00:00
]
Small restructuring
2019-05-23 04:30:43 +00:00
[[package]]
name = "futures-util-preview"
Bump dep versions
2019-11-10 17:48:49 +00:00
version = "0.3.0-alpha.19"
Small restructuring
2019-05-23 04:30:43 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "5ce968633c17e5f97936bd2797b6e38fb56cf16a7422319f7ec2e30d3c470e8d"
Small restructuring
2019-05-23 04:30:43 +00:00
dependencies = [
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"futures 0.1.29",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"futures-channel-preview",
"futures-core-preview",
"futures-io-preview",
"futures-sink-preview",
"memchr",
"pin-utils",
"slab",
"tokio-io",
Pipe external to internal Each line is a string object
2019-05-24 18:48:33 +00:00
]
[[package]]
name = "futures_codec"
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
version = "0.4.0"
Pipe external to internal Each line is a string object
2019-05-24 18:48:33 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
checksum = "fe8859feb7140742ed1a2a85a07941100ad2b5f98a421b353931d718a34144d1"
Pipe external to internal Each line is a string object
2019-05-24 18:48:33 +00:00
dependencies = [
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
"bytes 0.5.4",
"futures 0.3.3",
"memchr",
"pin-project",
A bunch of rework I'm gonna use a VecDeque now instead of trying to get async streams working to make progress, but the intent is that we should be able to use async streams in and out to interleave the work better.
2019-05-13 17:30:51 +00:00
]
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
[[package]]
name = "gethostname"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
version = "0.2.1"
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
checksum = "e692e296bfac1d2533ef168d0b60ff5897b8b70a4009276834014dd8924cc028"
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"libc",
"winapi 0.3.8",
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
]
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
[[package]]
name = "getrandom"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.1.14"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "7abc8dd8451921606d809ba32e95b6111925cd2906060d2dcc29c070220503eb"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"cfg-if",
"libc",
"wasi",
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
]
Evaluator MVP (#39) Evaluator, MVP
2019-05-28 06:45:18 +00:00
[[package]]
name = "getset"
Bump dep versions
2019-11-10 17:48:49 +00:00
version = "0.0.9"
Evaluator MVP (#39) Evaluator, MVP
2019-05-28 06:45:18 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "5bb3f5b7d8d70c9bd23cf29b2b38094661418fb0ea79f1b0cc2019a11d6f5429"
Evaluator MVP (#39) Evaluator, MVP
2019-05-28 06:45:18 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"proc-macro2",
"quote",
"syn",
Evaluator MVP (#39) Evaluator, MVP
2019-05-28 06:45:18 +00:00
]
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
[[package]]
name = "getset"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f62a139c59ae846c3964c392f12aac68f1997d1a40e9d3b40a89a4ab553e04a0"
dependencies = [
"proc-macro-error",
"proc-macro2",
"quote",
"syn",
]
Extract core stuff into own crates This commit extracts five new crates: - nu-source, which contains the core source-code handling logic in Nu, including Text, Span, and also the pretty.rs-based debug logic - nu-parser, which is the parser and expander logic - nu-protocol, which is the bulk of the types and basic conveniences used by plugins - nu-errors, which contains ShellError, ParseError and error handling conveniences - nu-textview, which is the textview plugin extracted into a crate One of the major consequences of this refactor is that it's no longer possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so a lot of types became more concrete (Value became a concrete type instead of Spanned<Value>, for example). This also turned a number of inherent methods in the main nu crate into plain functions (impl Value {} became a bunch of functions in the `value` namespace in `crate::data::value`).
2019-11-26 02:30:48 +00:00
[[package]]
name = "ghost"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "2a36606a68532b5640dc86bb1f33c64b45c4682aad4c50f3937b317ea387f3d6"
Extract core stuff into own crates This commit extracts five new crates: - nu-source, which contains the core source-code handling logic in Nu, including Text, Span, and also the pretty.rs-based debug logic - nu-parser, which is the parser and expander logic - nu-protocol, which is the bulk of the types and basic conveniences used by plugins - nu-errors, which contains ShellError, ParseError and error handling conveniences - nu-textview, which is the textview plugin extracted into a crate One of the major consequences of this refactor is that it's no longer possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so a lot of types became more concrete (Value became a concrete type instead of Spanned<Value>, for example). This also turned a number of inherent methods in the main nu crate into plain functions (impl Value {} became a bunch of functions in the `value` namespace in `crate::data::value`).
2019-11-26 02:30:48 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"proc-macro2",
"quote",
"syn",
Extract core stuff into own crates This commit extracts five new crates: - nu-source, which contains the core source-code handling logic in Nu, including Text, Span, and also the pretty.rs-based debug logic - nu-parser, which is the parser and expander logic - nu-protocol, which is the bulk of the types and basic conveniences used by plugins - nu-errors, which contains ShellError, ParseError and error handling conveniences - nu-textview, which is the textview plugin extracted into a crate One of the major consequences of this refactor is that it's no longer possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so a lot of types became more concrete (Value became a concrete type instead of Spanned<Value>, for example). This also turned a number of inherent methods in the main nu crate into plain functions (impl Value {} became a bunch of functions in the `value` namespace in `crate::data::value`).
2019-11-26 02:30:48 +00:00
]
Add git branch to prompt
2019-06-01 21:11:28 +00:00
[[package]]
name = "git2"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
version = "0.11.0"
Add git branch to prompt
2019-06-01 21:11:28 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
checksum = "77519ef7c5beee314d0804d4534f01e0f9e8d9acdee2b7a48627e590b27e0ec4"
Add git branch to prompt
2019-06-01 21:11:28 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"bitflags",
"libc",
"libgit2-sys",
"log",
"url",
Add git branch to prompt
2019-06-01 21:11:28 +00:00
]
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
[[package]]
name = "glob"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "9b919933a397b79c37e33b77bb2aa3dc8eb6e165ad809e58ff75bc7db2e34574"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
[[package]]
name = "h2"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b9433d71e471c1736fd5a61b671fc0b148d7a2992f666c958d03cd8feb3b88d1"
dependencies = [
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
"bytes 0.5.4",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"fnv",
"futures-core",
"futures-sink",
"futures-util",
"http 0.2.0",
"indexmap",
"log",
"slab",
"tokio",
"tokio-util",
]
Add opening urls
2019-06-08 18:09:17 +00:00
[[package]]
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
name = "heck"
version = "0.3.1"
Add opening urls
2019-06-08 18:09:17 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "20564e78d53d2bb135c343b3f47714a56af2061f1c928fdb541dc7b9fdd94205"
Add opening urls
2019-06-08 18:09:17 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"unicode-segmentation",
Add opening urls
2019-06-08 18:09:17 +00:00
]
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
[[package]]
name = "heim"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
version = "0.0.9"
Lots of fixes ahead of release
2019-08-21 06:39:57 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
checksum = "28f11cfed41a4703f8f56ccbe411073c52bd3996d92e3ccac90d36bd0e86e0eb"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"heim-common",
"heim-cpu",
"heim-derive",
"heim-disk",
"heim-host",
"heim-memory",
"heim-net",
"heim-process",
"heim-runtime",
"heim-sensors",
"heim-virt",
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
]
[[package]]
name = "heim-common"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
version = "0.0.9"
Lots of fixes ahead of release
2019-08-21 06:39:57 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
checksum = "f97d185137ab6437750cb22a115d4c64027620d48c57893d31720abcba42c388"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"cfg-if",
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
"core-foundation 0.7.0",
"futures-core",
"futures-util",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"lazy_static 1.4.0",
"libc",
"mach 0.3.2",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"nix 0.16.1",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"pin-utils",
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
"uom",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"winapi 0.3.8",
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
]
[[package]]
name = "heim-cpu"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
version = "0.0.9"
Lots of fixes ahead of release
2019-08-21 06:39:57 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
checksum = "328091d34621a28af550523e1c139749fa4bc4590a8ea91b160a0f4b82dd8b06"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"cfg-if",
"heim-common",
"heim-derive",
"heim-runtime",
"lazy_static 1.4.0",
"libc",
"mach 0.3.2",
"winapi 0.3.8",
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
]
[[package]]
name = "heim-derive"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
version = "0.0.9"
Lots of fixes ahead of release
2019-08-21 06:39:57 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
checksum = "dc97d9bf8ca9af8a02a533acea548756f23d4759474a1df8e79eb2b57f3cf7ac"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"proc-macro2",
"quote",
"syn",
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
]
[[package]]
name = "heim-disk"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
version = "0.0.9"
Lots of fixes ahead of release
2019-08-21 06:39:57 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
checksum = "82179359c7b215ae46fe8ac0f9015b8e5dfd6368cd0d113f261b28cb8993713f"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"bitflags",
"cfg-if",
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
"core-foundation 0.7.0",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"heim-common",
"heim-derive",
"heim-runtime",
"libc",
"mach 0.3.2",
"widestring",
"winapi 0.3.8",
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
]
[[package]]
name = "heim-host"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
version = "0.0.9"
Lots of fixes ahead of release
2019-08-21 06:39:57 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
checksum = "64b9c8c5f7d1479102a503e3f233241bfb819bf916f02b15e10ba5fbfee7a7f3"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"cfg-if",
"heim-common",
"heim-derive",
"heim-runtime",
"lazy_static 1.4.0",
"libc",
"mach 0.3.2",
"platforms",
"winapi 0.3.8",
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
]
[[package]]
name = "heim-memory"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
version = "0.0.9"
Lots of fixes ahead of release
2019-08-21 06:39:57 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
checksum = "d04e9e068b57049062622cf4a182a45f320459e266c39dfc52ca65fc8c178e3a"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"cfg-if",
"heim-common",
"heim-derive",
"heim-runtime",
"lazy_static 1.4.0",
"libc",
"mach 0.3.2",
"winapi 0.3.8",
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
]
[[package]]
name = "heim-net"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
version = "0.0.9"
Lots of fixes ahead of release
2019-08-21 06:39:57 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
checksum = "4c6323430ecae9b74378b37d0078768989c98b570daacec1d899737d90d72a5b"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"bitflags",
"cfg-if",
"heim-common",
"heim-derive",
"heim-runtime",
"hex 0.4.0",
"libc",
"macaddr",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"nix 0.16.1",
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
]
[[package]]
name = "heim-process"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
version = "0.0.9"
Lots of fixes ahead of release
2019-08-21 06:39:57 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
checksum = "b20a58b335dc9837088b2c9290822b55c661071cb542f0002e62ed18e8464379"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"cfg-if",
"darwin-libproc",
"heim-common",
"heim-cpu",
"heim-derive",
"heim-host",
"heim-net",
"heim-runtime",
"lazy_static 1.4.0",
"libc",
"mach 0.3.2",
"memchr",
"ntapi",
"ordered-float",
"winapi 0.3.8",
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
]
Pin semver breaking dep
2019-08-08 17:33:19 +00:00
[[package]]
name = "heim-runtime"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
version = "0.0.5"
Lots of fixes ahead of release
2019-08-21 06:39:57 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
checksum = "f87591c7b202868445a7da04b3d8f987b0672dd68c3d66e24fe8f759171dd612"
Pin semver breaking dep
2019-08-08 17:33:19 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"cfg-if",
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
"futures-channel",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"heim-common",
"lazy_static 1.4.0",
"threadpool",
Pin semver breaking dep
2019-08-08 17:33:19 +00:00
]
Update to heim v0.0.7.
2019-08-28 15:53:59 +00:00
[[package]]
name = "heim-sensors"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
version = "0.0.4"
Update to heim v0.0.7.
2019-08-28 15:53:59 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
checksum = "6f663425e6ed38a6356ee5751a2ebae421f7449fd0507b7e698c7e1e9fabee0c"
Update to heim v0.0.7.
2019-08-28 15:53:59 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"cfg-if",
"heim-common",
"heim-derive",
"heim-runtime",
Update to heim v0.0.7.
2019-08-28 15:53:59 +00:00
]
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
[[package]]
name = "heim-virt"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
version = "0.0.9"
Lots of fixes ahead of release
2019-08-21 06:39:57 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
checksum = "7dd975e9ca42170c0f65102b867e69c3d060027f9bb02fb29cc554f7a0e5680b"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"cfg-if",
"heim-common",
"heim-runtime",
"raw-cpuid",
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
]
Merge master
2019-11-16 17:17:05 +00:00
[[package]]
name = "hermit-abi"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.1.6"
Merge master
2019-11-16 17:17:05 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "eff2656d88f158ce120947499e971d743c05dbcbed62e5bd2f38f1698bbc3772"
Merge master
2019-11-16 17:17:05 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"libc",
Merge master
2019-11-16 17:17:05 +00:00
]
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
[[package]]
name = "hex"
version = "0.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "805026a5d0141ffc30abb3be3173848ad46a1b1664fe632428479619a3644d77"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
Add Cargo.lock
2019-09-24 19:02:35 +00:00
[[package]]
name = "hex"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "023b39be39e3a2da62a94feb433e91e8bcd37676fbc8bea371daf52b7a769a3e"
Add Cargo.lock
2019-09-24 19:02:35 +00:00
Add opening urls
2019-06-08 18:09:17 +00:00
[[package]]
name = "http"
Clean up expansion of external words Previously, external words accidentally used ExpansionRule::new().allow_external_command(), when it should have been ExpansionRule::new().allow_external_word(). External words are the broadest category in the parser, and are the appropriate category for external arguments. This was just a mistake.
2019-12-03 00:34:33 +00:00
version = "0.1.21"
Add opening urls
2019-06-08 18:09:17 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Clean up expansion of external words Previously, external words accidentally used ExpansionRule::new().allow_external_command(), when it should have been ExpansionRule::new().allow_external_word(). External words are the broadest category in the parser, and are the appropriate category for external arguments. This was just a mistake.
2019-12-03 00:34:33 +00:00
checksum = "d6ccf5ede3a895d8856620237b2f02972c1bbc78d2965ad7fe8838d4a0ed41f0"
Add opening urls
2019-06-08 18:09:17 +00:00
dependencies = [
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"bytes 0.4.12",
"fnv",
"itoa",
]
[[package]]
name = "http"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b708cc7f06493459026f53b9a61a7a121a5d1ec6238dee58ea4941132b30156b"
dependencies = [
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
"bytes 0.5.4",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"fnv",
"itoa",
Add opening urls
2019-06-08 18:09:17 +00:00
]
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
[[package]]
name = "http-body"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "13d5ff830006f7646652e057693569bfe0d51760c0085a071769d142a205111b"
dependencies = [
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
"bytes 0.5.4",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"http 0.2.0",
]
[[package]]
name = "httparse"
version = "1.3.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "cd179ae861f0c2e53da70d892f5f3029f9594be0c41dc5269cd371691b1dc2f9"
Bat
2019-05-18 01:24:13 +00:00
[[package]]
name = "humantime"
Fix #811 (#813)
2019-10-13 04:53:58 +00:00
version = "1.3.0"
Bat
2019-05-18 01:24:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "df004cfca50ef23c36850aaaa59ad52cc70d0e90243c3c7737a4dd32dc7a3c4f"
Bat
2019-05-18 01:24:13 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"quick-error",
Bat
2019-05-18 01:24:13 +00:00
]
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
[[package]]
name = "hyper"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.13.2"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "fa1c527bbc634be72aa7ba31e4e4def9bbb020f5416916279b7c705cd838893e"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
dependencies = [
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
"bytes 0.5.4",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"futures-channel",
"futures-core",
"futures-util",
"h2",
"http 0.2.0",
"http-body",
"httparse",
"itoa",
"log",
"net2",
"pin-project",
"time",
"tokio",
"tower-service",
"want",
]
[[package]]
name = "hyper-rustls"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.19.1"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "f6ea6215c7314d450ee45970ab8b3851ab447a0e6bafdd19e31b20a42dbb7faf"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
dependencies = [
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
"bytes 0.5.4",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"ct-logs",
"futures-util",
"hyper",
"rustls",
"rustls-native-certs",
"tokio",
"tokio-rustls",
"webpki",
]
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
[[package]]
name = "ichwh"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.3.1"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "b37aaf19f3ca34681b606f8b973f4f3422e40e418b30945d3cf9ae72021692ed"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
dependencies = [
"async-std",
"cfg-if",
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
"futures 0.3.3",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"thiserror",
]
bump deps
2019-07-29 07:46:24 +00:00
[[package]]
name = "idna"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "02e2673c30ee86b5b96a9cb52ad15718aa1f966f5ab9ad54a8b95d5ca33120a9"
bump deps
2019-07-29 07:46:24 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"matches",
"unicode-bidi",
"unicode-normalization",
bump deps
2019-07-29 07:46:24 +00:00
]
Add some logic for more binary formats
2019-07-05 07:53:09 +00:00
[[package]]
name = "image"
Upgrade crossterm (#1288) * WIP * Finish porting to new crossterm * Fmt
2020-01-27 02:51:46 +00:00
version = "0.22.4"
Add some logic for more binary formats
2019-07-05 07:53:09 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade crossterm (#1288) * WIP * Finish porting to new crossterm * Fmt
2020-01-27 02:51:46 +00:00
checksum = "53cb19c4e35102e5c6fb9ade5e0e236c5588424dc171a849af3141bf0b47768a"
Add some logic for more binary formats
2019-07-05 07:53:09 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"byteorder",
"jpeg-decoder",
"num-iter",
"num-rational",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"num-traits 0.2.11",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"png",
Add some logic for more binary formats
2019-07-05 07:53:09 +00:00
]
Internals cleanup and | select ...fields
2019-05-15 18:14:51 +00:00
[[package]]
name = "indexmap"
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
version = "1.3.2"
Internals cleanup and | select ...fields
2019-05-15 18:14:51 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
checksum = "076f042c5b7b98f31d205f1249267e12a6518c1481e9dae9764af19b707d2292"
Improve signature infrastructure The `config` command uses different kinds of named arguments, which illustrates how it works.
2019-06-01 05:50:16 +00:00
dependencies = [
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"autocfg 1.0.0",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"serde 1.0.104",
Improve signature infrastructure The `config` command uses different kinds of named arguments, which illustrates how it works.
2019-06-01 05:50:16 +00:00
]
Internals cleanup and | select ...fields
2019-05-15 18:14:51 +00:00
Add some logic for more binary formats
2019-07-05 07:53:09 +00:00
[[package]]
name = "inflate"
version = "0.4.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "1cdb29978cc5797bd8dcc8e5bf7de604891df2a8dc576973d71a281e916db2ff"
Add some logic for more binary formats
2019-07-05 07:53:09 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"adler32",
Add some logic for more binary formats
2019-07-05 07:53:09 +00:00
]
Extract core stuff into own crates This commit extracts five new crates: - nu-source, which contains the core source-code handling logic in Nu, including Text, Span, and also the pretty.rs-based debug logic - nu-parser, which is the parser and expander logic - nu-protocol, which is the bulk of the types and basic conveniences used by plugins - nu-errors, which contains ShellError, ParseError and error handling conveniences - nu-textview, which is the textview plugin extracted into a crate One of the major consequences of this refactor is that it's no longer possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so a lot of types became more concrete (Value became a concrete type instead of Spanned<Value>, for example). This also turned a number of inherent methods in the main nu crate into plain functions (impl Value {} became a bunch of functions in the `value` namespace in `crate::data::value`).
2019-11-26 02:30:48 +00:00
[[package]]
name = "inventory"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
version = "0.1.5"
Extract core stuff into own crates This commit extracts five new crates: - nu-source, which contains the core source-code handling logic in Nu, including Text, Span, and also the pretty.rs-based debug logic - nu-parser, which is the parser and expander logic - nu-protocol, which is the bulk of the types and basic conveniences used by plugins - nu-errors, which contains ShellError, ParseError and error handling conveniences - nu-textview, which is the textview plugin extracted into a crate One of the major consequences of this refactor is that it's no longer possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so a lot of types became more concrete (Value became a concrete type instead of Spanned<Value>, for example). This also turned a number of inherent methods in the main nu crate into plain functions (impl Value {} became a bunch of functions in the `value` namespace in `crate::data::value`).
2019-11-26 02:30:48 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
checksum = "2bf98296081bd2cb540acc09ef9c97f22b7e487841520350293605db1b2c7a27"
Extract core stuff into own crates This commit extracts five new crates: - nu-source, which contains the core source-code handling logic in Nu, including Text, Span, and also the pretty.rs-based debug logic - nu-parser, which is the parser and expander logic - nu-protocol, which is the bulk of the types and basic conveniences used by plugins - nu-errors, which contains ShellError, ParseError and error handling conveniences - nu-textview, which is the textview plugin extracted into a crate One of the major consequences of this refactor is that it's no longer possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so a lot of types became more concrete (Value became a concrete type instead of Spanned<Value>, for example). This also turned a number of inherent methods in the main nu crate into plain functions (impl Value {} became a bunch of functions in the `value` namespace in `crate::data::value`).
2019-11-26 02:30:48 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"ctor",
"ghost",
"inventory-impl",
Extract core stuff into own crates This commit extracts five new crates: - nu-source, which contains the core source-code handling logic in Nu, including Text, Span, and also the pretty.rs-based debug logic - nu-parser, which is the parser and expander logic - nu-protocol, which is the bulk of the types and basic conveniences used by plugins - nu-errors, which contains ShellError, ParseError and error handling conveniences - nu-textview, which is the textview plugin extracted into a crate One of the major consequences of this refactor is that it's no longer possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so a lot of types became more concrete (Value became a concrete type instead of Spanned<Value>, for example). This also turned a number of inherent methods in the main nu crate into plain functions (impl Value {} became a bunch of functions in the `value` namespace in `crate::data::value`).
2019-11-26 02:30:48 +00:00
]
[[package]]
name = "inventory-impl"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
version = "0.1.5"
Extract core stuff into own crates This commit extracts five new crates: - nu-source, which contains the core source-code handling logic in Nu, including Text, Span, and also the pretty.rs-based debug logic - nu-parser, which is the parser and expander logic - nu-protocol, which is the bulk of the types and basic conveniences used by plugins - nu-errors, which contains ShellError, ParseError and error handling conveniences - nu-textview, which is the textview plugin extracted into a crate One of the major consequences of this refactor is that it's no longer possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so a lot of types became more concrete (Value became a concrete type instead of Spanned<Value>, for example). This also turned a number of inherent methods in the main nu crate into plain functions (impl Value {} became a bunch of functions in the `value` namespace in `crate::data::value`).
2019-11-26 02:30:48 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
checksum = "0a8e30575afe28eea36a9a39136b70b2fb6b0dd0a212a5bd1f30a498395c0274"
Extract core stuff into own crates This commit extracts five new crates: - nu-source, which contains the core source-code handling logic in Nu, including Text, Span, and also the pretty.rs-based debug logic - nu-parser, which is the parser and expander logic - nu-protocol, which is the bulk of the types and basic conveniences used by plugins - nu-errors, which contains ShellError, ParseError and error handling conveniences - nu-textview, which is the textview plugin extracted into a crate One of the major consequences of this refactor is that it's no longer possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so a lot of types became more concrete (Value became a concrete type instead of Spanned<Value>, for example). This also turned a number of inherent methods in the main nu crate into plain functions (impl Value {} became a bunch of functions in the `value` namespace in `crate::data::value`).
2019-11-26 02:30:48 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"proc-macro2",
"quote",
"syn",
Extract core stuff into own crates This commit extracts five new crates: - nu-source, which contains the core source-code handling logic in Nu, including Text, Span, and also the pretty.rs-based debug logic - nu-parser, which is the parser and expander logic - nu-protocol, which is the bulk of the types and basic conveniences used by plugins - nu-errors, which contains ShellError, ParseError and error handling conveniences - nu-textview, which is the textview plugin extracted into a crate One of the major consequences of this refactor is that it's no longer possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so a lot of types became more concrete (Value became a concrete type instead of Spanned<Value>, for example). This also turned a number of inherent methods in the main nu crate into plain functions (impl Value {} became a bunch of functions in the `value` namespace in `crate::data::value`).
2019-11-26 02:30:48 +00:00
]
Pipe external to internal Each line is a string object
2019-05-24 18:48:33 +00:00
[[package]]
name = "iovec"
Fix #811 (#813)
2019-10-13 04:53:58 +00:00
version = "0.1.4"
Pipe external to internal Each line is a string object
2019-05-24 18:48:33 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "b2b3ea6ff95e175473f8ffe6a7eb7c00d054240321b84c57051175fe3c1e075e"
Pipe external to internal Each line is a string object
2019-05-24 18:48:33 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"libc",
Pipe external to internal Each line is a string object
2019-05-24 18:48:33 +00:00
]
Update futures-preview to 0.3.0-alpha.18
2019-08-29 13:42:49 +00:00
[[package]]
name = "isahc"
Merge master
2019-11-16 17:17:05 +00:00
version = "0.7.6"
Update futures-preview to 0.3.0-alpha.18
2019-08-29 13:42:49 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "17b77027f12e53ae59a379f7074259d32eb10867e6183388020e922832d9c3fb"
Update futures-preview to 0.3.0-alpha.18
2019-08-29 13:42:49 +00:00
dependencies = [
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"bytes 0.4.12",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"crossbeam-channel 0.3.9",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"crossbeam-utils 0.6.6",
"curl",
"curl-sys",
"futures-io-preview",
"futures-util-preview",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"http 0.1.21",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"lazy_static 1.4.0",
"log",
"slab",
"sluice",
Update futures-preview to 0.3.0-alpha.18
2019-08-29 13:42:49 +00:00
]
Add tree sink
2019-06-07 07:50:26 +00:00
[[package]]
name = "isatty"
version = "0.1.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "e31a8281fc93ec9693494da65fbf28c0c2aa60a2eaec25dc58e2f31952e95edc"
Add tree sink
2019-06-07 07:50:26 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"cfg-if",
"libc",
"redox_syscall",
"winapi 0.3.8",
Add tree sink
2019-06-07 07:50:26 +00:00
]
Better errors and more fleshed out semantics
2019-05-30 04:19:46 +00:00
[[package]]
name = "itertools"
version = "0.7.11"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "0d47946d458e94a1b7bcabbf6521ea7c037062c81f534615abcad76e84d4970d"
Better errors and more fleshed out semantics
2019-05-30 04:19:46 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"either",
Better errors and more fleshed out semantics
2019-05-30 04:19:46 +00:00
]
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "itertools"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
version = "0.8.2"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "f56a2d0bc861f9165be4eb3442afd3c236d8a98afd426f65d92324ae1091a484"
objectshell initial commit
2019-05-10 16:59:12 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"either",
objectshell initial commit
2019-05-10 16:59:12 +00:00
]
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
[[package]]
name = "itertools"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "284f18f85651fe11e8a991b2adb42cb078325c996ed026d994719efcfca1d54b"
dependencies = [
"either",
]
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "itoa"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.4.5"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "b8b7a7c0c47db5545ed3fef7468ee7bb5b74691498139e4b3f6a20685dc6dd8e"
objectshell initial commit
2019-05-10 16:59:12 +00:00
Add basic 'did you mean' support
2019-09-13 03:44:21 +00:00
[[package]]
name = "jobserver"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.1.21"
Add basic 'did you mean' support
2019-09-13 03:44:21 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "5c71313ebb9439f74b00d9d2dcec36440beaf57a6aa0623068441dd7cd81a7f2"
Add basic 'did you mean' support
2019-09-13 03:44:21 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"libc",
Add basic 'did you mean' support
2019-09-13 03:44:21 +00:00
]
Add some logic for more binary formats
2019-07-05 07:53:09 +00:00
[[package]]
name = "jpeg-decoder"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
version = "0.1.18"
Add some logic for more binary formats
2019-07-05 07:53:09 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
checksum = "0256f0aec7352539102a9efbcb75543227b7ab1117e0f95450023af730128451"
Add some logic for more binary formats
2019-07-05 07:53:09 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"byteorder",
Add some logic for more binary formats
2019-07-05 07:53:09 +00:00
]
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
[[package]]
name = "js-sys"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.3.35"
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "7889c7c36282151f6bf465be4700359318aef36baa951462382eae49e9577cf9"
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"wasm-bindgen",
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
]
Restructure and make commands uniform
2019-05-22 07:12:03 +00:00
[[package]]
name = "kernel32-sys"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "7507624b29483431c0ba2d82aece8ca6cdba9382bff4ddd0f7490560c056098d"
Restructure and make commands uniform
2019-05-22 07:12:03 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"winapi 0.2.8",
"winapi-build",
Restructure and make commands uniform
2019-05-22 07:12:03 +00:00
]
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
[[package]]
name = "kv-log-macro"
version = "1.0.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8c54d9f465d530a752e6ebdc217e081a7a614b48cb200f6f0aee21ba6bc9aabb"
dependencies = [
"log",
]
Better errors and more fleshed out semantics
2019-05-30 04:19:46 +00:00
[[package]]
name = "language-reporting"
Update cargo.lock
2019-10-16 02:09:47 +00:00
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "4e6a84e1e6cccd818617d299427ad1519f127af2738b1d3a581835ef56ae298b"
Better errors and more fleshed out semantics
2019-05-30 04:19:46 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"derive-new",
"itertools 0.7.11",
"log",
"render-tree",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"serde 1.0.104",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"serde_derive",
"termcolor",
Better errors and more fleshed out semantics
2019-05-30 04:19:46 +00:00
]
Lots of misc improvements
2019-06-03 07:41:28 +00:00
[[package]]
name = "lazy_static"
version = "0.2.11"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "76f033c7ad61445c5b347c7382dd1237847eb1bce590fe50365dcb33d546be73"
Lots of misc improvements
2019-06-03 07:41:28 +00:00
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "lazy_static"
Fix #811 (#813)
2019-10-13 04:53:58 +00:00
version = "1.4.0"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "e2abad23fbc42b3700f2f279844dc832adb2b2eb069b2df918f455c4e18cc646"
objectshell initial commit
2019-05-10 16:59:12 +00:00
Bat
2019-05-18 01:24:13 +00:00
[[package]]
name = "lazycell"
version = "1.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "b294d6fa9ee409a054354afc4352b0b9ef7ca222c69b8812cbea9e7d2bf3783f"
Bat
2019-05-18 01:24:13 +00:00
WIP
2019-06-22 03:43:37 +00:00
[[package]]
name = "lexical-core"
Fix #811 (#813)
2019-10-13 04:53:58 +00:00
version = "0.4.6"
WIP
2019-06-22 03:43:37 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "2304bccb228c4b020f3a4835d247df0a02a7c4686098d4167762cfbbe4c5cb14"
WIP
2019-06-22 03:43:37 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"arrayvec 0.4.12",
"cfg-if",
"rustc_version",
"ryu",
"static_assertions",
WIP
2019-06-22 03:43:37 +00:00
]
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "libc"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
version = "0.2.66"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "d515b1f41455adea1313a4a2ac8a8a477634fbae63cc6100e3aebb207ce61558"
objectshell initial commit
2019-05-10 16:59:12 +00:00
Add git branch to prompt
2019-06-01 21:11:28 +00:00
[[package]]
name = "libgit2-sys"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
version = "0.10.0"
Add git branch to prompt
2019-06-01 21:11:28 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
checksum = "d9ec6bca50549d34a392611dde775123086acbd994e3fff64954777ce2dc2e51"
Add git branch to prompt
2019-06-01 21:11:28 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"cc",
"libc",
"libz-sys",
"pkg-config",
Add git branch to prompt
2019-06-01 21:11:28 +00:00
]
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
[[package]]
name = "libnghttp2-sys"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "02254d44f4435dd79e695f2c2b83cd06a47919adea30216ceaf0c57ca0a72463"
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"cc",
"libc",
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
]
Add SQLite support
2019-08-27 21:45:18 +00:00
[[package]]
name = "libsqlite3-sys"
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
version = "0.17.1"
Add SQLite support
2019-08-27 21:45:18 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
checksum = "266eb8c361198e8d1f682bc974e5d9e2ae90049fb1943890904d11dad7d4a77d"
Add SQLite support
2019-08-27 21:45:18 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"cc",
"pkg-config",
"vcpkg",
Add SQLite support
2019-08-27 21:45:18 +00:00
]
Add git branch to prompt
2019-06-01 21:11:28 +00:00
[[package]]
name = "libz-sys"
version = "1.0.25"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "2eb5e43362e38e2bca2fd5f5134c4d4564a23a5c28e9b95411652021a8675ebe"
Add git branch to prompt
2019-06-01 21:11:28 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"cc",
"libc",
"pkg-config",
"vcpkg",
Add git branch to prompt
2019-06-01 21:11:28 +00:00
]
Bat
2019-05-18 01:24:13 +00:00
[[package]]
name = "line-wrap"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "f30344350a2a51da54c1d53be93fade8a237e545dbcc4bdbe635413f2117cab9"
Bat
2019-05-18 01:24:13 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"safemem",
Bat
2019-05-18 01:24:13 +00:00
]
Lots of misc improvements
2019-06-03 07:41:28 +00:00
[[package]]
name = "linked-hash-map"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "6d262045c5b87c0861b3f004610afd0e2c851e2908d08b6c870cbb9d5f494ecd"
Lots of misc improvements
2019-06-03 07:41:28 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"serde 0.8.23",
"serde_test",
Lots of misc improvements
2019-06-03 07:41:28 +00:00
]
Bat
2019-05-18 01:24:13 +00:00
[[package]]
name = "linked-hash-map"
version = "0.5.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "ae91b68aebc4ddb91978b11a1b02ddd8602a05ec19002801c5666000e05e0f83"
Bat
2019-05-18 01:24:13 +00:00
Last unwraps (#1160) * Work through most of the last unwraps * Finish removing unwraps
2020-01-04 06:44:17 +00:00
[[package]]
name = "lock_api"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.3.3"
Last unwraps (#1160) * Work through most of the last unwraps * Finish removing unwraps
2020-01-04 06:44:17 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "79b2de95ecb4691949fea4716ca53cdbcfccb2c612e19644a8bad05edcf9f47b"
Last unwraps (#1160) * Work through most of the last unwraps * Finish removing unwraps
2020-01-04 06:44:17 +00:00
dependencies = [
"scopeguard",
]
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "log"
bump deps
2019-07-29 07:46:24 +00:00
version = "0.4.8"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "14b6052be84e6b71ab17edffc2eeabf5c2c3ae1fdb464aae35ac50c67a44e1f7"
objectshell initial commit
2019-05-10 16:59:12 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"cfg-if",
objectshell initial commit
2019-05-10 16:59:12 +00:00
]
Add SQLite support
2019-08-27 21:45:18 +00:00
[[package]]
name = "lru-cache"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "31e24f1ad8321ca0e8a1e0ac13f23cb668e6f5466c2c57319f6a5cf1cc8e3b1c"
Add SQLite support
2019-08-27 21:45:18 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"linked-hash-map 0.5.2",
Add SQLite support
2019-08-27 21:45:18 +00:00
]
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
[[package]]
name = "macaddr"
Merge master
2019-11-16 17:17:05 +00:00
version = "0.1.2"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "bee538cb1031f87f970ba28f0e5ebfcdaf63ed1a000a4176b4117537c33d19fb"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
add some battery stats
2019-08-11 03:01:09 +00:00
[[package]]
name = "mach"
version = "0.2.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "86dd2487cdfea56def77b88438a2c915fb45113c5319bfe7e14306ca4cd0b0e1"
add some battery stats
2019-08-11 03:01:09 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"libc",
add some battery stats
2019-08-11 03:01:09 +00:00
]
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
[[package]]
name = "mach"
version = "0.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "b823e83b2affd8f40a9ee8c29dbc56404c1e34cd2710921f2801e2cf29527afa"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"libc",
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
]
Add clipboard support
2019-06-07 16:30:50 +00:00
[[package]]
name = "malloc_buf"
version = "0.0.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "62bb907fe88d54d8d9ce32a3cceab4218ed2f6b7d35617cafe9adf84e43919cb"
Add clipboard support
2019-06-07 16:30:50 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"libc",
Add clipboard support
2019-06-07 16:30:50 +00:00
]
Add git branch to prompt
2019-06-01 21:11:28 +00:00
[[package]]
name = "matches"
version = "0.1.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "7ffc5c5338469d4d3ea17d269fa8ea3512ad247247c30bd2df69e68309ed0a08"
Merge master
2019-11-16 17:17:05 +00:00
Rebase on master
2019-08-25 13:57:47 +00:00
[[package]]
name = "md5"
Update bson to 0.14
2019-08-31 14:22:45 +00:00
version = "0.6.1"
Rebase on master
2019-08-25 13:57:47 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "7e6bcd6433cff03a4bfc3d9834d504467db1f1cf6d0ea765d37d330249ed629d"
Rebase on master
2019-08-25 13:57:47 +00:00
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "memchr"
bump deps
2019-07-29 07:46:24 +00:00
version = "2.2.1"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "88579771288728879b57485cc7d6b07d648c9f0141eb955f8ab7f9d45394468e"
objectshell initial commit
2019-05-10 16:59:12 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"libc",
objectshell initial commit
2019-05-10 16:59:12 +00:00
]
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
[[package]]
name = "memoffset"
Merge master
2019-11-16 17:17:05 +00:00
version = "0.5.3"
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "75189eb85871ea5c2e2c15abbdd541185f63b408415e5051f5cac122d8c774b9"
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"rustc_version",
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
]
Make a `calc` command (#1280)
2020-01-29 13:34:36 +00:00
[[package]]
name = "meval"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f79496a5651c8d57cd033c5add8ca7ee4e3d5f7587a4777484640d9cb60392d9"
dependencies = [
"fnv",
"nom 1.2.4",
]
Add opening urls
2019-06-08 18:09:17 +00:00
[[package]]
name = "mime"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.3.16"
Add opening urls
2019-06-08 18:09:17 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "2a60c7ce501c71e03a9c9c0d35b861413ae925bd979cc7a4e30d060069aaac8d"
Add opening urls
2019-06-08 18:09:17 +00:00
[[package]]
name = "mime_guess"
Pin semver breaking dep
2019-08-08 17:33:19 +00:00
version = "2.0.1"
Add opening urls
2019-06-08 18:09:17 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "1a0ed03949aef72dbdf3116a383d7b38b4768e6f960528cd6a6044aa9ed68599"
Add opening urls
2019-06-08 18:09:17 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"mime",
"unicase",
Bat
2019-05-18 01:24:13 +00:00
]
[[package]]
name = "miniz_oxide"
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
version = "0.3.6"
Bat
2019-05-18 01:24:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
checksum = "aa679ff6578b1cddee93d7e82e263b94a575e0bfced07284eb0c037c1d2416a5"
Bat
2019-05-18 01:24:13 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"adler32",
Bat
2019-05-18 01:24:13 +00:00
]
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
[[package]]
name = "mio"
version = "0.6.21"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "302dec22bcf6bae6dfb69c647187f4b4d0fb6f535521f7bc022430ce8e12008f"
dependencies = [
"cfg-if",
"fuchsia-zircon",
"fuchsia-zircon-sys",
"iovec",
"kernel32-sys",
"libc",
"log",
"miow",
"net2",
"slab",
"winapi 0.2.8",
]
[[package]]
name = "mio-uds"
version = "0.6.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "966257a94e196b11bb43aca423754d87429960a768de9414f3691d6957abf125"
dependencies = [
"iovec",
"libc",
"mio",
]
[[package]]
name = "miow"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8c1f2f3b1cf331de6896aabf6e9d55dca90356cc9960cca7eaaf408a355ae919"
dependencies = [
"kernel32-sys",
"net2",
"winapi 0.2.8",
"ws2_32-sys",
]
Add basic 'did you mean' support
2019-09-13 03:44:21 +00:00
[[package]]
name = "natural"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "fd659d7d6b4554da2c0e7a486d5952b24dfce0e0bac88ab53b270f4efe1010a6"
Add basic 'did you mean' support
2019-09-13 03:44:21 +00:00
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
[[package]]
name = "natural"
version = "0.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "65e6b44f8ddc659cde3555e0140d3441ad26cb03a1410774af1f9a19097c1867"
dependencies = [
"rust-stemmers",
]
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
[[package]]
name = "neso"
version = "0.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "6b3c31defbcb081163db18437fd88c2a267cb3e26f7bd5e4b186e4b1b38fe8c8"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"bincode",
"cfg-if",
"log",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"serde 1.0.104",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"serde_derive",
"wasm-bindgen",
Add opening urls
2019-06-08 18:09:17 +00:00
]
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
[[package]]
name = "net2"
version = "0.2.33"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "42550d9fb7b6684a6d404d9fa7250c2eb2646df731d1c06afc06dcee9e1bcf88"
dependencies = [
"cfg-if",
"libc",
"winapi 0.3.8",
]
Handle Ctrl-C gracefully
2019-06-07 00:31:22 +00:00
[[package]]
name = "nix"
Some function stuff It's not done, but honestly it's getting too tedious. I will need to rethink how I'm doing it.
2019-06-10 19:13:29 +00:00
version = "0.14.1"
Handle Ctrl-C gracefully
2019-06-07 00:31:22 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "6c722bee1037d430d0f8e687bbdbf222f27cc6e4e68d5caf630857bb2b6dbdce"
Handle Ctrl-C gracefully
2019-06-07 00:31:22 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"bitflags",
"cc",
"cfg-if",
"libc",
"void",
Handle Ctrl-C gracefully
2019-06-07 00:31:22 +00:00
]
Update to heim v0.0.7.
2019-08-28 15:53:59 +00:00
[[package]]
name = "nix"
version = "0.15.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "3b2e0b4f3320ed72aaedb9a5ac838690a8047c7b275da22711fddff4f8a14229"
Update to heim v0.0.7.
2019-08-28 15:53:59 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"bitflags",
"cc",
"cfg-if",
"libc",
"void",
Update to heim v0.0.7.
2019-08-28 15:53:59 +00:00
]
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
[[package]]
name = "nix"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
version = "0.16.1"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
checksum = "dd0eaf8df8bab402257e0a5c17a254e4cc1f72a93588a1ddfb5d356c801aa7cb"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
dependencies = [
"bitflags",
"cc",
"cfg-if",
"libc",
"void",
]
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
[[package]]
name = "nix"
version = "0.17.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "50e4785f2c3b7589a0d0c1dd60285e1188adac4006e8abd6dd578e1567027363"
dependencies = [
"bitflags",
"cc",
"cfg-if",
"libc",
"void",
]
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "nodrop"
Fix #811 (#813)
2019-10-13 04:53:58 +00:00
version = "0.1.14"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "72ef4a56884ca558e5ddb05a1d1e7e1bfd9a68d9ed024c21704cc98872dae1bb"
objectshell initial commit
2019-05-10 16:59:12 +00:00
Make a `calc` command (#1280)
2020-01-29 13:34:36 +00:00
[[package]]
name = "nom"
version = "1.2.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a5b8c256fd9471521bcb84c3cdba98921497f1a331cbc15b8030fc63b82050ce"
Add tree sink
2019-06-07 07:50:26 +00:00
[[package]]
name = "nom"
version = "4.2.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "2ad2a91a8e869eeb30b9cb3119ae87773a8f4ae617f41b1eb9c154b2905f7bd6"
Add tree sink
2019-06-07 07:50:26 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"memchr",
"version_check 0.1.5",
Add tree sink
2019-06-07 07:50:26 +00:00
]
Paths
2019-06-13 05:33:38 +00:00
[[package]]
WIP
2019-06-22 03:43:37 +00:00
name = "nom"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
version = "5.1.0"
WIP
2019-06-22 03:43:37 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
checksum = "c433f4d505fe6ce7ff78523d2fa13a0b9f2690e181fc26168bcbe5ccc5d14e07"
Paths
2019-06-13 05:33:38 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"lexical-core",
"memchr",
"version_check 0.1.5",
Paths
2019-06-13 05:33:38 +00:00
]
Overhaul the expansion system The main thrust of this (very large) commit is an overhaul of the expansion system. The parsing pipeline is: - Lightly parse the source file for atoms, basic delimiters and pipeline structure into a token tree - Expand the token tree into a HIR (high-level intermediate representation) based upon the baseline syntax rules for expressions and the syntactic shape of commands. Somewhat non-traditionally, nu doesn't have an AST at all. It goes directly from the token tree, which doesn't represent many important distinctions (like the difference between `hello` and `5KB`) directly into a high-level representation that doesn't have a direct correspondence to the source code. At a high level, nu commands work like macros, in the sense that the syntactic shape of the invocation of a command depends on the definition of a command. However, commands do not have the ability to perform unrestricted expansions of the token tree. Instead, they describe their arguments in terms of syntactic shapes, and the expander expands the token tree into HIR based upon that definition. For example, the `where` command says that it takes a block as its first required argument, and the description of the block syntactic shape expands the syntax `cpu > 10` into HIR that represents `{ $it.cpu > 10 }`. This commit overhauls that system so that the syntactic shapes are described in terms of a few new traits (`ExpandSyntax` and `ExpandExpression` are the primary ones) that are more composable than the previous system. The first big win of this new system is the addition of the `ColumnPath` shape, which looks like `cpu."max ghz"` or `package.version`. Previously, while a variable path could look like `$it.cpu."max ghz"`, the tail of a variable path could not be easily reused in other contexts. Now, that tail is its own syntactic shape, and it can be used as part of a command's signature. This cleans up commands like `inc`, `add` and `edit` as well as shorthand blocks, which can now look like `| where cpu."max ghz" > 10`
2019-09-17 22:26:27 +00:00
[[package]]
name = "nom-tracable"
Bump dep versions
2019-11-10 17:48:49 +00:00
version = "0.4.1"
Overhaul the expansion system The main thrust of this (very large) commit is an overhaul of the expansion system. The parsing pipeline is: - Lightly parse the source file for atoms, basic delimiters and pipeline structure into a token tree - Expand the token tree into a HIR (high-level intermediate representation) based upon the baseline syntax rules for expressions and the syntactic shape of commands. Somewhat non-traditionally, nu doesn't have an AST at all. It goes directly from the token tree, which doesn't represent many important distinctions (like the difference between `hello` and `5KB`) directly into a high-level representation that doesn't have a direct correspondence to the source code. At a high level, nu commands work like macros, in the sense that the syntactic shape of the invocation of a command depends on the definition of a command. However, commands do not have the ability to perform unrestricted expansions of the token tree. Instead, they describe their arguments in terms of syntactic shapes, and the expander expands the token tree into HIR based upon that definition. For example, the `where` command says that it takes a block as its first required argument, and the description of the block syntactic shape expands the syntax `cpu > 10` into HIR that represents `{ $it.cpu > 10 }`. This commit overhauls that system so that the syntactic shapes are described in terms of a few new traits (`ExpandSyntax` and `ExpandExpression` are the primary ones) that are more composable than the previous system. The first big win of this new system is the addition of the `ColumnPath` shape, which looks like `cpu."max ghz"` or `package.version`. Previously, while a variable path could look like `$it.cpu."max ghz"`, the tail of a variable path could not be easily reused in other contexts. Now, that tail is its own syntactic shape, and it can be used as part of a command's signature. This cleans up commands like `inc`, `add` and `edit` as well as shorthand blocks, which can now look like `| where cpu."max ghz" > 10`
2019-09-17 22:26:27 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "4e9af1ee3bf4c9b842a720c53c0e7abb1b56a207e0b9bdbe7ff684b4cf630da1"
Overhaul the expansion system The main thrust of this (very large) commit is an overhaul of the expansion system. The parsing pipeline is: - Lightly parse the source file for atoms, basic delimiters and pipeline structure into a token tree - Expand the token tree into a HIR (high-level intermediate representation) based upon the baseline syntax rules for expressions and the syntactic shape of commands. Somewhat non-traditionally, nu doesn't have an AST at all. It goes directly from the token tree, which doesn't represent many important distinctions (like the difference between `hello` and `5KB`) directly into a high-level representation that doesn't have a direct correspondence to the source code. At a high level, nu commands work like macros, in the sense that the syntactic shape of the invocation of a command depends on the definition of a command. However, commands do not have the ability to perform unrestricted expansions of the token tree. Instead, they describe their arguments in terms of syntactic shapes, and the expander expands the token tree into HIR based upon that definition. For example, the `where` command says that it takes a block as its first required argument, and the description of the block syntactic shape expands the syntax `cpu > 10` into HIR that represents `{ $it.cpu > 10 }`. This commit overhauls that system so that the syntactic shapes are described in terms of a few new traits (`ExpandSyntax` and `ExpandExpression` are the primary ones) that are more composable than the previous system. The first big win of this new system is the addition of the `ColumnPath` shape, which looks like `cpu."max ghz"` or `package.version`. Previously, while a variable path could look like `$it.cpu."max ghz"`, the tail of a variable path could not be easily reused in other contexts. Now, that tail is its own syntactic shape, and it can be used as part of a command's signature. This cleans up commands like `inc`, `add` and `edit` as well as shorthand blocks, which can now look like `| where cpu."max ghz" > 10`
2019-09-17 22:26:27 +00:00
dependencies = [
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"nom 5.1.0",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"nom-tracable-macros",
"nom_locate",
Overhaul the expansion system The main thrust of this (very large) commit is an overhaul of the expansion system. The parsing pipeline is: - Lightly parse the source file for atoms, basic delimiters and pipeline structure into a token tree - Expand the token tree into a HIR (high-level intermediate representation) based upon the baseline syntax rules for expressions and the syntactic shape of commands. Somewhat non-traditionally, nu doesn't have an AST at all. It goes directly from the token tree, which doesn't represent many important distinctions (like the difference between `hello` and `5KB`) directly into a high-level representation that doesn't have a direct correspondence to the source code. At a high level, nu commands work like macros, in the sense that the syntactic shape of the invocation of a command depends on the definition of a command. However, commands do not have the ability to perform unrestricted expansions of the token tree. Instead, they describe their arguments in terms of syntactic shapes, and the expander expands the token tree into HIR based upon that definition. For example, the `where` command says that it takes a block as its first required argument, and the description of the block syntactic shape expands the syntax `cpu > 10` into HIR that represents `{ $it.cpu > 10 }`. This commit overhauls that system so that the syntactic shapes are described in terms of a few new traits (`ExpandSyntax` and `ExpandExpression` are the primary ones) that are more composable than the previous system. The first big win of this new system is the addition of the `ColumnPath` shape, which looks like `cpu."max ghz"` or `package.version`. Previously, while a variable path could look like `$it.cpu."max ghz"`, the tail of a variable path could not be easily reused in other contexts. Now, that tail is its own syntactic shape, and it can be used as part of a command's signature. This cleans up commands like `inc`, `add` and `edit` as well as shorthand blocks, which can now look like `| where cpu."max ghz" > 10`
2019-09-17 22:26:27 +00:00
]
[[package]]
name = "nom-tracable-macros"
Merge master
2019-11-16 17:17:05 +00:00
version = "0.4.1"
Overhaul the expansion system The main thrust of this (very large) commit is an overhaul of the expansion system. The parsing pipeline is: - Lightly parse the source file for atoms, basic delimiters and pipeline structure into a token tree - Expand the token tree into a HIR (high-level intermediate representation) based upon the baseline syntax rules for expressions and the syntactic shape of commands. Somewhat non-traditionally, nu doesn't have an AST at all. It goes directly from the token tree, which doesn't represent many important distinctions (like the difference between `hello` and `5KB`) directly into a high-level representation that doesn't have a direct correspondence to the source code. At a high level, nu commands work like macros, in the sense that the syntactic shape of the invocation of a command depends on the definition of a command. However, commands do not have the ability to perform unrestricted expansions of the token tree. Instead, they describe their arguments in terms of syntactic shapes, and the expander expands the token tree into HIR based upon that definition. For example, the `where` command says that it takes a block as its first required argument, and the description of the block syntactic shape expands the syntax `cpu > 10` into HIR that represents `{ $it.cpu > 10 }`. This commit overhauls that system so that the syntactic shapes are described in terms of a few new traits (`ExpandSyntax` and `ExpandExpression` are the primary ones) that are more composable than the previous system. The first big win of this new system is the addition of the `ColumnPath` shape, which looks like `cpu."max ghz"` or `package.version`. Previously, while a variable path could look like `$it.cpu."max ghz"`, the tail of a variable path could not be easily reused in other contexts. Now, that tail is its own syntactic shape, and it can be used as part of a command's signature. This cleans up commands like `inc`, `add` and `edit` as well as shorthand blocks, which can now look like `| where cpu."max ghz" > 10`
2019-09-17 22:26:27 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "8c16e5f9f228073fd36e4c9e65b12d763d9a1bda73b8400f3aa67d7971c8dffb"
Overhaul the expansion system The main thrust of this (very large) commit is an overhaul of the expansion system. The parsing pipeline is: - Lightly parse the source file for atoms, basic delimiters and pipeline structure into a token tree - Expand the token tree into a HIR (high-level intermediate representation) based upon the baseline syntax rules for expressions and the syntactic shape of commands. Somewhat non-traditionally, nu doesn't have an AST at all. It goes directly from the token tree, which doesn't represent many important distinctions (like the difference between `hello` and `5KB`) directly into a high-level representation that doesn't have a direct correspondence to the source code. At a high level, nu commands work like macros, in the sense that the syntactic shape of the invocation of a command depends on the definition of a command. However, commands do not have the ability to perform unrestricted expansions of the token tree. Instead, they describe their arguments in terms of syntactic shapes, and the expander expands the token tree into HIR based upon that definition. For example, the `where` command says that it takes a block as its first required argument, and the description of the block syntactic shape expands the syntax `cpu > 10` into HIR that represents `{ $it.cpu > 10 }`. This commit overhauls that system so that the syntactic shapes are described in terms of a few new traits (`ExpandSyntax` and `ExpandExpression` are the primary ones) that are more composable than the previous system. The first big win of this new system is the addition of the `ColumnPath` shape, which looks like `cpu."max ghz"` or `package.version`. Previously, while a variable path could look like `$it.cpu."max ghz"`, the tail of a variable path could not be easily reused in other contexts. Now, that tail is its own syntactic shape, and it can be used as part of a command's signature. This cleans up commands like `inc`, `add` and `edit` as well as shorthand blocks, which can now look like `| where cpu."max ghz" > 10`
2019-09-17 22:26:27 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"quote",
"syn",
Overhaul the expansion system The main thrust of this (very large) commit is an overhaul of the expansion system. The parsing pipeline is: - Lightly parse the source file for atoms, basic delimiters and pipeline structure into a token tree - Expand the token tree into a HIR (high-level intermediate representation) based upon the baseline syntax rules for expressions and the syntactic shape of commands. Somewhat non-traditionally, nu doesn't have an AST at all. It goes directly from the token tree, which doesn't represent many important distinctions (like the difference between `hello` and `5KB`) directly into a high-level representation that doesn't have a direct correspondence to the source code. At a high level, nu commands work like macros, in the sense that the syntactic shape of the invocation of a command depends on the definition of a command. However, commands do not have the ability to perform unrestricted expansions of the token tree. Instead, they describe their arguments in terms of syntactic shapes, and the expander expands the token tree into HIR based upon that definition. For example, the `where` command says that it takes a block as its first required argument, and the description of the block syntactic shape expands the syntax `cpu > 10` into HIR that represents `{ $it.cpu > 10 }`. This commit overhauls that system so that the syntactic shapes are described in terms of a few new traits (`ExpandSyntax` and `ExpandExpression` are the primary ones) that are more composable than the previous system. The first big win of this new system is the addition of the `ColumnPath` shape, which looks like `cpu."max ghz"` or `package.version`. Previously, while a variable path could look like `$it.cpu."max ghz"`, the tail of a variable path could not be easily reused in other contexts. Now, that tail is its own syntactic shape, and it can be used as part of a command's signature. This cleans up commands like `inc`, `add` and `edit` as well as shorthand blocks, which can now look like `| where cpu."max ghz" > 10`
2019-09-17 22:26:27 +00:00
]
Simple parsing
2019-05-11 04:45:57 +00:00
[[package]]
Revert "Revert "Migrate most uses of the Span concept to Tag"" This reverts commit bee7c5639cc78d65e6656518627a86009a522500.
2019-09-14 16:30:24 +00:00
name = "nom_locate"
version = "1.0.0"
Cleanup for upcoming release
2019-07-16 19:10:25 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "f932834fd8e391fc7710e2ba17e8f9f8645d846b55aa63207e17e110a1e1ce35"
Simple parsing
2019-05-11 04:45:57 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"bytecount",
"memchr",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"nom 5.1.0",
Simple parsing
2019-05-11 04:45:57 +00:00
]
Pin semver breaking dep
2019-08-08 17:33:19 +00:00
[[package]]
name = "ntapi"
version = "0.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "f26e041cd983acbc087e30fcba770380cfa352d0e392e175b2344ebaf7ea0602"
Pin semver breaking dep
2019-08-08 17:33:19 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"winapi 0.3.8",
Pin semver breaking dep
2019-08-08 17:33:19 +00:00
]
Update name
2019-05-16 23:39:58 +00:00
[[package]]
name = "nu"
Bump to 0.11.0 (#1474)
2020-03-10 17:34:19 +00:00
version = "0.11.0"
Move most of the root package into a subcrate. (#1445) This improves incremental build time when working on what was previously the root package. For example, previously all plugins would be rebuilt with a change to `src/commands/classified/external.rs`, but now only `nu-cli` will have to be rebuilt (and anything that depends on it).
2020-03-04 18:58:20 +00:00
dependencies = [
"clap",
"crossterm 0.16.0",
"ctrlc",
"dunce",
"futures 0.3.3",
"log",
"nu-build",
"nu-cli",
"nu-errors",
"nu-macros",
"nu-parser",
"nu-plugin",
"nu-protocol",
"nu-source",
"nu-test-support",
"nu-value-ext",
"nu_plugin_average",
"nu_plugin_binaryview",
"nu_plugin_fetch",
"nu_plugin_inc",
"nu_plugin_match",
"nu_plugin_post",
"nu_plugin_ps",
"nu_plugin_shuffle",
"nu_plugin_str",
"nu_plugin_sum",
"nu_plugin_sys",
"nu_plugin_textview",
"nu_plugin_tree",
"onig_sys",
"pretty_assertions",
"pretty_env_logger 0.4.0",
"semver",
"serde 1.0.104",
"syntect",
"toml 0.5.6",
"url",
]
[[package]]
name = "nu-build"
Bump to 0.11.0 (#1474)
2020-03-10 17:34:19 +00:00
version = "0.11.0"
Move most of the root package into a subcrate. (#1445) This improves incremental build time when working on what was previously the root package. For example, previously all plugins would be rebuilt with a change to `src/commands/classified/external.rs`, but now only `nu-cli` will have to be rebuilt (and anything that depends on it).
2020-03-04 18:58:20 +00:00
dependencies = [
"lazy_static 1.4.0",
"serde 1.0.104",
"serde_json",
"toml 0.5.6",
]
[[package]]
name = "nu-cli"
Bump to 0.11.0 (#1474)
2020-03-10 17:34:19 +00:00
version = "0.11.0"
Update name
2019-05-16 23:39:58 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"ansi_term 0.12.1",
"app_dirs",
"async-stream",
"base64 0.11.0",
"bigdecimal",
"bson",
"byte-unit",
Move to bytes/string hybrid codec (#1457) * WIP: move to bytes codec * Progress on adding collect helpers * Progress on adding collect helpers * Add in line splitting back to lines * Lines outputting line primitives * Close to ready? * Finish fixing lines * clippy fixes * fmt fixes * removed unused code * Cleanup a few bits * Cleanup a few bits * Cleanup a few more bits * Fix failing test with corrected test case
2020-03-06 16:06:39 +00:00
"bytes 0.5.4",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"calamine",
"cfg-if",
"chrono",
"clap",
Make feature options available downstream to nu-cli subcrate. (#1450)
2020-03-04 20:31:12 +00:00
"clipboard",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"csv",
"ctrlc",
"derive-new",
"dirs 2.0.2",
"dunce",
Add block size to du (#1341) * Add block size to du * Change blocks to physical size * Use path instead of strings for file/directory names * Why don't I just use paths instead of strings anyway? * shorten physical size and apparent size to physical and apparent resp.
2020-02-10 20:32:18 +00:00
"filesize",
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
"futures 0.3.3",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"futures-util",
"futures_codec",
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
"getset 0.1.0",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"git2",
"glob",
"hex 0.4.0",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"ichwh",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"indexmap",
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
"itertools 0.9.0",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"language-reporting",
"log",
Make a `calc` command (#1280)
2020-01-29 13:34:36 +00:00
"meval",
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
"natural 0.5.0",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"nom 5.1.0",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"nom-tracable",
"nom_locate",
Extract build.rs
2019-12-02 21:14:51 +00:00
"nu-build",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"nu-errors",
Add Range and start Signature support This commit contains two improvements: - Support for a Range syntax (and a corresponding Range value) - Work towards a signature syntax Implementing the Range syntax resulted in cleaning up how operators in the core syntax works. There are now two kinds of infix operators - tight operators (`.` and `..`) - loose operators Tight operators may not be interspersed (`$it.left..$it.right` is a syntax error). Loose operators require whitespace on both sides of the operator, and can be arbitrarily interspersed. Precedence is left to right in the core syntax. Note that delimited syntax (like `( ... )` or `[ ... ]`) is a single token node in the core syntax. A single token node can be parsed from beginning to end in a context-free manner. The rule for `.` is `<token node>.<member>`. The rule for `..` is `<token node>..<token node>`. Loose operators all have the same syntactic rule: `<token node><space><loose op><space><token node>`. The second aspect of this pull request is the beginning of support for a signature syntax. Before implementing signatures, a necessary prerequisite is for the core syntax to support multi-line programs. That work establishes a few things: - `;` and newlines are handled in the core grammar, and both count as "separators" - line comments begin with `#` and continue until the end of the line In this commit, multi-token productions in the core grammar can use separators interchangably with spaces. However, I think we will ultimately want a different rule preventing separators from occurring before an infix operator, so that the end of a line is always unambiguous. This would avoid gratuitous differences between modules and repl usage. We already effectively have this rule, because otherwise `x<newline> | y` would be a single pipeline, but of course that wouldn't work.
2019-12-04 21:14:52 +00:00
"nu-macros",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"nu-parser",
Nu plugins now depend on nu-plugin crate.
2019-12-27 13:30:14 +00:00
"nu-plugin",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"nu-protocol",
"nu-source",
Rename test-support to nu-test-support
2019-12-17 18:41:47 +00:00
"nu-test-support",
Move the remainder of the plugins to crates
2019-12-09 18:39:51 +00:00
"nu-value-ext",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"num-bigint",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"num-traits 0.2.11",
Last unwraps (#1160) * Work through most of the last unwraps * Finish removing unwraps
2020-01-04 06:44:17 +00:00
"parking_lot",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"pin-utils",
"pretty-hex",
"pretty_assertions",
Switch stdin redirect to manual. Add test (#1367)
2020-02-10 06:55:07 +00:00
"pretty_env_logger 0.4.0",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"prettytable-rs",
"ptree",
"query_interface",
"regex",
"roxmltree",
"rusqlite",
"rustyline",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"serde 1.0.104",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"serde-hjson 0.9.1",
"serde_bytes",
"serde_ini",
"serde_json",
"serde_urlencoded",
"serde_yaml",
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
"shellexpand 2.0.0",
Make feature options available downstream to nu-cli subcrate. (#1450)
2020-03-04 20:31:12 +00:00
"starship",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"strip-ansi-escapes",
"tempfile",
"term",
"termcolor",
"textwrap",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"toml 0.5.6",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"trash",
"typetag",
"umask",
"unicode-xid",
A few ls improvements. New welcome message (#1195)
2020-01-11 20:49:20 +00:00
"users",
Improve shelling out (#1273) Improvements to shelling out
2020-01-23 19:24:31 +00:00
"which",
Extract nu_source into a crate This commit extracts Tag, Span, Text, as well as source-related debug facilities into a new crate called nu_source. This change is much bigger than one might have expected because the previous code relied heavily on implementing inherent methods on `Tagged<T>` and `Spanned<T>`, which is no longer possible. As a result, this change creates more concrete types instead of using `Tagged<T>`. One notable example: Tagged<Value> became Value, and Value became UntaggedValue. This change clarifies the intent of the code in many places, but it does make it a big change.
2019-11-21 14:33:14 +00:00
]
Extract core stuff into own crates This commit extracts five new crates: - nu-source, which contains the core source-code handling logic in Nu, including Text, Span, and also the pretty.rs-based debug logic - nu-parser, which is the parser and expander logic - nu-protocol, which is the bulk of the types and basic conveniences used by plugins - nu-errors, which contains ShellError, ParseError and error handling conveniences - nu-textview, which is the textview plugin extracted into a crate One of the major consequences of this refactor is that it's no longer possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so a lot of types became more concrete (Value became a concrete type instead of Spanned<Value>, for example). This also turned a number of inherent methods in the main nu crate into plain functions (impl Value {} became a bunch of functions in the `value` namespace in `crate::data::value`).
2019-11-26 02:30:48 +00:00
[[package]]
name = "nu-errors"
Bump to 0.11.0 (#1474)
2020-03-10 17:34:19 +00:00
version = "0.11.0"
Extract core stuff into own crates This commit extracts five new crates: - nu-source, which contains the core source-code handling logic in Nu, including Text, Span, and also the pretty.rs-based debug logic - nu-parser, which is the parser and expander logic - nu-protocol, which is the bulk of the types and basic conveniences used by plugins - nu-errors, which contains ShellError, ParseError and error handling conveniences - nu-textview, which is the textview plugin extracted into a crate One of the major consequences of this refactor is that it's no longer possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so a lot of types became more concrete (Value became a concrete type instead of Spanned<Value>, for example). This also turned a number of inherent methods in the main nu crate into plain functions (impl Value {} became a bunch of functions in the `value` namespace in `crate::data::value`).
2019-11-26 02:30:48 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"ansi_term 0.12.1",
"bigdecimal",
"derive-new",
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
"getset 0.0.9",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"language-reporting",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"nom 5.1.0",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"nom_locate",
Extract build.rs
2019-12-02 21:14:51 +00:00
"nu-build",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"nu-source",
"num-bigint",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"num-traits 0.2.11",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"serde 1.0.104",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"serde_json",
"serde_yaml",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"toml 0.5.6",
Extract core stuff into own crates This commit extracts five new crates: - nu-source, which contains the core source-code handling logic in Nu, including Text, Span, and also the pretty.rs-based debug logic - nu-parser, which is the parser and expander logic - nu-protocol, which is the bulk of the types and basic conveniences used by plugins - nu-errors, which contains ShellError, ParseError and error handling conveniences - nu-textview, which is the textview plugin extracted into a crate One of the major consequences of this refactor is that it's no longer possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so a lot of types became more concrete (Value became a concrete type instead of Spanned<Value>, for example). This also turned a number of inherent methods in the main nu crate into plain functions (impl Value {} became a bunch of functions in the `value` namespace in `crate::data::value`).
2019-11-26 02:30:48 +00:00
]
Add Range and start Signature support This commit contains two improvements: - Support for a Range syntax (and a corresponding Range value) - Work towards a signature syntax Implementing the Range syntax resulted in cleaning up how operators in the core syntax works. There are now two kinds of infix operators - tight operators (`.` and `..`) - loose operators Tight operators may not be interspersed (`$it.left..$it.right` is a syntax error). Loose operators require whitespace on both sides of the operator, and can be arbitrarily interspersed. Precedence is left to right in the core syntax. Note that delimited syntax (like `( ... )` or `[ ... ]`) is a single token node in the core syntax. A single token node can be parsed from beginning to end in a context-free manner. The rule for `.` is `<token node>.<member>`. The rule for `..` is `<token node>..<token node>`. Loose operators all have the same syntactic rule: `<token node><space><loose op><space><token node>`. The second aspect of this pull request is the beginning of support for a signature syntax. Before implementing signatures, a necessary prerequisite is for the core syntax to support multi-line programs. That work establishes a few things: - `;` and newlines are handled in the core grammar, and both count as "separators" - line comments begin with `#` and continue until the end of the line In this commit, multi-token productions in the core grammar can use separators interchangably with spaces. However, I think we will ultimately want a different rule preventing separators from occurring before an infix operator, so that the end of a line is always unambiguous. This would avoid gratuitous differences between modules and repl usage. We already effectively have this rule, because otherwise `x<newline> | y` would be a single pipeline, but of course that wouldn't work.
2019-12-04 21:14:52 +00:00
[[package]]
name = "nu-macros"
Bump to 0.11.0 (#1474)
2020-03-10 17:34:19 +00:00
version = "0.11.0"
Add Range and start Signature support This commit contains two improvements: - Support for a Range syntax (and a corresponding Range value) - Work towards a signature syntax Implementing the Range syntax resulted in cleaning up how operators in the core syntax works. There are now two kinds of infix operators - tight operators (`.` and `..`) - loose operators Tight operators may not be interspersed (`$it.left..$it.right` is a syntax error). Loose operators require whitespace on both sides of the operator, and can be arbitrarily interspersed. Precedence is left to right in the core syntax. Note that delimited syntax (like `( ... )` or `[ ... ]`) is a single token node in the core syntax. A single token node can be parsed from beginning to end in a context-free manner. The rule for `.` is `<token node>.<member>`. The rule for `..` is `<token node>..<token node>`. Loose operators all have the same syntactic rule: `<token node><space><loose op><space><token node>`. The second aspect of this pull request is the beginning of support for a signature syntax. Before implementing signatures, a necessary prerequisite is for the core syntax to support multi-line programs. That work establishes a few things: - `;` and newlines are handled in the core grammar, and both count as "separators" - line comments begin with `#` and continue until the end of the line In this commit, multi-token productions in the core grammar can use separators interchangably with spaces. However, I think we will ultimately want a different rule preventing separators from occurring before an infix operator, so that the end of a line is always unambiguous. This would avoid gratuitous differences between modules and repl usage. We already effectively have this rule, because otherwise `x<newline> | y` would be a single pipeline, but of course that wouldn't work.
2019-12-04 21:14:52 +00:00
dependencies = [
"nu-protocol",
]
Extract core stuff into own crates This commit extracts five new crates: - nu-source, which contains the core source-code handling logic in Nu, including Text, Span, and also the pretty.rs-based debug logic - nu-parser, which is the parser and expander logic - nu-protocol, which is the bulk of the types and basic conveniences used by plugins - nu-errors, which contains ShellError, ParseError and error handling conveniences - nu-textview, which is the textview plugin extracted into a crate One of the major consequences of this refactor is that it's no longer possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so a lot of types became more concrete (Value became a concrete type instead of Spanned<Value>, for example). This also turned a number of inherent methods in the main nu crate into plain functions (impl Value {} became a bunch of functions in the `value` namespace in `crate::data::value`).
2019-11-26 02:30:48 +00:00
[[package]]
name = "nu-parser"
Bump to 0.11.0 (#1474)
2020-03-10 17:34:19 +00:00
version = "0.11.0"
Extract core stuff into own crates This commit extracts five new crates: - nu-source, which contains the core source-code handling logic in Nu, including Text, Span, and also the pretty.rs-based debug logic - nu-parser, which is the parser and expander logic - nu-protocol, which is the bulk of the types and basic conveniences used by plugins - nu-errors, which contains ShellError, ParseError and error handling conveniences - nu-textview, which is the textview plugin extracted into a crate One of the major consequences of this refactor is that it's no longer possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so a lot of types became more concrete (Value became a concrete type instead of Spanned<Value>, for example). This also turned a number of inherent methods in the main nu crate into plain functions (impl Value {} became a bunch of functions in the `value` namespace in `crate::data::value`).
2019-11-26 02:30:48 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"ansi_term 0.12.1",
"bigdecimal",
"cfg-if",
"derive-new",
Add Range and start Signature support This commit contains two improvements: - Support for a Range syntax (and a corresponding Range value) - Work towards a signature syntax Implementing the Range syntax resulted in cleaning up how operators in the core syntax works. There are now two kinds of infix operators - tight operators (`.` and `..`) - loose operators Tight operators may not be interspersed (`$it.left..$it.right` is a syntax error). Loose operators require whitespace on both sides of the operator, and can be arbitrarily interspersed. Precedence is left to right in the core syntax. Note that delimited syntax (like `( ... )` or `[ ... ]`) is a single token node in the core syntax. A single token node can be parsed from beginning to end in a context-free manner. The rule for `.` is `<token node>.<member>`. The rule for `..` is `<token node>..<token node>`. Loose operators all have the same syntactic rule: `<token node><space><loose op><space><token node>`. The second aspect of this pull request is the beginning of support for a signature syntax. Before implementing signatures, a necessary prerequisite is for the core syntax to support multi-line programs. That work establishes a few things: - `;` and newlines are handled in the core grammar, and both count as "separators" - line comments begin with `#` and continue until the end of the line In this commit, multi-token productions in the core grammar can use separators interchangably with spaces. However, I think we will ultimately want a different rule preventing separators from occurring before an infix operator, so that the end of a line is always unambiguous. This would avoid gratuitous differences between modules and repl usage. We already effectively have this rule, because otherwise `x<newline> | y` would be a single pipeline, but of course that wouldn't work.
2019-12-04 21:14:52 +00:00
"enumflags2",
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
"getset 0.0.9",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"indexmap",
"itertools 0.8.2",
"language-reporting",
"log",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"nom 5.1.0",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"nom-tracable",
"nom_locate",
Extract build.rs
2019-12-02 21:14:51 +00:00
"nu-build",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"nu-errors",
"nu-protocol",
"nu-source",
"num-bigint",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"num-traits 0.2.11",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"pretty",
Fix the workspace I commented out
2019-12-18 17:58:23 +00:00
"pretty_assertions",
Switch stdin redirect to manual. Add test (#1367)
2020-02-10 06:55:07 +00:00
"pretty_env_logger 0.3.1",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"ptree",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"serde 1.0.104",
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
"shellexpand 1.1.1",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"termcolor",
"unicode-xid",
Extract core stuff into own crates This commit extracts five new crates: - nu-source, which contains the core source-code handling logic in Nu, including Text, Span, and also the pretty.rs-based debug logic - nu-parser, which is the parser and expander logic - nu-protocol, which is the bulk of the types and basic conveniences used by plugins - nu-errors, which contains ShellError, ParseError and error handling conveniences - nu-textview, which is the textview plugin extracted into a crate One of the major consequences of this refactor is that it's no longer possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so a lot of types became more concrete (Value became a concrete type instead of Spanned<Value>, for example). This also turned a number of inherent methods in the main nu crate into plain functions (impl Value {} became a bunch of functions in the `value` namespace in `crate::data::value`).
2019-11-26 02:30:48 +00:00
]
Nu plugins now depend on nu-plugin crate.
2019-12-27 13:30:14 +00:00
[[package]]
name = "nu-plugin"
Bump to 0.11.0 (#1474)
2020-03-10 17:34:19 +00:00
version = "0.11.0"
Nu plugins now depend on nu-plugin crate.
2019-12-27 13:30:14 +00:00
dependencies = [
"indexmap",
"nu-build",
"nu-errors",
"nu-protocol",
"nu-source",
"nu-value-ext",
"num-bigint",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"serde 1.0.104",
Nu plugins now depend on nu-plugin crate.
2019-12-27 13:30:14 +00:00
"serde_json",
]
Extract core stuff into own crates This commit extracts five new crates: - nu-source, which contains the core source-code handling logic in Nu, including Text, Span, and also the pretty.rs-based debug logic - nu-parser, which is the parser and expander logic - nu-protocol, which is the bulk of the types and basic conveniences used by plugins - nu-errors, which contains ShellError, ParseError and error handling conveniences - nu-textview, which is the textview plugin extracted into a crate One of the major consequences of this refactor is that it's no longer possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so a lot of types became more concrete (Value became a concrete type instead of Spanned<Value>, for example). This also turned a number of inherent methods in the main nu crate into plain functions (impl Value {} became a bunch of functions in the `value` namespace in `crate::data::value`).
2019-11-26 02:30:48 +00:00
[[package]]
name = "nu-protocol"
Bump to 0.11.0 (#1474)
2020-03-10 17:34:19 +00:00
version = "0.11.0"
Extract core stuff into own crates This commit extracts five new crates: - nu-source, which contains the core source-code handling logic in Nu, including Text, Span, and also the pretty.rs-based debug logic - nu-parser, which is the parser and expander logic - nu-protocol, which is the bulk of the types and basic conveniences used by plugins - nu-errors, which contains ShellError, ParseError and error handling conveniences - nu-textview, which is the textview plugin extracted into a crate One of the major consequences of this refactor is that it's no longer possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so a lot of types became more concrete (Value became a concrete type instead of Spanned<Value>, for example). This also turned a number of inherent methods in the main nu crate into plain functions (impl Value {} became a bunch of functions in the `value` namespace in `crate::data::value`).
2019-11-26 02:30:48 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"ansi_term 0.12.1",
"bigdecimal",
Move the remainder of the plugins to crates
2019-12-09 18:39:51 +00:00
"byte-unit",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"chrono",
"derive-new",
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
"getset 0.0.9",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"indexmap",
"language-reporting",
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
"natural 0.3.0",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"nom 5.1.0",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"nom-tracable",
"nom_locate",
Extract build.rs
2019-12-02 21:14:51 +00:00
"nu-build",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"nu-errors",
"nu-source",
"num-bigint",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"num-traits 0.2.11",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"query_interface",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"serde 1.0.104",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"serde_bytes",
"serde_json",
"serde_yaml",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"toml 0.5.6",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"typetag",
Extract core stuff into own crates This commit extracts five new crates: - nu-source, which contains the core source-code handling logic in Nu, including Text, Span, and also the pretty.rs-based debug logic - nu-parser, which is the parser and expander logic - nu-protocol, which is the bulk of the types and basic conveniences used by plugins - nu-errors, which contains ShellError, ParseError and error handling conveniences - nu-textview, which is the textview plugin extracted into a crate One of the major consequences of this refactor is that it's no longer possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so a lot of types became more concrete (Value became a concrete type instead of Spanned<Value>, for example). This also turned a number of inherent methods in the main nu crate into plain functions (impl Value {} became a bunch of functions in the `value` namespace in `crate::data::value`).
2019-11-26 02:30:48 +00:00
]
Extract nu_source into a crate This commit extracts Tag, Span, Text, as well as source-related debug facilities into a new crate called nu_source. This change is much bigger than one might have expected because the previous code relied heavily on implementing inherent methods on `Tagged<T>` and `Spanned<T>`, which is no longer possible. As a result, this change creates more concrete types instead of using `Tagged<T>`. One notable example: Tagged<Value> became Value, and Value became UntaggedValue. This change clarifies the intent of the code in many places, but it does make it a big change.
2019-11-21 14:33:14 +00:00
[[package]]
name = "nu-source"
Bump to 0.11.0 (#1474)
2020-03-10 17:34:19 +00:00
version = "0.11.0"
Extract nu_source into a crate This commit extracts Tag, Span, Text, as well as source-related debug facilities into a new crate called nu_source. This change is much bigger than one might have expected because the previous code relied heavily on implementing inherent methods on `Tagged<T>` and `Spanned<T>`, which is no longer possible. As a result, this change creates more concrete types instead of using `Tagged<T>`. One notable example: Tagged<Value> became Value, and Value became UntaggedValue. This change clarifies the intent of the code in many places, but it does make it a big change.
2019-11-21 14:33:14 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"derive-new",
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
"getset 0.0.9",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"language-reporting",
"nom-tracable",
"nom_locate",
Extract build.rs
2019-12-02 21:14:51 +00:00
"nu-build",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"pretty",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"serde 1.0.104",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"termcolor",
Restructure and make commands uniform
2019-05-22 07:12:03 +00:00
]
Rename test-support to nu-test-support
2019-12-17 18:41:47 +00:00
[[package]]
name = "nu-test-support"
Bump to 0.11.0 (#1474)
2020-03-10 17:34:19 +00:00
version = "0.11.0"
Rename test-support to nu-test-support
2019-12-17 18:41:47 +00:00
dependencies = [
"app_dirs",
"dunce",
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
"getset 0.0.9",
Rename test-support to nu-test-support
2019-12-17 18:41:47 +00:00
"glob",
Baseline environment and configuration work. (#1287)
2020-01-28 03:13:22 +00:00
"indexmap",
Keep dummies in default features for convenience. (#1212)
2020-01-13 06:17:56 +00:00
"nu-build",
Externals now spawn independently. (#1230) This commit changes the way we shell out externals when using the `"$it"` argument. Also pipes per row to an external's stdin if no `"$it"` argument is present for external commands. Further separation of logic (preparing the external's command arguments, getting the data for piping, emitting values, spawning processes) will give us a better idea for lower level details regarding external commands until we can find the right abstractions for making them more generic and unify within the pipeline calling logic of Nu internal's and external's.
2020-01-16 09:05:53 +00:00
"nu-parser",
Baseline environment and configuration work. (#1287)
2020-01-28 03:13:22 +00:00
"nu-protocol",
Externals now spawn independently. (#1230) This commit changes the way we shell out externals when using the `"$it"` argument. Also pipes per row to an external's stdin if no `"$it"` argument is present for external commands. Further separation of logic (preparing the external's command arguments, getting the data for piping, emitting values, spawning processes) will give us a better idea for lower level details regarding external commands until we can find the right abstractions for making them more generic and unify within the pipeline calling logic of Nu internal's and external's.
2020-01-16 09:05:53 +00:00
"nu-source",
Rename test-support to nu-test-support
2019-12-17 18:41:47 +00:00
"tempfile",
]
Move the remainder of the plugins to crates
2019-12-09 18:39:51 +00:00
[[package]]
name = "nu-value-ext"
Bump to 0.11.0 (#1474)
2020-03-10 17:34:19 +00:00
version = "0.11.0"
Move the remainder of the plugins to crates
2019-12-09 18:39:51 +00:00
dependencies = [
Baseline environment and configuration work. (#1287)
2020-01-28 03:13:22 +00:00
"indexmap",
Move the remainder of the plugins to crates
2019-12-09 18:39:51 +00:00
"itertools 0.8.2",
"nu-build",
"nu-errors",
"nu-parser",
"nu-protocol",
"nu-source",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"num-traits 0.2.11",
Move the remainder of the plugins to crates
2019-12-09 18:39:51 +00:00
]
[[package]]
name = "nu_plugin_average"
Bump to 0.11.0 (#1474)
2020-03-10 17:34:19 +00:00
version = "0.11.0"
Move the remainder of the plugins to crates
2019-12-09 18:39:51 +00:00
dependencies = [
"nu-build",
"nu-errors",
Nu plugins now depend on nu-plugin crate.
2019-12-27 13:30:14 +00:00
"nu-plugin",
Move the remainder of the plugins to crates
2019-12-09 18:39:51 +00:00
"nu-protocol",
"nu-source",
]
Move binaryview to a sub-crate
2019-12-04 17:51:20 +00:00
[[package]]
name = "nu_plugin_binaryview"
Bump to 0.11.0 (#1474)
2020-03-10 17:34:19 +00:00
version = "0.11.0"
Move binaryview to a sub-crate
2019-12-04 17:51:20 +00:00
dependencies = [
"ansi_term 0.12.1",
Switch stdin redirect to manual. Add test (#1367)
2020-02-10 06:55:07 +00:00
"crossterm 0.14.2",
Move binaryview to a sub-crate
2019-12-04 17:51:20 +00:00
"image",
"neso",
"nu-build",
"nu-errors",
Nu plugins now depend on nu-plugin crate.
2019-12-27 13:30:14 +00:00
"nu-plugin",
Move binaryview to a sub-crate
2019-12-04 17:51:20 +00:00
"nu-protocol",
"nu-source",
"pretty-hex",
"rawkey",
Extract ps and sys subcrates. Move helper methods to UntaggedValue
2019-12-04 19:52:31 +00:00
]
WIP move post/fetch to plugins
2019-12-07 03:46:05 +00:00
[[package]]
name = "nu_plugin_fetch"
Bump to 0.11.0 (#1474)
2020-03-10 17:34:19 +00:00
version = "0.11.0"
WIP move post/fetch to plugins
2019-12-07 03:46:05 +00:00
dependencies = [
Update more futures-preview to futures (#1346)
2020-02-06 04:28:42 +00:00
"futures 0.3.3",
WIP move post/fetch to plugins
2019-12-07 03:46:05 +00:00
"nu-build",
"nu-errors",
Nu plugins now depend on nu-plugin crate.
2019-12-27 13:30:14 +00:00
"nu-plugin",
WIP move post/fetch to plugins
2019-12-07 03:46:05 +00:00
"nu-protocol",
"nu-source",
"surf",
"url",
]
Trying this as a workaround to the [[bin]] issue
2019-12-10 03:57:55 +00:00
[[package]]
name = "nu_plugin_inc"
Bump to 0.11.0 (#1474)
2020-03-10 17:34:19 +00:00
version = "0.11.0"
Trying this as a workaround to the [[bin]] issue
2019-12-10 03:57:55 +00:00
dependencies = [
"nu-build",
"nu-errors",
Nu plugins now depend on nu-plugin crate.
2019-12-27 13:30:14 +00:00
"nu-plugin",
Trying this as a workaround to the [[bin]] issue
2019-12-10 03:57:55 +00:00
"nu-protocol",
"nu-source",
"nu-value-ext",
"semver",
]
Move the remainder of the plugins to crates
2019-12-09 18:39:51 +00:00
[[package]]
name = "nu_plugin_match"
Bump to 0.11.0 (#1474)
2020-03-10 17:34:19 +00:00
version = "0.11.0"
Move the remainder of the plugins to crates
2019-12-09 18:39:51 +00:00
dependencies = [
Update more futures-preview to futures (#1346)
2020-02-06 04:28:42 +00:00
"futures 0.3.3",
Move the remainder of the plugins to crates
2019-12-09 18:39:51 +00:00
"nu-build",
"nu-errors",
Nu plugins now depend on nu-plugin crate.
2019-12-27 13:30:14 +00:00
"nu-plugin",
Move the remainder of the plugins to crates
2019-12-09 18:39:51 +00:00
"nu-protocol",
"nu-source",
"regex",
]
WIP move post/fetch to plugins
2019-12-07 03:46:05 +00:00
[[package]]
name = "nu_plugin_post"
Bump to 0.11.0 (#1474)
2020-03-10 17:34:19 +00:00
version = "0.11.0"
WIP move post/fetch to plugins
2019-12-07 03:46:05 +00:00
dependencies = [
"base64 0.11.0",
Update more futures-preview to futures (#1346)
2020-02-06 04:28:42 +00:00
"futures 0.3.3",
WIP move post/fetch to plugins
2019-12-07 03:46:05 +00:00
"nu-build",
"nu-errors",
Nu plugins now depend on nu-plugin crate.
2019-12-27 13:30:14 +00:00
"nu-plugin",
WIP move post/fetch to plugins
2019-12-07 03:46:05 +00:00
"nu-protocol",
"nu-source",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"num-traits 0.2.11",
WIP move post/fetch to plugins
2019-12-07 03:46:05 +00:00
"serde_json",
"surf",
"url",
]
Trying this as a workaround to the [[bin]] issue
2019-12-10 03:57:55 +00:00
[[package]]
name = "nu_plugin_ps"
Bump to 0.11.0 (#1474)
2020-03-10 17:34:19 +00:00
version = "0.11.0"
Trying this as a workaround to the [[bin]] issue
2019-12-10 03:57:55 +00:00
dependencies = [
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
"futures 0.3.3",
"futures-timer 3.0.1",
Trying this as a workaround to the [[bin]] issue
2019-12-10 03:57:55 +00:00
"heim",
"nu-build",
"nu-errors",
Nu plugins now depend on nu-plugin crate.
2019-12-27 13:30:14 +00:00
"nu-plugin",
Trying this as a workaround to the [[bin]] issue
2019-12-10 03:57:55 +00:00
"nu-protocol",
"nu-source",
"pin-utils",
]
Update deps locklfile (#1446) Update deps lockfile
2020-03-03 20:34:23 +00:00
[[package]]
name = "nu_plugin_shuffle"
Bump to 0.11.0 (#1474)
2020-03-10 17:34:19 +00:00
version = "0.11.0"
Update deps locklfile (#1446) Update deps lockfile
2020-03-03 20:34:23 +00:00
dependencies = [
"nu-build",
"nu-errors",
"nu-plugin",
"nu-protocol",
"nu-source",
"rand",
]
Trying this as a workaround to the [[bin]] issue
2019-12-10 03:57:55 +00:00
[[package]]
name = "nu_plugin_str"
Bump to 0.11.0 (#1474)
2020-03-10 17:34:19 +00:00
version = "0.11.0"
Trying this as a workaround to the [[bin]] issue
2019-12-10 03:57:55 +00:00
dependencies = [
Add string to datetime to str plugin (#1381) * Add string to datetime to str plugin * Test string to date/time conversion
2020-02-13 15:47:04 +00:00
"chrono",
Trying this as a workaround to the [[bin]] issue
2019-12-10 03:57:55 +00:00
"nu-build",
"nu-errors",
Nu plugins now depend on nu-plugin crate.
2019-12-27 13:30:14 +00:00
"nu-plugin",
Trying this as a workaround to the [[bin]] issue
2019-12-10 03:57:55 +00:00
"nu-protocol",
"nu-source",
"nu-value-ext",
"num-bigint",
"regex",
]
Move the remainder of the plugins to crates
2019-12-09 18:39:51 +00:00
[[package]]
name = "nu_plugin_sum"
Bump to 0.11.0 (#1474)
2020-03-10 17:34:19 +00:00
version = "0.11.0"
Move the remainder of the plugins to crates
2019-12-09 18:39:51 +00:00
dependencies = [
"nu-build",
"nu-errors",
Nu plugins now depend on nu-plugin crate.
2019-12-27 13:30:14 +00:00
"nu-plugin",
Move the remainder of the plugins to crates
2019-12-09 18:39:51 +00:00
"nu-protocol",
"nu-source",
]
Trying this as a workaround to the [[bin]] issue
2019-12-10 03:57:55 +00:00
[[package]]
name = "nu_plugin_sys"
Bump to 0.11.0 (#1474)
2020-03-10 17:34:19 +00:00
version = "0.11.0"
Trying this as a workaround to the [[bin]] issue
2019-12-10 03:57:55 +00:00
dependencies = [
"battery",
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
"futures 0.3.3",
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
"futures-util",
Trying this as a workaround to the [[bin]] issue
2019-12-10 03:57:55 +00:00
"heim",
"nu-build",
"nu-errors",
Nu plugins now depend on nu-plugin crate.
2019-12-27 13:30:14 +00:00
"nu-plugin",
Trying this as a workaround to the [[bin]] issue
2019-12-10 03:57:55 +00:00
"nu-protocol",
"nu-source",
]
[[package]]
name = "nu_plugin_textview"
Bump to 0.11.0 (#1474)
2020-03-10 17:34:19 +00:00
version = "0.11.0"
Trying this as a workaround to the [[bin]] issue
2019-12-10 03:57:55 +00:00
dependencies = [
"ansi_term 0.12.1",
Switch stdin redirect to manual. Add test (#1367)
2020-02-10 06:55:07 +00:00
"crossterm 0.14.2",
Trying this as a workaround to the [[bin]] issue
2019-12-10 03:57:55 +00:00
"nu-build",
"nu-errors",
Nu plugins now depend on nu-plugin crate.
2019-12-27 13:30:14 +00:00
"nu-plugin",
Trying this as a workaround to the [[bin]] issue
2019-12-10 03:57:55 +00:00
"nu-protocol",
"nu-source",
"onig_sys",
"syntect",
"url",
]
Move the remainder of the plugins to crates
2019-12-09 18:39:51 +00:00
[[package]]
name = "nu_plugin_tree"
Bump to 0.11.0 (#1474)
2020-03-10 17:34:19 +00:00
version = "0.11.0"
Move the remainder of the plugins to crates
2019-12-09 18:39:51 +00:00
dependencies = [
"derive-new",
"nu-build",
"nu-errors",
Nu plugins now depend on nu-plugin crate.
2019-12-27 13:30:14 +00:00
"nu-plugin",
Move the remainder of the plugins to crates
2019-12-09 18:39:51 +00:00
"nu-protocol",
"nu-source",
"ptree",
]
Basic support for decimal numbers This commit is more substantial than it looks: there was basically no real support for decimals before, and that impacted values all the way through. I also made Size contain a decimal instead of an integer (`1.6kb` is a reasonable thing to type), which impacted a bunch of code. The biggest impact of this commit is that it creates many more possible ways for valid nu types to fail to serialize as toml, json, etc. which typically can't support the full range of Decimal (or Bigint, which I also think we should support). This commit makes to-toml fallible, and a similar effort is necessary for the rest of the serializations. We also need to figure out how to clearly communicate to users what has happened, but failing to serialize to toml seems clearly superior to me than weird errors in basic math operations.
2019-08-30 17:29:04 +00:00
[[package]]
name = "num-bigint"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.2.6"
Basic support for decimal numbers This commit is more substantial than it looks: there was basically no real support for decimals before, and that impacted values all the way through. I also made Size contain a decimal instead of an integer (`1.6kb` is a reasonable thing to type), which impacted a bunch of code. The biggest impact of this commit is that it creates many more possible ways for valid nu types to fail to serialize as toml, json, etc. which typically can't support the full range of Decimal (or Bigint, which I also think we should support). This commit makes to-toml fallible, and a similar effort is necessary for the rest of the serializations. We also need to figure out how to clearly communicate to users what has happened, but failing to serialize to toml seems clearly superior to me than weird errors in basic math operations.
2019-08-30 17:29:04 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "090c7f9998ee0ff65aa5b723e4009f7b217707f1fb5ea551329cc4d6231fb304"
Basic support for decimal numbers This commit is more substantial than it looks: there was basically no real support for decimals before, and that impacted values all the way through. I also made Size contain a decimal instead of an integer (`1.6kb` is a reasonable thing to type), which impacted a bunch of code. The biggest impact of this commit is that it creates many more possible ways for valid nu types to fail to serialize as toml, json, etc. which typically can't support the full range of Decimal (or Bigint, which I also think we should support). This commit makes to-toml fallible, and a similar effort is necessary for the rest of the serializations. We also need to figure out how to clearly communicate to users what has happened, but failing to serialize to toml seems clearly superior to me than weird errors in basic math operations.
2019-08-30 17:29:04 +00:00
dependencies = [
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"autocfg 1.0.0",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"num-integer",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"num-traits 0.2.11",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"serde 1.0.104",
Basic support for decimal numbers This commit is more substantial than it looks: there was basically no real support for decimals before, and that impacted values all the way through. I also made Size contain a decimal instead of an integer (`1.6kb` is a reasonable thing to type), which impacted a bunch of code. The biggest impact of this commit is that it creates many more possible ways for valid nu types to fail to serialize as toml, json, etc. which typically can't support the full range of Decimal (or Bigint, which I also think we should support). This commit makes to-toml fallible, and a similar effort is necessary for the rest of the serializations. We also need to figure out how to clearly communicate to users what has happened, but failing to serialize to toml seems clearly superior to me than weird errors in basic math operations.
2019-08-30 17:29:04 +00:00
]
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "num-integer"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
version = "0.1.42"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
checksum = "3f6ea62e9d81a77cd3ee9a2a5b9b609447857f3d358704331e4ef39eb247fcba"
objectshell initial commit
2019-05-10 16:59:12 +00:00
dependencies = [
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"autocfg 1.0.0",
"num-traits 0.2.11",
Restructure and make commands uniform
2019-05-22 07:12:03 +00:00
]
Add some logic for more binary formats
2019-07-05 07:53:09 +00:00
[[package]]
name = "num-iter"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.1.40"
Add some logic for more binary formats
2019-07-05 07:53:09 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "dfb0800a0291891dd9f4fe7bd9c19384f98f7fbe0cd0f39a2c6b88b9868bbc00"
Add some logic for more binary formats
2019-07-05 07:53:09 +00:00
dependencies = [
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
"autocfg 1.0.0",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"num-integer",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"num-traits 0.2.11",
Add some logic for more binary formats
2019-07-05 07:53:09 +00:00
]
[[package]]
name = "num-rational"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.2.3"
Add some logic for more binary formats
2019-07-05 07:53:09 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "da4dc79f9e6c81bef96148c8f6b8e72ad4541caa4a24373e900a36da07de03a3"
Add some logic for more binary formats
2019-07-05 07:53:09 +00:00
dependencies = [
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
"autocfg 1.0.0",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"num-integer",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"num-traits 0.2.11",
Add some logic for more binary formats
2019-07-05 07:53:09 +00:00
]
Lots of misc improvements
2019-06-03 07:41:28 +00:00
[[package]]
name = "num-traits"
version = "0.1.43"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "92e5113e9fd4cc14ded8e499429f396a20f98c772a47cc8622a736e1ec843c31"
Lots of misc improvements
2019-06-03 07:41:28 +00:00
dependencies = [
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"num-traits 0.2.11",
Lots of misc improvements
2019-06-03 07:41:28 +00:00
]
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "num-traits"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
version = "0.2.11"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
checksum = "c62be47e61d1842b9170f0fdeec8eba98e60e90e5446449a0545e5152acd7096"
Restructure and make commands uniform
2019-05-22 07:12:03 +00:00
dependencies = [
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"autocfg 1.0.0",
Restructure and make commands uniform
2019-05-22 07:12:03 +00:00
]
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "num_cpus"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "1.12.0"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "46203554f085ff89c235cd12f7075f3233af9b11ed7c9e16dfe2560d03313ce6"
objectshell initial commit
2019-05-10 16:59:12 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"hermit-abi",
"libc",
objectshell initial commit
2019-05-10 16:59:12 +00:00
]
Add clipboard support
2019-06-07 16:30:50 +00:00
[[package]]
name = "objc"
Merge master
2019-11-16 17:17:05 +00:00
version = "0.2.7"
Add clipboard support
2019-06-07 16:30:50 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "915b1b472bc21c53464d6c8461c9d3af805ba1ef837e1cac254428f4a77177b1"
Add clipboard support
2019-06-07 16:30:50 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"malloc_buf",
Add clipboard support
2019-06-07 16:30:50 +00:00
]
[[package]]
name = "objc-foundation"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "1add1b659e36c9607c7aab864a76c7a4c2760cd0cd2e120f3fb8b952c7e22bf9"
Add clipboard support
2019-06-07 16:30:50 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"block",
"objc",
"objc_id",
Add clipboard support
2019-06-07 16:30:50 +00:00
]
[[package]]
name = "objc_id"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "c92d4ddb4bd7b50d730c215ff871754d0da6b2178849f8a2a2ab69712d0c073b"
Add clipboard support
2019-06-07 16:30:50 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"objc",
Add clipboard support
2019-06-07 16:30:50 +00:00
]
Improve signature infrastructure The `config` command uses different kinds of named arguments, which illustrates how it works.
2019-06-01 05:50:16 +00:00
[[package]]
name = "ole32-sys"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "5d2c49021782e5233cd243168edfa8037574afed4eba4bbaf538b3d8d1789d8c"
Improve signature infrastructure The `config` command uses different kinds of named arguments, which illustrates how it works.
2019-06-01 05:50:16 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"winapi 0.2.8",
"winapi-build",
Improve signature infrastructure The `config` command uses different kinds of named arguments, which illustrates how it works.
2019-06-01 05:50:16 +00:00
]
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
[[package]]
name = "once_cell"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "1.3.1"
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "b1c601810575c99596d4afc46f78a678c80105117c379eb3650cf99b8a21ce5b"
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
Bat
2019-05-18 01:24:13 +00:00
[[package]]
name = "onig"
Fix #811 (#813)
2019-10-13 04:53:58 +00:00
version = "4.3.3"
Bat
2019-05-18 01:24:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "8518fcb2b1b8c2f45f0ad499df4fda6087fc3475ca69a185c173b8315d2fb383"
Bat
2019-05-18 01:24:13 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"bitflags",
"lazy_static 1.4.0",
"libc",
"onig_sys",
Bat
2019-05-18 01:24:13 +00:00
]
[[package]]
name = "onig_sys"
Revert bump
2019-08-10 06:31:31 +00:00
version = "69.1.0"
Bat
2019-05-18 01:24:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "388410bf5fa341f10e58e6db3975f4bea1ac30247dd79d37a9e5ced3cb4cc3b0"
Bat
2019-05-18 01:24:13 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"cc",
"pkg-config",
Bat
2019-05-18 01:24:13 +00:00
]
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
[[package]]
name = "open"
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
version = "1.4.0"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
checksum = "7c283bf0114efea9e42f1a60edea9859e8c47528eae09d01df4b29c1e489cc48"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
dependencies = [
"winapi 0.3.8",
]
Add git branch to prompt
2019-06-01 21:11:28 +00:00
[[package]]
name = "openssl-probe"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "77af24da69f9d9341038eba93a073b1fdaaa1b788221b00a69bce9e762cb32de"
Add git branch to prompt
2019-06-01 21:11:28 +00:00
[[package]]
name = "openssl-sys"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.9.54"
Add git branch to prompt
2019-06-01 21:11:28 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "1024c0a59774200a555087a6da3f253a9095a5f344e353b212ac4c8b8e450986"
Add git branch to prompt
2019-06-01 21:11:28 +00:00
dependencies = [
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
"autocfg 1.0.0",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"cc",
"libc",
"pkg-config",
"vcpkg",
Add git branch to prompt
2019-06-01 21:11:28 +00:00
]
Update bson to 0.14
2019-08-31 14:22:45 +00:00
[[package]]
name = "ord_subset"
version = "3.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "d7ce14664caf5b27f5656ff727defd68ae1eb75ef3c4d95259361df1eb376bef"
Update bson to 0.14
2019-08-31 14:22:45 +00:00
Added a first pass at sort-by
2019-05-17 15:55:50 +00:00
[[package]]
name = "ordered-float"
version = "1.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "18869315e81473c951eb56ad5558bbc56978562d3ecfb87abb7a1e944cea4518"
Added a first pass at sort-by
2019-05-17 15:55:50 +00:00
dependencies = [
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"num-traits 0.2.11",
Restructure and make commands uniform
2019-05-22 07:12:03 +00:00
]
Add tree sink
2019-06-07 07:50:26 +00:00
[[package]]
name = "ordermap"
version = "0.3.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "a86ed3f5f244b372d6b1a00b72ef7f8876d0bc6a78a4c9985c53614041512063"
Add tree sink
2019-06-07 07:50:26 +00:00
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
[[package]]
name = "os_info"
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
version = "2.0.1"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
checksum = "cf0044ce3b28b09ffb3ef188c81dbc6592999366d153dccdc065045ee54717f7"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
dependencies = [
"log",
"serde 1.0.104",
"winapi 0.3.8",
]
Custom lexer
2019-05-29 15:26:45 +00:00
[[package]]
name = "output_vt100"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "53cdc5b785b7a58c5aad8216b3dfa114df64b0b06ae6e1501cef91df2fbdf8f9"
Custom lexer
2019-05-29 15:26:45 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"winapi 0.3.8",
Last unwraps (#1160) * Work through most of the last unwraps * Finish removing unwraps
2020-01-04 06:44:17 +00:00
]
[[package]]
name = "parking_lot"
version = "0.10.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "92e98c49ab0b7ce5b222f2cc9193fc4efe11c6d0bd4f648e374684a6857b1cfc"
dependencies = [
"lock_api",
"parking_lot_core",
]
[[package]]
name = "parking_lot_core"
version = "0.7.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7582838484df45743c8434fbff785e8edf260c28748353d44bc0da32e0ceabf1"
dependencies = [
"cfg-if",
"cloudabi",
"libc",
"redox_syscall",
"smallvec",
"winapi 0.3.8",
Custom lexer
2019-05-29 15:26:45 +00:00
]
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
[[package]]
name = "path-slash"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "a0858af4d9136275541f4eac7be1af70add84cf356d901799b065ac1b8ff6e2f"
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
bump deps
2019-07-29 07:46:24 +00:00
[[package]]
name = "percent-encoding"
Pin semver breaking dep
2019-08-08 17:33:19 +00:00
version = "2.1.0"
bump deps
2019-07-29 07:46:24 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "d4fd5641d01c8f18a23da7b6fe29298ff4b55afcccdf78973b24cf3175fee32e"
bump deps
2019-07-29 07:46:24 +00:00
Add tree sink
2019-06-07 07:50:26 +00:00
[[package]]
name = "petgraph"
version = "0.4.13"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "9c3659d1ee90221741f65dd128d9998311b0e40c5d3c23a62445938214abce4f"
Add tree sink
2019-06-07 07:50:26 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"fixedbitset",
"ordermap",
Add tree sink
2019-06-07 07:50:26 +00:00
]
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
[[package]]
name = "pin-project"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.4.8"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "7804a463a8d9572f13453c516a5faea534a2403d7ced2f0c7e100eeff072772c"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
dependencies = [
"pin-project-internal",
]
[[package]]
name = "pin-project-internal"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.4.8"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "385322a45f2ecf3410c68d2a549a4a2685e8051d0f278e39743ff4e451cb9b3f"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
dependencies = [
"proc-macro2",
"quote",
"syn",
]
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
[[package]]
name = "pin-project-lite"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.1.4"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "237844750cfbb86f67afe27eee600dfbbcb6188d734139b534cbfbf4f96792ae"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
Small restructuring
2019-05-23 04:30:43 +00:00
[[package]]
name = "pin-utils"
version = "0.1.0-alpha.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "5894c618ce612a3fa23881b152b608bafb8c56cfc22f434a3ba3120b40f7b587"
Small restructuring
2019-05-23 04:30:43 +00:00
Bat
2019-05-18 01:24:13 +00:00
[[package]]
name = "pkg-config"
Merge master
2019-11-16 17:17:05 +00:00
version = "0.3.17"
Bat
2019-05-18 01:24:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "05da548ad6865900e60eaba7f589cc0783590a92e940c26953ff81ddbab2d677"
Bat
2019-05-18 01:24:13 +00:00
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
[[package]]
name = "platforms"
Fix #811 (#813)
2019-10-13 04:53:58 +00:00
version = "0.2.1"
Bat
2019-05-18 01:24:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "feb3b2b1033b8a60b4da6ee470325f887758c95d5320f52f9ce0df055a55940e"
Bat
2019-05-18 01:24:13 +00:00
[[package]]
name = "plist"
Merge master
2019-06-22 01:38:17 +00:00
version = "0.4.2"
Bat
2019-05-18 01:24:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "5f2a9f075f6394100e7c105ed1af73fb1859d6fd14e49d4290d578120beb167f"
Bat
2019-05-18 01:24:13 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"base64 0.10.1",
"byteorder",
"humantime",
"line-wrap",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"serde 1.0.104",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"xml-rs",
Bat
2019-05-18 01:24:13 +00:00
]
Add some logic for more binary formats
2019-07-05 07:53:09 +00:00
[[package]]
name = "png"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.15.3"
Add some logic for more binary formats
2019-07-05 07:53:09 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "ef859a23054bbfee7811284275ae522f0434a3c8e7f4b74bd4a35ae7e1c4a283"
Add some logic for more binary formats
2019-07-05 07:53:09 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"bitflags",
"crc32fast",
"deflate",
"inflate",
Add some logic for more binary formats
2019-07-05 07:53:09 +00:00
]
Add from_xlsx for importing excel files
2019-11-17 03:18:41 +00:00
[[package]]
name = "podio"
version = "0.1.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "780fb4b6698bbf9cf2444ea5d22411cef2953f0824b98f33cf454ec5615645bd"
Add from_xlsx for importing excel files
2019-11-17 03:18:41 +00:00
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
[[package]]
name = "ppv-lite86"
Merge master
2019-11-16 17:17:05 +00:00
version = "0.2.6"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "74490b50b9fbe561ac330df47c08f3f33073d2d00c150f719147d7c54522fa1b"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
--no-edit
2019-11-04 15:47:03 +00:00
[[package]]
name = "pretty"
version = "0.5.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "f60c0d9f6fc88ecdd245d90c1920ff76a430ab34303fc778d33b1d0a4c3bf6d3"
--no-edit
2019-11-04 15:47:03 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"typed-arena",
--no-edit
2019-11-04 15:47:03 +00:00
]
Add pretty binary viewing
2019-07-04 05:23:05 +00:00
[[package]]
name = "pretty-hex"
Fix #811 (#813)
2019-10-13 04:53:58 +00:00
version = "0.1.1"
Add pretty binary viewing
2019-07-04 05:23:05 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "be91bcc43e73799dc46a6c194a55e7aae1d86cc867c860fd4a436019af21bd8c"
Add pretty binary viewing
2019-07-04 05:23:05 +00:00
Custom lexer
2019-05-29 15:26:45 +00:00
[[package]]
name = "pretty_assertions"
version = "0.6.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "3f81e1644e1b54f5a68959a29aa86cde704219254669da328ecfdf6a1f09d427"
Custom lexer
2019-05-29 15:26:45 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"ansi_term 0.11.0",
"ctor",
"difference",
"output_vt100",
Custom lexer
2019-05-29 15:26:45 +00:00
]
A real parser (lalrpop)
2019-05-26 06:54:41 +00:00
[[package]]
name = "pretty_env_logger"
Remove X11 requirement
2019-08-23 03:29:08 +00:00
version = "0.3.1"
A real parser (lalrpop)
2019-05-26 06:54:41 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "717ee476b1690853d222af4634056d830b5197ffd747726a9a1eee6da9f49074"
A real parser (lalrpop)
2019-05-26 06:54:41 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"chrono",
Switch stdin redirect to manual. Add test (#1367)
2020-02-10 06:55:07 +00:00
"env_logger 0.6.2",
"log",
]
[[package]]
name = "pretty_env_logger"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "926d36b9553851b8b0005f1275891b392ee4d2d833852c417ed025477350fb9d"
dependencies = [
"env_logger 0.7.1",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"log",
A real parser (lalrpop)
2019-05-26 06:54:41 +00:00
]
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "prettytable-rs"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "0fd04b170004fa2daccf418a7f8253aaf033c27760b5f225889024cf66d7ac2e"
objectshell initial commit
2019-05-10 16:59:12 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"atty",
"csv",
"encode_unicode",
"lazy_static 1.4.0",
"term",
"unicode-width",
objectshell initial commit
2019-05-10 16:59:12 +00:00
]
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
[[package]]
name = "proc-macro-error"
version = "0.4.11"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e7959c6467d962050d639361f7703b2051c43036d03493c36f01d440fdd3138a"
dependencies = [
"proc-macro-error-attr",
"proc-macro2",
"quote",
"syn",
"version_check 0.9.1",
]
[[package]]
name = "proc-macro-error-attr"
version = "0.4.11"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e4002d9f55991d5e019fb940a90e1a95eb80c24e77cb2462dd4dc869604d543a"
dependencies = [
"proc-macro2",
"quote",
"syn",
"syn-mid",
"version_check 0.9.1",
]
--no-edit
2019-11-04 15:47:03 +00:00
[[package]]
name = "proc-macro-hack"
version = "0.5.11"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "ecd45702f76d6d3c75a80564378ae228a85f0b59d2f3ed43c91b4a69eb2ebfc5"
--no-edit
2019-11-04 15:47:03 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"proc-macro2",
"quote",
"syn",
--no-edit
2019-11-04 15:47:03 +00:00
]
[[package]]
name = "proc-macro-nested"
version = "0.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "369a6ed065f249a159e06c45752c780bda2fb53c995718f9e484d08daa9eb42e"
--no-edit
2019-11-04 15:47:03 +00:00
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "proc-macro2"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "1.0.8"
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "3acb317c6ff86a4e579dfa00fc5e6cca91ecbb4e7eb2df0468805b674eb88548"
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"unicode-xid",
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
]
Add tree sink
2019-06-07 07:50:26 +00:00
[[package]]
name = "ptree"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "6b0a3be00b19ee7bd33238c1c523a7ab4df697345f6b36f90827a7860ea938d4"
Add tree sink
2019-06-07 07:50:26 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"ansi_term 0.11.0",
"config",
"directories",
"isatty",
"petgraph",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"serde 1.0.104",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"serde-value",
"serde_derive",
"tint",
Add tree sink
2019-06-07 07:50:26 +00:00
]
Extract core stuff into own crates This commit extracts five new crates: - nu-source, which contains the core source-code handling logic in Nu, including Text, Span, and also the pretty.rs-based debug logic - nu-parser, which is the parser and expander logic - nu-protocol, which is the bulk of the types and basic conveniences used by plugins - nu-errors, which contains ShellError, ParseError and error handling conveniences - nu-textview, which is the textview plugin extracted into a crate One of the major consequences of this refactor is that it's no longer possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so a lot of types became more concrete (Value became a concrete type instead of Spanned<Value>, for example). This also turned a number of inherent methods in the main nu crate into plain functions (impl Value {} became a bunch of functions in the `value` namespace in `crate::data::value`).
2019-11-26 02:30:48 +00:00
[[package]]
name = "query_interface"
version = "0.3.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "78c0f0046284eebb86b68f93f9677d499034f88e15ca01021ceea32c4d3c3693"
Extract core stuff into own crates This commit extracts five new crates: - nu-source, which contains the core source-code handling logic in Nu, including Text, Span, and also the pretty.rs-based debug logic - nu-parser, which is the parser and expander logic - nu-protocol, which is the bulk of the types and basic conveniences used by plugins - nu-errors, which contains ShellError, ParseError and error handling conveniences - nu-textview, which is the textview plugin extracted into a crate One of the major consequences of this refactor is that it's no longer possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so a lot of types became more concrete (Value became a concrete type instead of Spanned<Value>, for example). This also turned a number of inherent methods in the main nu crate into plain functions (impl Value {} became a bunch of functions in the `value` namespace in `crate::data::value`).
2019-11-26 02:30:48 +00:00
Bat
2019-05-18 01:24:13 +00:00
[[package]]
name = "quick-error"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "1.2.3"
Bat
2019-05-18 01:24:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "a1d01941d82fa2ab50be1e79e6714289dd7cde78eba4c074bc5a4374f650dfe0"
Bat
2019-05-18 01:24:13 +00:00
Add from_xlsx for importing excel files
2019-11-17 03:18:41 +00:00
[[package]]
name = "quick-xml"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
version = "0.17.2"
Add from_xlsx for importing excel files
2019-11-17 03:18:41 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
checksum = "fe1e430bdcf30c9fdc25053b9c459bb1a4672af4617b6c783d7d91dc17c6bbb0"
Add from_xlsx for importing excel files
2019-11-17 03:18:41 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"encoding_rs",
"memchr",
Add from_xlsx for importing excel files
2019-11-17 03:18:41 +00:00
]
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
[[package]]
name = "quote"
version = "1.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "053a8c8bcc71fcce321828dc897a98ab9760bef03a4fc36693c231e5b3216cfe"
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"proc-macro2",
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
]
Bat
2019-05-18 01:24:13 +00:00
[[package]]
name = "rand"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.7.3"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "6a6b1679d49b24bbfe0c803429aa1874472f50d9b363131f0e89fc356b544d03"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"getrandom",
"libc",
"rand_chacha",
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
"rand_core",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"rand_hc",
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
]
[[package]]
name = "rand_chacha"
bump deps
2019-07-29 07:46:24 +00:00
version = "0.2.1"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "03a2a90da8c7523f554344f921aa97283eadf6ac484a6d2a7d0212fa7f8d6853"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"c2-chacha",
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
"rand_core",
objectshell initial commit
2019-05-10 16:59:12 +00:00
]
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
[[package]]
name = "rand_core"
Fix #811 (#813)
2019-10-13 04:53:58 +00:00
version = "0.5.1"
Bat
2019-05-18 01:24:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "90bde5296fc891b0cef12a6d03ddccc162ce7b2aff54160af9338f8d40df6d19"
Bat
2019-05-18 01:24:13 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"getrandom",
Bat
2019-05-18 01:24:13 +00:00
]
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
[[package]]
name = "rand_hc"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "ca3129af7b92a17112d59ad498c6f81eaf463253766b90396d39ea7a39d6613c"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
dependencies = [
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
"rand_core",
objectshell initial commit
2019-05-10 16:59:12 +00:00
]
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
[[package]]
name = "raw-cpuid"
Add Cargo.lock
2019-09-24 19:02:35 +00:00
version = "7.0.3"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "b4a349ca83373cfa5d6dbb66fd76e58b2cca08da71a5f6400de0a0a6a9bceeaf"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"bitflags",
"cc",
"rustc_version",
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
]
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
[[package]]
name = "rawkey"
Move off of git deps
2019-08-02 03:58:10 +00:00
version = "0.1.2"
Cleanup for upcoming release
2019-07-16 19:10:25 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "33ec17a493dcb820725c002bc253f6f3ba4e4dc635e72c238540691b05e43897"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"readkey",
"user32-sys",
"winapi 0.3.8",
"x11",
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
]
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
[[package]]
name = "rayon"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
version = "1.3.0"
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
checksum = "db6ce3297f9c85e16621bb8cca38a06779ffc31bb8184e1be4bed2be4678a098"
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"crossbeam-deque",
"either",
"rayon-core",
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
]
[[package]]
name = "rayon-core"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
version = "1.7.0"
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
checksum = "08a89b46efaf957e52b18062fb2f4660f8b8a4dde1807ca002690868ef2c85a9"
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"crossbeam-deque",
"crossbeam-queue",
"crossbeam-utils 0.7.0",
"lazy_static 1.4.0",
"num_cpus",
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
]
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
[[package]]
name = "readkey"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
version = "0.1.7"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
checksum = "86d401b6d6a1725a59f1b4e813275d289dff3ad09c72b373a10a7a8217ba3146"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "redox_syscall"
bump deps
2019-07-29 07:46:24 +00:00
version = "0.1.56"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "2439c63f3f6139d1b57529d16bc3b8bb855230c8efcc5d3a896c8bea7c3b1e84"
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "redox_users"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.3.4"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "09b23093265f8d200fa7b4c2c76297f47e681c655f6f1285a8780d6a022f7431"
objectshell initial commit
2019-05-10 16:59:12 +00:00
dependencies = [
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
"getrandom",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"redox_syscall",
"rust-argon2",
objectshell initial commit
2019-05-10 16:59:12 +00:00
]
[[package]]
name = "regex"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "1.3.4"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "322cf97724bea3ee221b78fe25ac9c46114ebb51747ad5babd51a2fc6a8235a8"
objectshell initial commit
2019-05-10 16:59:12 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"aho-corasick",
"memchr",
"regex-syntax",
"thread_local",
objectshell initial commit
2019-05-10 16:59:12 +00:00
]
Introduced ability to open csv documents.
2019-07-19 20:11:49 +00:00
[[package]]
name = "regex-automata"
bump deps
2019-07-29 07:46:24 +00:00
version = "0.1.8"
Introduced ability to open csv documents.
2019-07-19 20:11:49 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "92b73c2a1770c255c240eaa4ee600df1704a38dc3feaa6e949e7fcd4f8dc09f9"
Introduced ability to open csv documents.
2019-07-19 20:11:49 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"byteorder",
Introduced ability to open csv documents.
2019-07-19 20:11:49 +00:00
]
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "regex-syntax"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.6.14"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "b28dfe3fe9badec5dbf0a79a9cccad2cfc2ab5484bdb3e44cbd1ae8b3ba2be06"
objectshell initial commit
2019-05-10 16:59:12 +00:00
Add opening urls
2019-06-08 18:09:17 +00:00
[[package]]
name = "remove_dir_all"
Merge master
2019-06-22 01:38:17 +00:00
version = "0.5.2"
Add opening urls
2019-06-08 18:09:17 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "4a83fa3702a688b9359eccba92d153ac33fd2e8462f9e0e3fdf155239ea7792e"
Add opening urls
2019-06-08 18:09:17 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"winapi 0.3.8",
Add opening urls
2019-06-08 18:09:17 +00:00
]
Better errors and more fleshed out semantics
2019-05-30 04:19:46 +00:00
[[package]]
name = "render-tree"
version = "0.1.1"
Update cargo.lock
2019-10-16 02:09:47 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "68ed587df09cfb7ce1bc6fe8f77e24db219f222c049326ccbfb948ec67e31664"
Better errors and more fleshed out semantics
2019-05-30 04:19:46 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"itertools 0.7.11",
"log",
"termcolor",
Better errors and more fleshed out semantics
2019-05-30 04:19:46 +00:00
]
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
[[package]]
name = "reqwest"
version = "0.10.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c0e798e19e258bf6c30a304622e3e9ac820e483b06a1857a026e1f109b113fe4"
dependencies = [
"base64 0.11.0",
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
"bytes 0.5.4",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"encoding_rs",
"futures-core",
"futures-util",
"http 0.2.0",
"http-body",
"hyper",
"hyper-rustls",
"js-sys",
"lazy_static 1.4.0",
"log",
"mime",
"mime_guess",
"percent-encoding",
"pin-project-lite",
"rustls",
"serde 1.0.104",
"serde_urlencoded",
"time",
"tokio",
"tokio-rustls",
"url",
"wasm-bindgen",
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
"wasm-bindgen-futures 0.4.8",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"web-sys",
"webpki-roots",
"winreg",
]
Add .ini loading/saving
2019-06-16 06:43:40 +00:00
[[package]]
name = "result"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "194d8e591e405d1eecf28819740abed6d719d1a2db87fc0bcdedee9a26d55560"
Add .ini loading/saving
2019-06-16 06:43:40 +00:00
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
[[package]]
name = "ring"
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
version = "0.16.11"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
checksum = "741ba1704ae21999c00942f9f5944f801e977f54302af346b596287599ad1862"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
dependencies = [
"cc",
"lazy_static 1.4.0",
"libc",
"spin",
"untrusted",
"web-sys",
"winapi 0.3.8",
]
Add xml open support
2019-06-11 06:26:03 +00:00
[[package]]
name = "roxmltree"
Switch stdin redirect to manual. Add test (#1367)
2020-02-10 06:55:07 +00:00
version = "0.9.1"
Add xml open support
2019-06-11 06:26:03 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch stdin redirect to manual. Add test (#1367)
2020-02-10 06:55:07 +00:00
checksum = "99d696b20b92d3e02e08fd8456f0ab03007c99e6b111a6205b9cb6fc044d0957"
Add xml open support
2019-06-11 06:26:03 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"xmlparser",
Add xml open support
2019-06-11 06:26:03 +00:00
]
Add SQLite support
2019-08-27 21:45:18 +00:00
[[package]]
name = "rusqlite"
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
version = "0.21.0"
Add SQLite support
2019-08-27 21:45:18 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
checksum = "64a656821bb6317a84b257737b7934f79c0dbb7eb694710475908280ebad3e64"
Add SQLite support
2019-08-27 21:45:18 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"bitflags",
"fallible-iterator",
"fallible-streaming-iterator",
"libsqlite3-sys",
"lru-cache",
"memchr",
"time",
Add SQLite support
2019-08-27 21:45:18 +00:00
]
Pin semver breaking dep
2019-08-08 17:33:19 +00:00
[[package]]
name = "rust-argon2"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.7.0"
Pin semver breaking dep
2019-08-08 17:33:19 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "2bc8af4bda8e1ff4932523b94d3dd20ee30a87232323eda55903ffd71d2fb017"
Pin semver breaking dep
2019-08-08 17:33:19 +00:00
dependencies = [
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
"base64 0.11.0",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"blake2b_simd",
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
"constant_time_eq",
"crossbeam-utils 0.7.0",
Pin semver breaking dep
2019-08-08 17:33:19 +00:00
]
Add tree sink
2019-06-07 07:50:26 +00:00
[[package]]
name = "rust-ini"
version = "0.13.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "3e52c148ef37f8c375d49d5a73aa70713125b7f19095948a923f80afdeb22ec2"
Add tree sink
2019-06-07 07:50:26 +00:00
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
[[package]]
name = "rust-stemmers"
version = "1.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e46a2036019fdb888131db7a4c847a1063a7493f971ed94ea82c67eada63ca54"
dependencies = [
"serde 1.0.104",
"serde_derive",
]
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "rustc-demangle"
Fix #811 (#813)
2019-10-13 04:53:58 +00:00
version = "0.1.16"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "4c691c0e608126e00913e33f0ccf3727d5fc84573623b8d65b2df340b5201783"
objectshell initial commit
2019-05-10 16:59:12 +00:00
Update bson to 0.14
2019-08-31 14:22:45 +00:00
[[package]]
name = "rustc-serialize"
version = "0.3.24"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "dcf128d1287d2ea9d80910b5f1120d0b8eede3fbf1abe91c40d39ea7d51e6fda"
Update bson to 0.14
2019-08-31 14:22:45 +00:00
Bat
2019-05-18 01:24:13 +00:00
[[package]]
name = "rustc_version"
version = "0.2.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "138e3e0acb6c9fb258b19b67cb8abd63c00679d2851805ea151465464fe9030a"
Bat
2019-05-18 01:24:13 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"semver",
Bat
2019-05-18 01:24:13 +00:00
]
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
[[package]]
name = "rustls"
version = "0.16.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b25a18b1bf7387f0145e7f8324e700805aade3842dd3db2e74e4cdeb4677c09e"
dependencies = [
"base64 0.10.1",
"log",
"ring",
"sct",
"webpki",
]
[[package]]
name = "rustls-native-certs"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "51ffebdbb48c14f84eba0b715197d673aff1dd22cc1007ca647e28483bbcc307"
dependencies = [
"openssl-probe",
"rustls",
"schannel",
"security-framework",
]
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "rustyline"
Updated rustyline to 6.0.0. Added completion_mode config (#1289) * Updated rustyline to 6.0.0. Added completion_mode config * Formatted completion_mode config
2020-01-27 03:41:17 +00:00
version = "6.0.0"
Bump rustyline (#1146) * Slightly improve new which command * Bump rustyline
2020-01-01 17:54:25 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Updated rustyline to 6.0.0. Added completion_mode config (#1289) * Updated rustyline to 6.0.0. Added completion_mode config * Formatted completion_mode config
2020-01-27 03:41:17 +00:00
checksum = "de64be8eecbe428b6924f1d8430369a01719fbb182c26fa431ddbb0a95f5315d"
objectshell initial commit
2019-05-10 16:59:12 +00:00
dependencies = [
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
"cfg-if",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"dirs 2.0.2",
"libc",
"log",
"memchr",
"nix 0.14.1",
"unicode-segmentation",
"unicode-width",
"utf8parse",
"winapi 0.3.8",
objectshell initial commit
2019-05-10 16:59:12 +00:00
]
Bump and cleanup plugin name match
2019-07-04 03:06:43 +00:00
[[package]]
name = "ryu"
Merge master
2019-11-16 17:17:05 +00:00
version = "1.0.2"
Bump and cleanup plugin name match
2019-07-04 03:06:43 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "bfa8506c1de11c9c4e4c38863ccbe02a305c8188e85a05a784c9e11e1c3910c8"
Bump and cleanup plugin name match
2019-07-04 03:06:43 +00:00
Bat
2019-05-18 01:24:13 +00:00
[[package]]
name = "safemem"
Merge master
2019-11-16 17:17:05 +00:00
version = "0.3.3"
Bat
2019-05-18 01:24:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "ef703b7cb59335eae2eb93ceb664c0eb7ea6bf567079d843e09420219668e072"
Bat
2019-05-18 01:24:13 +00:00
[[package]]
name = "same-file"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "1.0.6"
Bat
2019-05-18 01:24:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "93fc1dc3aaa9bfed95e02e6eadabb4baf7e3078b0bd1b4d7b6b0b68378900502"
Bat
2019-05-18 01:24:13 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"winapi-util",
Bat
2019-05-18 01:24:13 +00:00
]
Add opening urls
2019-06-08 18:09:17 +00:00
[[package]]
name = "schannel"
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
version = "0.1.17"
Add opening urls
2019-06-08 18:09:17 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
checksum = "507a9e6e8ffe0a4e0ebb9a10293e62fdf7657c06f1b8bb07a8fcf697d2abf295"
Add opening urls
2019-06-08 18:09:17 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"lazy_static 1.4.0",
"winapi 0.3.8",
Add opening urls
2019-06-08 18:09:17 +00:00
]
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
[[package]]
name = "scopeguard"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "b42e15e59b18a828bbf5c58ea01debb36b9b096346de35d941dcb89009f24a0d"
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
[[package]]
name = "sct"
version = "0.6.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e3042af939fca8c3453b7af0f1c66e533a15a86169e39de2657310ade8f98d3c"
dependencies = [
"ring",
"untrusted",
]
[[package]]
name = "security-framework"
version = "0.3.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8ef2429d7cefe5fd28bd1d2ed41c944547d4ff84776f5935b456da44593a16df"
dependencies = [
"core-foundation 0.6.4",
"core-foundation-sys 0.6.2",
"libc",
"security-framework-sys",
]
[[package]]
name = "security-framework-sys"
version = "0.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e31493fc37615debb8c5090a7aeb4a9730bc61e77ab10b9af59f1a202284f895"
dependencies = [
"core-foundation-sys 0.6.2",
]
Bat
2019-05-18 01:24:13 +00:00
[[package]]
name = "semver"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "1d7eb9ef2c18661902cc47e535f9bc51b78acd254da71d375c2f6720d9a40403"
Bat
2019-05-18 01:24:13 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"semver-parser",
Bat
2019-05-18 01:24:13 +00:00
]
[[package]]
name = "semver-parser"
version = "0.7.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "388a1df253eca08550bef6c72392cfe7c30914bf41df5269b68cbd6ff8f570a3"
Bat
2019-05-18 01:24:13 +00:00
Lots of misc improvements
2019-06-03 07:41:28 +00:00
[[package]]
name = "serde"
version = "0.8.23"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "9dad3f759919b92c3068c696c15c3d17238234498bbdcc80f2c469606f948ac8"
Lots of misc improvements
2019-06-03 07:41:28 +00:00
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "serde"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
version = "1.0.104"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
checksum = "414115f25f818d7dfccec8ee535d76949ae78584fc4f79a6f45a904bf8ab4449"
Add opening urls
2019-06-08 18:09:17 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"serde_derive",
Add opening urls
2019-06-08 18:09:17 +00:00
]
objectshell initial commit
2019-05-10 16:59:12 +00:00
Add tree sink
2019-06-07 07:50:26 +00:00
[[package]]
name = "serde-hjson"
version = "0.8.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "0b833c5ad67d52ced5f5938b2980f32a9c1c5ef047f0b4fb3127e7a423c76153"
Add tree sink
2019-06-07 07:50:26 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"lazy_static 0.2.11",
"linked-hash-map 0.3.0",
"num-traits 0.1.43",
"regex",
"serde 0.8.23",
Add tree sink
2019-06-07 07:50:26 +00:00
]
Lots of misc improvements
2019-06-03 07:41:28 +00:00
[[package]]
name = "serde-hjson"
Remove X11 requirement
2019-08-23 03:29:08 +00:00
version = "0.9.1"
Lots of misc improvements
2019-06-03 07:41:28 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "6a3a4e0ea8a88553209f6cc6cfe8724ecad22e1acf372793c27d995290fe74f8"
Lots of misc improvements
2019-06-03 07:41:28 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"lazy_static 1.4.0",
"linked-hash-map 0.3.0",
"num-traits 0.1.43",
"regex",
"serde 0.8.23",
Lots of misc improvements
2019-06-03 07:41:28 +00:00
]
Add tree sink
2019-06-07 07:50:26 +00:00
[[package]]
name = "serde-value"
version = "0.5.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "7a663f873dedc4eac1a559d4c6bc0d0b2c34dc5ac4702e105014b8281489e44f"
Add tree sink
2019-06-07 07:50:26 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"ordered-float",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"serde 1.0.104",
Add tree sink
2019-06-07 07:50:26 +00:00
]
Bump deps and add serde_bytes support
2019-07-15 18:34:44 +00:00
[[package]]
name = "serde_bytes"
Upgrade some dependencies
2019-12-08 17:56:21 +00:00
version = "0.11.3"
Bump deps and add serde_bytes support
2019-07-15 18:34:44 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade some dependencies
2019-12-08 17:56:21 +00:00
checksum = "325a073952621257820e7a3469f55ba4726d8b28657e7e36653d1c36dc2c84ae"
Bump deps and add serde_bytes support
2019-07-15 18:34:44 +00:00
dependencies = [
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"serde 1.0.104",
Bump deps and add serde_bytes support
2019-07-15 18:34:44 +00:00
]
Bat
2019-05-18 01:24:13 +00:00
[[package]]
name = "serde_derive"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
version = "1.0.104"
Bat
2019-05-18 01:24:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
checksum = "128f9e303a5a29922045a830221b8f78ec74a5f544944f3d5984f8ec3895ef64"
Bat
2019-05-18 01:24:13 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"proc-macro2",
"quote",
"syn",
Bat
2019-05-18 01:24:13 +00:00
]
Add .ini loading/saving
2019-06-16 06:43:40 +00:00
[[package]]
name = "serde_ini"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "eb236687e2bb073a7521c021949be944641e671b8505a94069ca37b656c81139"
Add .ini loading/saving
2019-06-16 06:43:40 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"result",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"serde 1.0.104",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"void",
Add a bunch more tokens and delimited ()
2019-06-12 17:44:45 +00:00
]
Bat
2019-05-18 01:24:13 +00:00
[[package]]
name = "serde_json"
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
version = "1.0.48"
Bat
2019-05-18 01:24:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
checksum = "9371ade75d4c2d6cb154141b9752cf3781ec9c05e0e5cf35060e1e70ee7b9c25"
Bat
2019-05-18 01:24:13 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"indexmap",
"itoa",
"ryu",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"serde 1.0.104",
Bat
2019-05-18 01:24:13 +00:00
]
Lots of misc improvements
2019-06-03 07:41:28 +00:00
[[package]]
name = "serde_test"
version = "0.8.23"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "110b3dbdf8607ec493c22d5d947753282f3bae73c0f56d322af1e8c78e4c23d5"
Lots of misc improvements
2019-06-03 07:41:28 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"serde 0.8.23",
Lots of misc improvements
2019-06-03 07:41:28 +00:00
]
Add opening urls
2019-06-08 18:09:17 +00:00
[[package]]
name = "serde_urlencoded"
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
version = "0.6.1"
Add opening urls
2019-06-08 18:09:17 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "9ec5d77e2d4c73717816afac02670d5c4f534ea95ed430442cad02e7a6e32c97"
Add opening urls
2019-06-08 18:09:17 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"dtoa",
"itoa",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"serde 1.0.104",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"url",
Add opening urls
2019-06-08 18:09:17 +00:00
]
Lots of misc improvements
2019-06-03 07:41:28 +00:00
[[package]]
name = "serde_yaml"
Fix #811 (#813)
2019-10-13 04:53:58 +00:00
version = "0.8.11"
Lots of misc improvements
2019-06-03 07:41:28 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "691b17f19fc1ec9d94ec0b5864859290dff279dbd7b03f017afda54eb36c3c35"
Lots of misc improvements
2019-06-03 07:41:28 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"dtoa",
"linked-hash-map 0.5.2",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"serde 1.0.104",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"yaml-rust",
Lots of misc improvements
2019-06-03 07:41:28 +00:00
]
Improve signature infrastructure The `config` command uses different kinds of named arguments, which illustrates how it works.
2019-06-01 05:50:16 +00:00
[[package]]
name = "shell32-sys"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "9ee04b46101f57121c9da2b151988283b6beb79b34f5bb29a58ee48cb695122c"
Improve signature infrastructure The `config` command uses different kinds of named arguments, which illustrates how it works.
2019-06-01 05:50:16 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"winapi 0.2.8",
"winapi-build",
Improve signature infrastructure The `config` command uses different kinds of named arguments, which illustrates how it works.
2019-06-01 05:50:16 +00:00
]
Add support for ~ expansion This ended up being a bit of a yak shave. The basic idea in this commit is to expand `~` in paths, but only in paths. The way this is accomplished is by doing the expansion inside of the code that parses literal syntax for `SyntaxType::Path`. As a quick refresher: every command is entitled to expand its arguments in a custom way. While this could in theory be used for general-purpose macros, today the expansion facility is limited to syntactic hints. For example, the syntax `where cpu > 0` expands under the hood to `where { $it.cpu > 0 }`. This happens because the first argument to `where` is defined as a `SyntaxType::Block`, and the parser coerces binary expressions whose left-hand-side looks like a member into a block when the command is expecting one. This is mildly more magical than what most programming languages would do, but we believe that it makes sense to allow commands to fine-tune the syntax because of the domain nushell is in (command-line shells). The syntactic expansions supported by this facility are relatively limited. For example, we don't allow `$it` to become a bare word, simply because the command asks for a string in the relevant position. That would quickly become more confusing than it's worth. This PR adds a new `SyntaxType` rule: `SyntaxType::Path`. When a command declares a parameter as a `SyntaxType::Path`, string literals and bare words passed as an argument to that parameter are processed using the path expansion rules. Right now, that only means that `~` is expanded into the home directory, but additional rules are possible in the future. By restricting this expansion to a syntactic expansion when passed as an argument to a command expecting a path, we avoid making `~` a generally reserved character. This will also allow us to give good tab completion for paths with `~` characters in them when a command is expecting a path. In order to accomplish the above, this commit changes the parsing functions to take a `Context` instead of just a `CommandRegistry`. From the perspective of macro expansion, you can think of the `CommandRegistry` as a dictionary of in-scope macros, and the `Context` as the compile-time state used in expansion. This could gain additional functionality over time as we find more uses for the expansion system.
2019-08-26 19:21:03 +00:00
[[package]]
name = "shellexpand"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
version = "1.1.1"
Add support for ~ expansion This ended up being a bit of a yak shave. The basic idea in this commit is to expand `~` in paths, but only in paths. The way this is accomplished is by doing the expansion inside of the code that parses literal syntax for `SyntaxType::Path`. As a quick refresher: every command is entitled to expand its arguments in a custom way. While this could in theory be used for general-purpose macros, today the expansion facility is limited to syntactic hints. For example, the syntax `where cpu > 0` expands under the hood to `where { $it.cpu > 0 }`. This happens because the first argument to `where` is defined as a `SyntaxType::Block`, and the parser coerces binary expressions whose left-hand-side looks like a member into a block when the command is expecting one. This is mildly more magical than what most programming languages would do, but we believe that it makes sense to allow commands to fine-tune the syntax because of the domain nushell is in (command-line shells). The syntactic expansions supported by this facility are relatively limited. For example, we don't allow `$it` to become a bare word, simply because the command asks for a string in the relevant position. That would quickly become more confusing than it's worth. This PR adds a new `SyntaxType` rule: `SyntaxType::Path`. When a command declares a parameter as a `SyntaxType::Path`, string literals and bare words passed as an argument to that parameter are processed using the path expansion rules. Right now, that only means that `~` is expanded into the home directory, but additional rules are possible in the future. By restricting this expansion to a syntactic expansion when passed as an argument to a command expecting a path, we avoid making `~` a generally reserved character. This will also allow us to give good tab completion for paths with `~` characters in them when a command is expecting a path. In order to accomplish the above, this commit changes the parsing functions to take a `Context` instead of just a `CommandRegistry`. From the perspective of macro expansion, you can think of the `CommandRegistry` as a dictionary of in-scope macros, and the `Context` as the compile-time state used in expansion. This could gain additional functionality over time as we find more uses for the expansion system.
2019-08-26 19:21:03 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
checksum = "2c7e79eddc7b411f9beeaaf2d421de7e7cb3b1ab9eaf1b79704c0e4130cba6b5"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
dependencies = [
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"dirs 2.0.2",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
]
Add support for ~ expansion This ended up being a bit of a yak shave. The basic idea in this commit is to expand `~` in paths, but only in paths. The way this is accomplished is by doing the expansion inside of the code that parses literal syntax for `SyntaxType::Path`. As a quick refresher: every command is entitled to expand its arguments in a custom way. While this could in theory be used for general-purpose macros, today the expansion facility is limited to syntactic hints. For example, the syntax `where cpu > 0` expands under the hood to `where { $it.cpu > 0 }`. This happens because the first argument to `where` is defined as a `SyntaxType::Block`, and the parser coerces binary expressions whose left-hand-side looks like a member into a block when the command is expecting one. This is mildly more magical than what most programming languages would do, but we believe that it makes sense to allow commands to fine-tune the syntax because of the domain nushell is in (command-line shells). The syntactic expansions supported by this facility are relatively limited. For example, we don't allow `$it` to become a bare word, simply because the command asks for a string in the relevant position. That would quickly become more confusing than it's worth. This PR adds a new `SyntaxType` rule: `SyntaxType::Path`. When a command declares a parameter as a `SyntaxType::Path`, string literals and bare words passed as an argument to that parameter are processed using the path expansion rules. Right now, that only means that `~` is expanded into the home directory, but additional rules are possible in the future. By restricting this expansion to a syntactic expansion when passed as an argument to a command expecting a path, we avoid making `~` a generally reserved character. This will also allow us to give good tab completion for paths with `~` characters in them when a command is expecting a path. In order to accomplish the above, this commit changes the parsing functions to take a `Context` instead of just a `CommandRegistry`. From the perspective of macro expansion, you can think of the `CommandRegistry` as a dictionary of in-scope macros, and the `Context` as the compile-time state used in expansion. This could gain additional functionality over time as we find more uses for the expansion system.
2019-08-26 19:21:03 +00:00
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
[[package]]
name = "shellexpand"
version = "2.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9a2b22262a9aaf9464d356f656fea420634f78c881c5eebd5ef5e66d8b9bc603"
dependencies = [
"dirs 2.0.2",
]
Upgrade crossterm (#1288) * WIP * Finish porting to new crossterm * Fmt
2020-01-27 02:51:46 +00:00
[[package]]
name = "signal-hook"
version = "0.1.13"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "10b9f3a1686a29f53cfd91ee5e3db3c12313ec02d33765f02c1a9645a1811e2c"
dependencies = [
"libc",
"mio",
"signal-hook-registry",
]
[[package]]
name = "signal-hook-registry"
version = "1.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "94f478ede9f64724c5d173d7bb56099ec3e2d9fc2774aac65d34b8b890405f41"
dependencies = [
"arc-swap",
"libc",
]
Small restructuring
2019-05-23 04:30:43 +00:00
[[package]]
name = "slab"
version = "0.4.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "c111b5bd5695e56cffe5129854aa230b39c93a305372fdbb2668ca2394eea9f8"
Small restructuring
2019-05-23 04:30:43 +00:00
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
[[package]]
name = "sluice"
Fix #811 (#813)
2019-10-13 04:53:58 +00:00
version = "0.4.2"
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "0a7d06dfb3e8743bc19e6de8a302277471d08077d68946b307280496dc5a3531"
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"futures-channel-preview",
"futures-core-preview",
"futures-io-preview",
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
]
Bat
2019-05-18 01:24:13 +00:00
[[package]]
name = "smallvec"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "1.2.0"
Bat
2019-05-18 01:24:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "5c2fb2ec9bcd216a5b0d0ccf31ab17b5ed1d627960edff65bbe95d3ce221cefc"
Bat
2019-05-18 01:24:13 +00:00
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
[[package]]
name = "socket2"
version = "0.3.11"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "e8b74de517221a2cb01a53349cf54182acdc31a074727d3079068448c0676d85"
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"cfg-if",
"libc",
"redox_syscall",
"winapi 0.3.8",
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
]
[[package]]
name = "sourcefile"
version = "0.1.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "4bf77cb82ba8453b42b6ae1d692e4cdc92f9a47beaf89a847c8be83f4e328ad3"
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
[[package]]
name = "spin"
version = "0.5.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6e63cff320ae2c57904679ba7cb63280a3dc4613885beafb148ee7bf9aa9042d"
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
[[package]]
name = "starship"
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
version = "0.37.0"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
checksum = "588e250206eec64cee803f0d7c1d1f7c1d3ba7e123d513f0311b172d07a0f755"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
dependencies = [
"ansi_term 0.12.1",
"battery",
"byte-unit",
"chrono",
"clap",
"dirs 2.0.2",
"gethostname",
"git2",
"log",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"nom 5.1.0",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"once_cell",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"open",
"os_info",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"path-slash",
Switch stdin redirect to manual. Add test (#1367)
2020-02-10 06:55:07 +00:00
"pretty_env_logger 0.4.0",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"rayon",
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
"regex",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"reqwest",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"serde_json",
"starship_module_config_derive",
"sysinfo",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"term_size",
"textwrap",
"toml 0.5.6",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"unicode-segmentation",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"unicode-width",
"urlencoding",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"yaml-rust",
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
]
[[package]]
name = "starship_module_config_derive"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
version = "0.1.1"
chore: switch starship dependency back to the main one
2019-10-09 07:36:55 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
checksum = "9d1ccdf8467ad115d088ab970010266b27deec41b9d940f154c785b3808bd04e"
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"proc-macro2",
"quote",
"syn",
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
]
WIP
2019-06-22 03:43:37 +00:00
[[package]]
name = "static_assertions"
Fix #811 (#813)
2019-10-13 04:53:58 +00:00
version = "0.3.4"
WIP
2019-06-22 03:43:37 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "7f3eb36b47e512f8f1c9e3d10c2c1965bc992bd9cdb024fa581e2194501c83d3"
WIP
2019-06-22 03:43:37 +00:00
Give rustyline non-ansi to begin with. Fixes Windows
2019-11-16 20:02:26 +00:00
[[package]]
name = "strip-ansi-escapes"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "9d63676e2abafa709460982ddc02a3bb586b6d15a49b75c212e06edd3933acee"
Give rustyline non-ansi to begin with. Fixes Windows
2019-11-16 20:02:26 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"vte",
Give rustyline non-ansi to begin with. Fixes Windows
2019-11-16 20:02:26 +00:00
]
Bat
2019-05-18 01:24:13 +00:00
[[package]]
name = "strsim"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "8ea5119cdb4c55b55d432abb513a0429384878c15dde60cc77b1c99de1a95a6a"
Bat
2019-05-18 01:24:13 +00:00
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
[[package]]
name = "surf"
Bump dep versions
2019-11-10 17:48:49 +00:00
version = "1.0.3"
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "741a8008f8a833ef16f47df94a30754478fb2c2bf822b9c2e6f7f09203b97ace"
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"futures-preview",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"http 0.1.21",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"isahc",
"js-sys",
"log",
"mime",
"mime_guess",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"serde 1.0.104",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"serde_json",
"serde_urlencoded",
"url",
"wasm-bindgen",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"wasm-bindgen-futures 0.3.27",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"web-sys",
objectshell initial commit
2019-05-10 16:59:12 +00:00
]
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
[[package]]
name = "syn"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "1.0.14"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "af6f3550d8dff9ef7dc34d384ac6f107e5d31c8f57d9f28e0081503f547ac8f5"
objectshell initial commit
2019-05-10 16:59:12 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"proc-macro2",
"quote",
"unicode-xid",
objectshell initial commit
2019-05-10 16:59:12 +00:00
]
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
[[package]]
name = "syn-mid"
version = "0.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7be3539f6c128a931cf19dcee741c1af532c7fd387baa739c03dd2e96479338a"
dependencies = [
"proc-macro2",
"quote",
"syn",
]
Bat
2019-05-18 01:24:13 +00:00
[[package]]
name = "syntect"
Revert bump
2019-08-10 06:31:31 +00:00
version = "3.2.0"
Bat
2019-05-18 01:24:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "e80b8831c5a543192ffc3727f01cf0e57579c6ac15558e3048bfb5708892167b"
Bat
2019-05-18 01:24:13 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"bincode",
"bitflags",
"flate2",
"fnv",
"lazy_static 1.4.0",
"lazycell",
"onig",
"plist",
"regex-syntax",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"serde 1.0.104",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"serde_derive",
"serde_json",
"walkdir",
"yaml-rust",
Bat
2019-05-18 01:24:13 +00:00
]
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
[[package]]
name = "sysinfo"
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
version = "0.11.6"
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
checksum = "0bf9aa50e31b8d8ded9eafa135b4faf717ce308c35a7c919e1ba4cdb10ae1bfe"
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"cfg-if",
"doc-comment",
"libc",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"ntapi",
"once_cell",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"rayon",
"winapi 0.3.8",
feat: starship prompt Kind of touches on #356 by integrating the Starship prompt directly into the shell. Not finished yet and has surfaced a potential bug in rustyline anyway. It depends on https://github.com/starship/starship/pull/509 being merged so the Starship prompt can be used as a library. I could have tackled #356 completely and implemented a full custom prompt feature but I felt this was a simpler approach given that Starship is both written in Rust so shelling out isn't necessary and it already has a bunch of useful features built in. However, I would understand if it would be preferable to just scrap integrating Starship directly and instead implement a custom prompt system which would facilitate simply shelling out to Starship.
2019-10-08 13:47:30 +00:00
]
Add opening urls
2019-06-08 18:09:17 +00:00
[[package]]
name = "tempfile"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
version = "3.1.0"
Add opening urls
2019-06-08 18:09:17 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "7a6e24d9338a0a5be79593e2fa15a648add6138caa803e2d5bc782c371732ca9"
Add opening urls
2019-06-08 18:09:17 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"cfg-if",
"libc",
"rand",
"redox_syscall",
"remove_dir_all",
"winapi 0.3.8",
Add opening urls
2019-06-08 18:09:17 +00:00
]
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "term"
version = "0.5.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "edd106a334b7657c10b7c540a0106114feadeb4dc314513e97df481d5d966f42"
objectshell initial commit
2019-05-10 16:59:12 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"byteorder",
"dirs 1.0.5",
"winapi 0.3.8",
objectshell initial commit
2019-05-10 16:59:12 +00:00
]
Wrap table cells as needed
2019-08-16 05:47:47 +00:00
[[package]]
name = "term_size"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "9e5b9a66db815dcfd2da92db471106457082577c3c278d4138ab3e3b4e189327"
Wrap table cells as needed
2019-08-16 05:47:47 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"kernel32-sys",
"libc",
"winapi 0.2.8",
Wrap table cells as needed
2019-08-16 05:47:47 +00:00
]
A real parser (lalrpop)
2019-05-26 06:54:41 +00:00
[[package]]
name = "termcolor"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
version = "1.1.0"
A real parser (lalrpop)
2019-05-26 06:54:41 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
checksum = "bb6bfa289a4d7c5766392812c0a1f4c1ba45afa1ad47803c11e1f407d846d75f"
A real parser (lalrpop)
2019-05-26 06:54:41 +00:00
dependencies = [
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"winapi-util",
A real parser (lalrpop)
2019-05-26 06:54:41 +00:00
]
Bat
2019-05-18 01:24:13 +00:00
[[package]]
name = "textwrap"
version = "0.11.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "d326610f408c7a4eb6f51c37c330e496b08506c9457c9d34287ecc38809fb060"
Bat
2019-05-18 01:24:13 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"term_size",
"unicode-width",
Bat
2019-05-18 01:24:13 +00:00
]
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
[[package]]
name = "thiserror"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "1.0.10"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "205684fd018ca14432b12cce6ea3d46763311a571c3d294e71ba3f01adcf1aad"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
dependencies = [
"thiserror-impl",
]
[[package]]
name = "thiserror-impl"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "1.0.10"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "57e4d2e50ca050ed44fb58309bdce3efa79948f84f9993ad1978de5eebdce5a7"
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
dependencies = [
"proc-macro2",
"quote",
"syn",
]
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "thread_local"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "1.0.1"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "d40c6d1b69745a6ec6fb1ca717914848da4b44ae29d9b3080cbee91d72a69b14"
objectshell initial commit
2019-05-10 16:59:12 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"lazy_static 1.4.0",
objectshell initial commit
2019-05-10 16:59:12 +00:00
]
Pin semver breaking dep
2019-08-08 17:33:19 +00:00
[[package]]
name = "threadpool"
version = "1.7.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "e2f0c90a5f3459330ac8bc0d2f879c693bb7a2f59689c1083fc4ef83834da865"
Pin semver breaking dep
2019-08-08 17:33:19 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"num_cpus",
Pin semver breaking dep
2019-08-08 17:33:19 +00:00
]
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "time"
version = "0.1.42"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "db8dcfca086c1143c9270ac42a2bbd8a7ee477b78ac8e45b19abfb0cbede4b6f"
objectshell initial commit
2019-05-10 16:59:12 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"libc",
"redox_syscall",
"winapi 0.3.8",
objectshell initial commit
2019-05-10 16:59:12 +00:00
]
Add tree sink
2019-06-07 07:50:26 +00:00
[[package]]
name = "tint"
version = "1.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "7af24570664a3074673dbbf69a65bdae0ae0b72f2949b1adfbacb736ee4d6896"
Add tree sink
2019-06-07 07:50:26 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"lazy_static 0.2.11",
Add tree sink
2019-06-07 07:50:26 +00:00
]
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
[[package]]
name = "tokio"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.2.11"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "8fdd17989496f49cdc57978c96f0c9fe5e4a58a8bddc6813c449a4624f6a030b"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
dependencies = [
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
"bytes 0.5.4",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"fnv",
"iovec",
"lazy_static 1.4.0",
"memchr",
"mio",
"num_cpus",
"pin-project-lite",
"slab",
]
Pipe external to internal Each line is a string object
2019-05-24 18:48:33 +00:00
[[package]]
name = "tokio-io"
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
version = "0.1.13"
Pipe external to internal Each line is a string object
2019-05-24 18:48:33 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
checksum = "57fc868aae093479e3131e3d165c93b1c7474109d13c90ec0dda2a1bbfff0674"
Pipe external to internal Each line is a string object
2019-05-24 18:48:33 +00:00
dependencies = [
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"bytes 0.4.12",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"futures 0.1.29",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"log",
Pipe external to internal Each line is a string object
2019-05-24 18:48:33 +00:00
]
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
[[package]]
name = "tokio-rustls"
version = "0.12.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "141afec0978abae6573065a48882c6bae44c5cc61db9b511ac4abf6a09bfd9cc"
dependencies = [
"futures-core",
"rustls",
"tokio",
"webpki",
]
[[package]]
name = "tokio-util"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "571da51182ec208780505a32528fc5512a8fe1443ab960b3f2f3ef093cd16930"
dependencies = [
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
"bytes 0.5.4",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"futures-core",
"futures-sink",
"log",
"pin-project-lite",
"tokio",
]
Add tree sink
2019-06-07 07:50:26 +00:00
[[package]]
name = "toml"
version = "0.4.10"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "758664fc71a3a69038656bee8b6be6477d2a6c315a6b81f7081f591bffa4111f"
Add tree sink
2019-06-07 07:50:26 +00:00
dependencies = [
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"serde 1.0.104",
Add tree sink
2019-06-07 07:50:26 +00:00
]
Restructure and make commands uniform
2019-05-22 07:12:03 +00:00
[[package]]
name = "toml"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
version = "0.5.6"
Restructure and make commands uniform
2019-05-22 07:12:03 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
checksum = "ffc92d160b1eef40665be3a05630d003936a3bc7da7421277846c2613e92c71a"
Restructure and make commands uniform
2019-05-22 07:12:03 +00:00
dependencies = [
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"serde 1.0.104",
Restructure and make commands uniform
2019-05-22 07:12:03 +00:00
]
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
[[package]]
name = "tower-service"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e987b6bf443f4b5b3b6f38704195592cca41c5bb7aedd3c3693c7081f8289860"
#194 Added trash crate and send files to the trash using a flag
2019-10-18 22:41:24 +00:00
[[package]]
name = "trash"
version = "1.0.0"
Restructure and make commands uniform
2019-05-22 07:12:03 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "f2f24d31505f49e989b1ee2c03c323251f6763d5907d471b71192dac92e323f8"
Restructure and make commands uniform
2019-05-22 07:12:03 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"winapi 0.3.8",
Restructure and make commands uniform
2019-05-22 07:12:03 +00:00
]
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
[[package]]
name = "try-lock"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e604eb7b43c06650e854be16a2a03155743d3752dd1c943f6829e26b7a36e382"
--no-edit
2019-11-04 15:47:03 +00:00
[[package]]
name = "typed-arena"
version = "1.7.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "a9b2228007eba4120145f785df0f6c92ea538f5a3635a612ecf4e334c8c1446d"
--no-edit
2019-11-04 15:47:03 +00:00
add some battery stats
2019-08-11 03:01:09 +00:00
[[package]]
name = "typenum"
Fix #811 (#813)
2019-10-13 04:53:58 +00:00
version = "1.11.2"
add some battery stats
2019-08-11 03:01:09 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "6d2783fe2d6b8c1101136184eb41be8b1ad379e4657050b8aaff0c79ee7575f9"
add some battery stats
2019-08-11 03:01:09 +00:00
Extract core stuff into own crates This commit extracts five new crates: - nu-source, which contains the core source-code handling logic in Nu, including Text, Span, and also the pretty.rs-based debug logic - nu-parser, which is the parser and expander logic - nu-protocol, which is the bulk of the types and basic conveniences used by plugins - nu-errors, which contains ShellError, ParseError and error handling conveniences - nu-textview, which is the textview plugin extracted into a crate One of the major consequences of this refactor is that it's no longer possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so a lot of types became more concrete (Value became a concrete type instead of Spanned<Value>, for example). This also turned a number of inherent methods in the main nu crate into plain functions (impl Value {} became a bunch of functions in the `value` namespace in `crate::data::value`).
2019-11-26 02:30:48 +00:00
[[package]]
name = "typetag"
version = "0.1.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "6ebb2c484029d695fb68a06d80e1536c68d491b3e0cf874c66abed255e831cfe"
Extract core stuff into own crates This commit extracts five new crates: - nu-source, which contains the core source-code handling logic in Nu, including Text, Span, and also the pretty.rs-based debug logic - nu-parser, which is the parser and expander logic - nu-protocol, which is the bulk of the types and basic conveniences used by plugins - nu-errors, which contains ShellError, ParseError and error handling conveniences - nu-textview, which is the textview plugin extracted into a crate One of the major consequences of this refactor is that it's no longer possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so a lot of types became more concrete (Value became a concrete type instead of Spanned<Value>, for example). This also turned a number of inherent methods in the main nu crate into plain functions (impl Value {} became a bunch of functions in the `value` namespace in `crate::data::value`).
2019-11-26 02:30:48 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"erased-serde",
"inventory",
"lazy_static 1.4.0",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"serde 1.0.104",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"typetag-impl",
Extract core stuff into own crates This commit extracts five new crates: - nu-source, which contains the core source-code handling logic in Nu, including Text, Span, and also the pretty.rs-based debug logic - nu-parser, which is the parser and expander logic - nu-protocol, which is the bulk of the types and basic conveniences used by plugins - nu-errors, which contains ShellError, ParseError and error handling conveniences - nu-textview, which is the textview plugin extracted into a crate One of the major consequences of this refactor is that it's no longer possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so a lot of types became more concrete (Value became a concrete type instead of Spanned<Value>, for example). This also turned a number of inherent methods in the main nu crate into plain functions (impl Value {} became a bunch of functions in the `value` namespace in `crate::data::value`).
2019-11-26 02:30:48 +00:00
]
[[package]]
name = "typetag-impl"
version = "0.1.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "b63fd4799e4d0ec5cf0b055ebb8e2c3a657bbf76a84f6edc77ca60780e000204"
Extract core stuff into own crates This commit extracts five new crates: - nu-source, which contains the core source-code handling logic in Nu, including Text, Span, and also the pretty.rs-based debug logic - nu-parser, which is the parser and expander logic - nu-protocol, which is the bulk of the types and basic conveniences used by plugins - nu-errors, which contains ShellError, ParseError and error handling conveniences - nu-textview, which is the textview plugin extracted into a crate One of the major consequences of this refactor is that it's no longer possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so a lot of types became more concrete (Value became a concrete type instead of Spanned<Value>, for example). This also turned a number of inherent methods in the main nu crate into plain functions (impl Value {} became a bunch of functions in the `value` namespace in `crate::data::value`).
2019-11-26 02:30:48 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"proc-macro2",
"quote",
"syn",
Extract core stuff into own crates This commit extracts five new crates: - nu-source, which contains the core source-code handling logic in Nu, including Text, Span, and also the pretty.rs-based debug logic - nu-parser, which is the parser and expander logic - nu-protocol, which is the bulk of the types and basic conveniences used by plugins - nu-errors, which contains ShellError, ParseError and error handling conveniences - nu-textview, which is the textview plugin extracted into a crate One of the major consequences of this refactor is that it's no longer possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so a lot of types became more concrete (Value became a concrete type instead of Spanned<Value>, for example). This also turned a number of inherent methods in the main nu crate into plain functions (impl Value {} became a bunch of functions in the `value` namespace in `crate::data::value`).
2019-11-26 02:30:48 +00:00
]
Add umask to unix --full list
2019-11-19 05:46:47 +00:00
[[package]]
name = "umask"
version = "0.1.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "d3ec2e5aeb4aadd510db9124513a7fec4a9c3a331b7f57aa519440dab3707067"
Add umask to unix --full list
2019-11-19 05:46:47 +00:00
Add opening urls
2019-06-08 18:09:17 +00:00
[[package]]
name = "unicase"
Merge master
2019-11-16 17:17:05 +00:00
version = "2.6.0"
Add opening urls
2019-06-08 18:09:17 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "50f37be617794602aabbeee0be4f259dc1778fabe05e2d67ee8f79326d5cb4f6"
Add opening urls
2019-06-08 18:09:17 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"version_check 0.9.1",
Add opening urls
2019-06-08 18:09:17 +00:00
]
Add git branch to prompt
2019-06-01 21:11:28 +00:00
[[package]]
name = "unicode-bidi"
version = "0.3.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "49f2bd0c6468a8230e1db229cff8029217cf623c767ea5d60bfbd42729ea54d5"
Add git branch to prompt
2019-06-01 21:11:28 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"matches",
Add git branch to prompt
2019-06-01 21:11:28 +00:00
]
[[package]]
name = "unicode-normalization"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.1.12"
Add git branch to prompt
2019-06-01 21:11:28 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "5479532badd04e128284890390c1e876ef7a993d0570b3597ae43dfa1d59afa4"
Add git branch to prompt
2019-06-01 21:11:28 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"smallvec",
Add git branch to prompt
2019-06-01 21:11:28 +00:00
]
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "unicode-segmentation"
Merge master
2019-11-16 17:17:05 +00:00
version = "1.6.0"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "e83e153d1053cbb5a118eeff7fd5be06ed99153f00dbcd8ae310c5fb2b22edc0"
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "unicode-width"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
version = "0.1.7"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
checksum = "caaa9d531767d1ff2150b9332433f32a24622147e5ebb1f26409d5da67afd479"
objectshell initial commit
2019-05-10 16:59:12 +00:00
bump deps
2019-07-29 07:46:24 +00:00
[[package]]
name = "unicode-xid"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "826e7639553986605ec5979c7dd957c7895e93eabed50ab2ffa7f6128a75097c"
bump deps
2019-07-29 07:46:24 +00:00
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
[[package]]
name = "untrusted"
version = "0.7.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "60369ef7a31de49bcb3f6ca728d4ba7300d9a1658f94c727d4cab8c8d9f4aece"
Update to heim v0.0.7.
2019-08-28 15:53:59 +00:00
[[package]]
name = "uom"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
version = "0.26.0"
Update to heim v0.0.7.
2019-08-28 15:53:59 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "4cec796ec5f7ac557631709079168286056205c51c60aac33f51764bdc7b8dc4"
Update to heim v0.0.7.
2019-08-28 15:53:59 +00:00
dependencies = [
Bump heim and necessary deps
2019-12-14 13:27:14 +00:00
"num-rational",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"num-traits 0.2.11",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"typenum",
Update to heim v0.0.7.
2019-08-28 15:53:59 +00:00
]
bump deps
2019-07-29 07:46:24 +00:00
[[package]]
name = "url"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
version = "2.1.1"
bump deps
2019-07-29 07:46:24 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
checksum = "829d4a8476c35c9bf0bbce5a3b23f4106f79728039b726d292bb93bc106787cb"
bump deps
2019-07-29 07:46:24 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"idna",
"matches",
"percent-encoding",
bump deps
2019-07-29 07:46:24 +00:00
]
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
[[package]]
name = "urlencoding"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3df3561629a8bb4c57e5a2e4c43348d9e29c7c29d9b1c4c1f47166deca8f37ed"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
[[package]]
name = "user32-sys"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "4ef4711d107b21b410a3a974b1204d9accc8b10dad75d8324b5d755de1617d47"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"winapi 0.2.8",
"winapi-build",
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
]
A few ls improvements. New welcome message (#1195)
2020-01-11 20:49:20 +00:00
[[package]]
name = "users"
version = "0.9.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c72f4267aea0c3ec6d07eaabea6ead7c5ddacfafc5e22bcf8d186706851fb4cf"
dependencies = [
"libc",
]
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "utf8parse"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "8772a4ccbb4e89959023bc5b7cb8623a795caa7092d99f3aa9501b9484d4557d"
objectshell initial commit
2019-05-10 16:59:12 +00:00
Add git branch to prompt
2019-06-01 21:11:28 +00:00
[[package]]
name = "vcpkg"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
version = "0.2.8"
Add git branch to prompt
2019-06-01 21:11:28 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "3fc439f2794e98976c88a2a2dafce96b930fe8010b0a256b3c2199a773933168"
Add git branch to prompt
2019-06-01 21:11:28 +00:00
Bat
2019-05-18 01:24:13 +00:00
[[package]]
name = "vec_map"
version = "0.8.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "05c78687fb1a80548ae3250346c3db86a80a7cdd77bda190189f2d0a0987c81a"
Bat
2019-05-18 01:24:13 +00:00
Simple parsing
2019-05-11 04:45:57 +00:00
[[package]]
name = "version_check"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "914b1a6776c4c929a602fafd8bc742e06365d4bcbe48c30f9cca5824f70dc9dd"
Simple parsing
2019-05-11 04:45:57 +00:00
Merge master
2019-11-16 17:17:05 +00:00
[[package]]
name = "version_check"
version = "0.9.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "078775d0255232fb988e6fccf26ddc9d1ac274299aaedcedce21c6f72cc533ce"
Merge master
2019-11-16 17:17:05 +00:00
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "void"
version = "1.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "6a02e4885ed3bc0f2de90ea6dd45ebcbb66dacffe03547fadbb0eeae2770887d"
objectshell initial commit
2019-05-10 16:59:12 +00:00
Give rustyline non-ansi to begin with. Fixes Windows
2019-11-16 20:02:26 +00:00
[[package]]
name = "vte"
version = "0.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "4f42f536e22f7fcbb407639765c8fd78707a33109301f834a594758bedd6e8cf"
Give rustyline non-ansi to begin with. Fixes Windows
2019-11-16 20:02:26 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"utf8parse",
Give rustyline non-ansi to begin with. Fixes Windows
2019-11-16 20:02:26 +00:00
]
Bat
2019-05-18 01:24:13 +00:00
[[package]]
name = "walkdir"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "2.3.1"
Bat
2019-05-18 01:24:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "777182bc735b6424e1a57516d35ed72cb8019d85c8c9bf536dccb3445c1a2f7d"
Bat
2019-05-18 01:24:13 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"same-file",
"winapi 0.3.8",
"winapi-util",
Bat
2019-05-18 01:24:13 +00:00
]
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
[[package]]
name = "want"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1ce8a968cb1cd110d136ff8b819a556d6fb6d919363c61534f6860c7eb172ba0"
dependencies = [
"log",
"try-lock",
]
Fix #811 (#813)
2019-10-13 04:53:58 +00:00
[[package]]
name = "wasi"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.9.0+wasi-snapshot-preview1"
Fix #811 (#813)
2019-10-13 04:53:58 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "cccddf32554fecc6acb585f82a32a72e28b48f8c4c1883ddfeeeaa96f7d8e519"
Fix #811 (#813)
2019-10-13 04:53:58 +00:00
Add opening urls
2019-06-08 18:09:17 +00:00
[[package]]
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
name = "wasm-bindgen"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.2.58"
Add opening urls
2019-06-08 18:09:17 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "5205e9afdf42282b192e2310a5b463a6d1c1d774e30dc3c791ac37ab42d2616c"
Add opening urls
2019-06-08 18:09:17 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"cfg-if",
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
"serde 1.0.104",
"serde_json",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"wasm-bindgen-macro",
Add opening urls
2019-06-08 18:09:17 +00:00
]
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
[[package]]
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
name = "wasm-bindgen-backend"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.2.58"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "11cdb95816290b525b32587d76419facd99662a07e59d3cdb560488a819d9a45"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"bumpalo",
"lazy_static 1.4.0",
"log",
"proc-macro2",
"quote",
"syn",
"wasm-bindgen-shared",
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
]
[[package]]
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
name = "wasm-bindgen-futures"
Fix #811 (#813)
2019-10-13 04:53:58 +00:00
version = "0.3.27"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "83420b37346c311b9ed822af41ec2e82839bfe99867ec6c54e2da43b7538771c"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"cfg-if",
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
"futures 0.1.29",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"futures-channel-preview",
"futures-util-preview",
"js-sys",
"lazy_static 1.4.0",
"wasm-bindgen",
"web-sys",
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
]
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
[[package]]
name = "wasm-bindgen-futures"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.4.8"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "8bbdd49e3e28b40dec6a9ba8d17798245ce32b019513a845369c641b275135d9"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
dependencies = [
"cfg-if",
"js-sys",
"wasm-bindgen",
"web-sys",
]
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
[[package]]
name = "wasm-bindgen-macro"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.2.58"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "574094772ce6921576fb6f2e3f7497b8a76273b6db092be18fc48a082de09dc3"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"quote",
"wasm-bindgen-macro-support",
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
]
[[package]]
name = "wasm-bindgen-macro-support"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.2.58"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "e85031354f25eaebe78bb7db1c3d86140312a911a106b2e29f9cc440ce3e7668"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"proc-macro2",
"quote",
"syn",
"wasm-bindgen-backend",
"wasm-bindgen-shared",
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
]
[[package]]
name = "wasm-bindgen-shared"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.2.58"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "f5e7e61fc929f4c0dddb748b102ebf9f632e2b8d739f2016542b4de2965a9601"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
[[package]]
name = "wasm-bindgen-webidl"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.2.58"
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "ef012a0d93fc0432df126a8eaf547b2dce25a8ce9212e1d3cbeef5c11157975d"
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"anyhow",
"heck",
"log",
"proc-macro2",
"quote",
"syn",
"wasm-bindgen-backend",
"weedle",
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
]
[[package]]
name = "web-sys"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.3.35"
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "aaf97caf6aa8c2b1dac90faf0db529d9d63c93846cca4911856f78a83cebf53b"
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"anyhow",
"js-sys",
"sourcefile",
"wasm-bindgen",
"wasm-bindgen-webidl",
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
]
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
[[package]]
name = "webpki"
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
version = "0.21.2"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 03:46:48 +00:00
checksum = "f1f50e1972865d6b1adb54167d1c8ed48606004c2c9d0ea5f1eeb34d95e863ef"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
dependencies = [
"ring",
"untrusted",
]
[[package]]
name = "webpki-roots"
version = "0.17.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a262ae37dd9d60f60dd473d1158f9fbebf110ba7b6a5051c8160460f6043718b"
dependencies = [
"webpki",
]
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
[[package]]
name = "weedle"
version = "0.10.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "3bb43f70885151e629e2a19ce9e50bd730fd436cfd4b666894c9ce4de9141164"
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"nom 4.2.3",
switch from reqwest to surf
2019-08-24 19:36:19 +00:00
]
Improve shelling out (#1273) Improvements to shelling out
2020-01-23 19:24:31 +00:00
[[package]]
name = "which"
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
version = "3.1.1"
Improve shelling out (#1273) Improvements to shelling out
2020-01-23 19:24:31 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some deps (#1467)
2020-03-08 19:18:44 +00:00
checksum = "d011071ae14a2f6671d0b74080ae0cd8ebf3a6f8c9589a2cd45f23126fe29724"
Improve shelling out (#1273) Improvements to shelling out
2020-01-23 19:24:31 +00:00
dependencies = [
"failure",
"libc",
]
Update plugin protocol for begin, and create new sys plugin
2019-07-27 07:45:00 +00:00
[[package]]
name = "widestring"
version = "0.4.0"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "effc0e4ff8085673ea7b9b2e3c73f6bd4d118810c9009ed8f1e16bd96c331db6"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
Restructure and make commands uniform
2019-05-22 07:12:03 +00:00
[[package]]
name = "winapi"
version = "0.2.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "167dc9d6949a9b857f3451275e911c3f44255842c1f7a76f33c55103a909087a"
Restructure and make commands uniform
2019-05-22 07:12:03 +00:00
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "winapi"
Update to heim v0.0.7.
2019-08-28 15:53:59 +00:00
version = "0.3.8"
objectshell initial commit
2019-05-10 16:59:12 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "8093091eeb260906a183e6ae1abdba2ef5ef2257a21801128899c3fc699229c6"
objectshell initial commit
2019-05-10 16:59:12 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"winapi-i686-pc-windows-gnu",
"winapi-x86_64-pc-windows-gnu",
objectshell initial commit
2019-05-10 16:59:12 +00:00
]
Restructure and make commands uniform
2019-05-22 07:12:03 +00:00
[[package]]
name = "winapi-build"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "2d315eee3b34aca4797b2da6b13ed88266e6d612562a0c46390af8299fc699bc"
Restructure and make commands uniform
2019-05-22 07:12:03 +00:00
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "winapi-i686-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "ac3b87c63620426dd9b991e5ce0329eff545bccbbb34f3be09ff6fb6ab51b7b6"
objectshell initial commit
2019-05-10 16:59:12 +00:00
Bat
2019-05-18 01:24:13 +00:00
[[package]]
name = "winapi-util"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
version = "0.1.3"
Bat
2019-05-18 01:24:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
checksum = "4ccfbf554c6ad11084fb7517daca16cfdcaccbdadba4fc336f032a8b12c2ad80"
Bat
2019-05-18 01:24:13 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"winapi 0.3.8",
Bat
2019-05-18 01:24:13 +00:00
]
objectshell initial commit
2019-05-10 16:59:12 +00:00
[[package]]
name = "winapi-x86_64-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "712e227841d057c1ee1cd2fb22fa7e5a5461ae8e48fa2ca79ec42cfc1931183f"
objectshell initial commit
2019-05-10 16:59:12 +00:00
A real parser (lalrpop)
2019-05-26 06:54:41 +00:00
[[package]]
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
name = "winreg"
version = "0.6.2"
A real parser (lalrpop)
2019-05-26 06:54:41 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
checksum = "b2986deb581c4fe11b621998a5e53361efe6b48a151178d0cd9eeffa4dc6acc9"
A real parser (lalrpop)
2019-05-26 06:54:41 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"winapi 0.3.8",
A real parser (lalrpop)
2019-05-26 06:54:41 +00:00
]
Rewrite `which` (#1144) * Detect built-in commands passed as args to `which` This expands the built-in `which` command to detect nushell commands that may have the same name as a binary in the path. * Allow which to interpret multiple arguments Previously, it would discard any argument besides the first. This allows `which` to process multiple arguments. It also makes the output a stream of rows. * Use map to build the output * Add boolean column for builtins * Use macros for entry creation shortcuts * Process command args and use async_stream In order to use `ichwh`, I'll need to use async_stream. But in order to avoid lifetime errors with that, I have to process the command args before using them. I'll admit I don't fully understand what is going on with the `args.process(...)` function, but it works. * Use `ichwh` for path searching This commit transitions from `which` to `ichwh`. The path search is now done asynchronously. * Enable the `--all` flag on `which` * Make `which` respect external commands Escaped commands passed to wich (e.g., `which "^ls"`), are now searched before builtins. * Fix clippy warnings This commit resolves two warnings from clippy, in light of #1142. * Update Cargo.lock to get new `ichwh` version `ichwh@0.2.1` has support for local paths. * Add documentation for command
2020-01-01 06:45:27 +00:00
[[package]]
name = "ws2_32-sys"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d59cefebd0c892fa2dd6de581e937301d8552cb44489cdff035c6187cb63fa5e"
dependencies = [
"winapi 0.2.8",
"winapi-build",
]
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
[[package]]
name = "x11"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "2.18.2"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "77ecd092546cb16f25783a5451538e73afc8d32e242648d54f4ae5459ba1e773"
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"libc",
"pkg-config",
Switch to rawkey reader. Add more binary reading
2019-07-04 22:17:18 +00:00
]
Add clipboard support
2019-06-07 16:30:50 +00:00
[[package]]
name = "x11-clipboard"
bump deps
2019-07-29 07:46:24 +00:00
version = "0.3.3"
Add clipboard support
2019-06-07 16:30:50 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "89bd49c06c9eb5d98e6ba6536cf64ac9f7ee3a009b2f53996d405b3944f6bcea"
Add clipboard support
2019-06-07 16:30:50 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"xcb",
Add clipboard support
2019-06-07 16:30:50 +00:00
]
[[package]]
name = "xcb"
version = "0.8.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "5e917a3f24142e9ff8be2414e36c649d47d6cc2ba81f16201cdef96e533e02de"
Add clipboard support
2019-06-07 16:30:50 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"libc",
"log",
Add clipboard support
2019-06-07 16:30:50 +00:00
]
Improve signature infrastructure The `config` command uses different kinds of named arguments, which illustrates how it works.
2019-06-01 05:50:16 +00:00
[[package]]
name = "xdg"
version = "2.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "d089681aa106a86fade1b0128fb5daf07d5867a509ab036d99988dec80429a57"
Improve signature infrastructure The `config` command uses different kinds of named arguments, which illustrates how it works.
2019-06-01 05:50:16 +00:00
Bat
2019-05-18 01:24:13 +00:00
[[package]]
name = "xml-rs"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "541b12c998c5b56aa2b4e6f18f03664eef9a4fd0a246a55594efae6cc2d964b5"
Bat
2019-05-18 01:24:13 +00:00
Add xml open support
2019-06-11 06:26:03 +00:00
[[package]]
name = "xmlparser"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
version = "0.13.0"
Add xml open support
2019-06-11 06:26:03 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some of our dependencies (#1234)
2020-01-17 20:35:48 +00:00
checksum = "b16981128b9e811347d0e72c25b2b22773da22b6dc30282846ad50427e89ba97"
Add xml open support
2019-06-11 06:26:03 +00:00
Bat
2019-05-18 01:24:13 +00:00
[[package]]
name = "yaml-rust"
version = "0.4.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
checksum = "65923dd1784f44da1d2c3dbbc5e822045628c590ba72123e1c73d3c230c4434d"
Bat
2019-05-18 01:24:13 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"linked-hash-map 0.5.2",
Bat
2019-05-18 01:24:13 +00:00
]
Add from_xlsx for importing excel files
2019-11-17 03:18:41 +00:00
[[package]]
name = "zip"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
version = "0.5.4"
Add from_xlsx for importing excel files
2019-11-17 03:18:41 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `Cargo.lock` for `ichwh` fix (#1312) `ichwh@0.3.1` fixes a bug that causes path searches to fail. We update `Cargo.lock` to fix this. Resolves #1207
2020-02-01 06:11:42 +00:00
checksum = "e41ff37ba788e2169b19fa70253b70cb53d9f2db9fb9aea9bcfc5047e02c3bae"
Add from_xlsx for importing excel files
2019-11-17 03:18:41 +00:00
dependencies = [
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 02:21:00 +00:00
"crc32fast",
"flate2",
"podio",
]
Reference in a new issue Copy permalink