extern/nushell
1
0
Fork 1
mirror of https://github.com/nushell/nushell.git synced 2024-11-07 17:14:23 +01:00
Code Issues Packages Projects Releases Wiki Activity
763fcbc137
nushell/Cargo.lock

4544 lines
105 KiB
Plaintext
Raw Normal View History

objectshell initial commit
2019-05-10 18:59:12 +02:00
# This file is automatically @generated by Cargo.
# It is not intended for manual editing.
Bat
2019-05-18 03:24:13 +02:00
[[package]]
name = "adler32"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
version = "1.0.4"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
checksum = "5d2e7343e7fc9de883d1b0341e0b13970f764c14101234857d2ddafa1cb1cac2"
Bat
2019-05-18 03:24:13 +02:00
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "aho-corasick"
Pin semver breaking dep
2019-08-08 19:33:19 +02:00
version = "0.7.6"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "58fb5e95d83b38284460a5fda7d6470aa0b8844d283a0b614b8535e880800d2d"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
"memchr",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
Simple parsing
2019-05-11 06:45:57 +02: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 03:21:00 +01:00
checksum = "ee49baf6cb617b853aa8d93bf420db2383fab46d314482ca2803b40d5fde979b"
Simple parsing
2019-05-11 06:45:57 +02: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 03:21:00 +01:00
"winapi 0.3.8",
Simple parsing
2019-05-11 06:45:57 +02:00
]
Bump deps and add serde_bytes support
2019-07-15 20:34:44 +02:00
[[package]]
name = "ansi_term"
Add basic 'did you mean' support
2019-09-13 05:44:21 +02:00
version = "0.12.1"
Bump deps and add serde_bytes support
2019-07-15 20:34:44 +02: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 03:21:00 +01:00
checksum = "d52a9bb7ec0cf484c551830a7ce27bd20d67eac647e1befb56b0be4ee39a55d2"
Bump deps and add serde_bytes support
2019-07-15 20:34:44 +02: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 03:21:00 +01:00
"winapi 0.3.8",
Bump deps and add serde_bytes support
2019-07-15 20:34:44 +02:00
]
Merge master
2019-11-16 18:17:05 +01: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 07:45:27 +01:00
version = "1.0.26"
Merge master
2019-11-16 18:17:05 +01: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 07:45:27 +01:00
checksum = "7825f6833612eb2414095684fcf6c635becf3ce97fe48cf6421321e93bfbd53c"
Merge master
2019-11-16 18:17:05 +01:00
Improve signature infrastructure The `config` command uses different kinds of named arguments, which illustrates how it works.
2019-06-01 07:50:16 +02: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 03:21:00 +01:00
checksum = "e73a24bad9bd6a94d6395382a6c69fe071708ae4409f763c5475e14ee896313d"
Improve signature infrastructure The `config` command uses different kinds of named arguments, which illustrates how it works.
2019-06-01 07:50:16 +02: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 03:21:00 +01: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 07:50:16 +02:00
]
Upgrade crossterm (#1288) * WIP * Finish porting to new crossterm * Fmt
2020-01-27 03:51:46 +01: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 18:59:12 +02:00
[[package]]
Pin semver breaking dep
2019-08-08 19:33:19 +02:00
name = "arrayref"
version = "0.3.5"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "0d382e583f07208808f6b1249e60848879ba3543f57c32277bf52d69c2f0f0ee"
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "arrayvec"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
version = "0.4.12"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "cd9fd44efafa8690358b7408d253adf110036b88f55672a933f01d616ad9b1b9"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
"nodrop",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
Merge master
2019-11-16 18:17:05 +01: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 03:21:00 +01:00
checksum = "cff77d8686867eceff3105329d4698d96c2391c176d5d03adc90c7389162b5b8"
Merge master
2019-11-16 18:17:05 +01: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 07:45:27 +01: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 02:22:17 +02:00
[[package]]
name = "async-stream"
Bump dep versions
2019-11-10 18:48:49 +01:00
version = "0.1.2"
Use async-stream crate to replace most async_stream_block invocations
2019-09-26 02:22:17 +02: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 03:21:00 +01:00
checksum = "fb6fa015ebe961e9908ca4c1854e7dc7aabd4417da77b6a0466e4dfb4c8f6f69"
Use async-stream crate to replace most async_stream_block invocations
2019-09-26 02:22:17 +02: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 03:21:00 +01:00
"async-stream-impl",
"futures-core-preview",
Use async-stream crate to replace most async_stream_block invocations
2019-09-26 02:22:17 +02:00
]
[[package]]
name = "async-stream-impl"
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 03:21:00 +01:00
checksum = "4f0d8c5b411e36dcfb04388bacfec54795726b1f0148adcb0f377a96d6747e0e"
Use async-stream crate to replace most async_stream_block invocations
2019-09-26 02:22:17 +02: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 03:21:00 +01:00
"proc-macro2",
"quote",
"syn",
Use async-stream crate to replace most async_stream_block invocations
2019-09-26 02:22:17 +02: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 07:45:27 +01:00
[[package]]
name = "async-task"
version = "1.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d22dc86693d375d2733b536fd8914bea0fa93adf4b1e6bcbd9c7c500cb62d920"
dependencies = [
"crossbeam-utils 0.7.0",
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "atty"
bump deps
2019-07-29 09:46:24 +02:00
version = "0.2.13"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "1803c647a3ec87095e7ae7acfca019e98de5ec9a7d01343f611cf3152ed71a90"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
"libc",
"winapi 0.3.8",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
[[package]]
name = "autocfg"
Merge master
2019-11-16 18:17:05 +01:00
version = "0.1.7"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "1d49d90015b3c36167a20fe2810c5cd875ad504b39cff3d4eae7977e6b7c1cb2"
objectshell initial commit
2019-05-10 18:59:12 +02:00
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 18:59:12 +02:00
[[package]]
name = "backtrace"
Merge master
2019-11-16 18:17:05 +01:00
version = "0.3.40"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "924c76597f0d9ca25d762c25a4d369d51267536465dc5064bdf0eb073ed477ea"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
"backtrace-sys",
"cfg-if",
"libc",
"rustc-demangle",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
[[package]]
name = "backtrace-sys"
Merge master
2019-11-16 18:17:05 +01:00
version = "0.1.32"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "5d6575f128516de27e3ce99689419835fce9643a9b215a14d2b5b685be018491"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
"cc",
"libc",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
checksum = "0b25d992356d2eb0ed82172f5248873db5560c4721f564b13cb5193bda5e668e"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
"byteorder",
Bat
2019-05-18 03:24:13 +02:00
]
Bump dep versions
2019-11-10 18:48:49 +01: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 03:21:00 +01:00
checksum = "b41b7ea54a0c9d92199de89e20e58d49f02f8e699814ef3fdf266f6f748d15c7"
Bump dep versions
2019-11-10 18:48:49 +01:00
add some battery stats
2019-08-11 05:01:09 +02: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 03:21:00 +01:00
version = "0.7.5"
add some battery stats
2019-08-11 05:01:09 +02: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 03:21:00 +01:00
checksum = "36a698e449024a5d18994a815998bf5e2e4bc1883e35a7d7ba95b6b69ee45907"
add some battery stats
2019-08-11 05:01:09 +02: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 03:21:00 +01:00
"cfg-if",
Bump heim and necessary deps
2019-12-14 14:27:14 +01: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 03:21:00 +01:00
"lazycell",
"libc",
"mach 0.2.3",
"nix 0.15.0",
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
"num-traits 0.2.11",
Bump heim and necessary deps
2019-12-14 14:27:14 +01: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 03:21:00 +01:00
"winapi 0.3.8",
add some battery stats
2019-08-11 05:01:09 +02: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 18:20:31 +02: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 03:21:00 +01: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 18:20:31 +02: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 03:21:00 +01:00
"num-bigint",
"num-integer",
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 07:45:27 +01: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 18:20:31 +02:00
]
Bat
2019-05-18 03:24:13 +02:00
[[package]]
name = "bincode"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
version = "1.2.1"
Bat
2019-05-18 03:24:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
checksum = "5753e2a71534719bf3f4e57006c3a4f0d2c672a4b676eec84161f763eca87dbf"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01: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 07:45:27 +01:00
"serde 1.0.104",
Bat
2019-05-18 03:24:13 +02:00
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "bitflags"
Merge master
2019-11-16 18:17:05 +01:00
version = "1.2.1"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "cf1de2fe8c75bc145a2f577add951f8134889b4795d47466a54a5c846d691693"
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
Pin semver breaking dep
2019-08-08 19:33:19 +02:00
name = "blake2b_simd"
Merge master
2019-11-16 18:17:05 +01:00
version = "0.5.9"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "b83b7baab1e671718d78204225800d6b170e648188ac7dc992e9d6bddf87d0c0"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
"arrayref",
"arrayvec 0.5.1",
"constant_time_eq",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
Add clipboard support
2019-06-07 18:30:50 +02: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 03:21:00 +01:00
checksum = "0d8c1fef690941d3e7788d328517591fecc684c084084702d6ff1641e993699a"
Add clipboard support
2019-06-07 18:30:50 +02:00
Rebase on master
2019-08-25 15:57:47 +02:00
[[package]]
name = "bson"
Update bson to 0.14
2019-08-31 16:22:45 +02:00
version = "0.14.0"
Rebase on master
2019-08-25 15:57:47 +02: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 03:21:00 +01:00
checksum = "d61895d21e2194d1ce1d434cff69025daac1e49a8b4698eb04b05722dbc08b33"
Rebase on master
2019-08-25 15:57:47 +02: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 03:21:00 +01: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 07:45:27 +01: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 03:21:00 +01:00
"serde_json",
"time",
Rebase on master
2019-08-25 15:57:47 +02:00
]
Introduced ability to open csv documents.
2019-07-19 22:11:49 +02:00
[[package]]
name = "bstr"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
version = "0.2.8"
Introduced ability to open csv documents.
2019-07-19 22:11:49 +02: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 03:21:00 +01:00
checksum = "8d6c2c5b58ab920a4f5aeaaca34b4488074e8cc7596af94e6f8c6ff247c60245"
Introduced ability to open csv documents.
2019-07-19 22:11:49 +02: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 03:21:00 +01: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 07:45:27 +01:00
"serde 1.0.104",
Introduced ability to open csv documents.
2019-07-19 22:11:49 +02:00
]
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
[[package]]
name = "bumpalo"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
version = "2.6.0"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02: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 03:21:00 +01:00
checksum = "ad807f2fc2bf185eeb98ff3a901bd46dc5ad58163d0fa4577ba0d25674d71708"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
Internals cleanup and | select ...fields
2019-05-15 20:14:51 +02: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 15:47:30 +02:00
version = "3.0.3"
Internals cleanup and | select ...fields
2019-05-15 20:14:51 +02: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 03:21:00 +01:00
checksum = "6894a79550807490d9f19a138a6da0f8830e70c83e83402dd23f16fd6c479056"
Internals cleanup and | select ...fields
2019-05-15 20:14:51 +02:00
Start rebuilding lite parser using nom
2019-06-11 07:53:04 +02: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 03:21:00 +01:00
checksum = "f861d9ce359f56dbcb6e0c2a1cb84e52ad732cadb57b806adeb3c7668caccbd8"
Start rebuilding lite parser using nom
2019-06-11 07:53:04 +02:00
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "byteorder"
Merge master
2019-06-22 03:38:17 +02:00
version = "1.3.2"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "a7c3dd8985a7111efc5c80b44e23ecdd8c007de8ade3b96595387e812b957cf5"
objectshell initial commit
2019-05-10 18:59:12 +02:00
Pipe external to internal Each line is a string object
2019-05-24 20:48:33 +02: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 03:21:00 +01:00
checksum = "206fdffcfa2df7cbe15601ef46c813fce0965eb3286db6b56c583b814b51c81c"
Pipe external to internal Each line is a string object
2019-05-24 20:48:33 +02: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 03:21:00 +01:00
"byteorder",
"iovec",
Pipe external to internal Each line is a string object
2019-05-24 20:48:33 +02:00
]
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
[[package]]
name = "bytes"
version = "0.5.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "10004c15deb332055f7a4a208190aed362cf9a7c2f6ab70a305fba50e1105f38"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
[[package]]
name = "c2-chacha"
Merge master
2019-11-16 18:17:05 +01:00
version = "0.2.3"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02: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 03:21:00 +01:00
checksum = "214238caa1bf3a496ec3392968969cab8549f96ff30652c9e56885329315f6bb"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02: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 03:21:00 +01:00
"ppv-lite86",
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
]
Add from_xlsx for importing excel files
2019-11-17 04:18:41 +01: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 03:21:00 +01:00
version = "0.16.1"
Add from_xlsx for importing excel files
2019-11-17 04:18:41 +01: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 03:21:00 +01:00
checksum = "abc39da027ec520445e6e526f105170b424ca68ea9e53553d3e6a29df41713ba"
Add from_xlsx for importing excel files
2019-11-17 04:18:41 +01: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 03:21:00 +01: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 07:45:27 +01: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 03:21:00 +01:00
"zip",
Add from_xlsx for importing excel files
2019-11-17 04:18:41 +01:00
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "cc"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
version = "1.0.48"
objectshell initial commit
2019-05-10 18:59:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
checksum = "f52a465a666ca3d838ebbf08b241383421412fe7ebb463527bba275526d89f76"
Add basic 'did you mean' support
2019-09-13 05:44:21 +02: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 03:21:00 +01:00
"jobserver",
"num_cpus",
Add basic 'did you mean' support
2019-09-13 05:44:21 +02:00
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "cfg-if"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
version = "0.1.10"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "4785bdd1c96b2a846b2bd7cc02e86b6b3dbf14e7e53446c4f54c92a361040822"
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "chrono"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
version = "0.4.10"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "31850b4a4d6bae316f7a09e691c944c28299298837edc0a03f755618c23cbc01"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
"num-integer",
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 07:45:27 +01: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 03:21:00 +01:00
"time",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
checksum = "5067f5bb2d80ef5d68b4c87db81601f0b75bca627bc2ef76b141d7b846a3c6d9"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
"ansi_term 0.11.0",
"atty",
"bitflags",
"strsim",
"textwrap",
"unicode-width",
"vec_map",
Bat
2019-05-18 03:24:13 +02:00
]
Add clipboard support
2019-06-07 18:30:50 +02: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 03:21:00 +01:00
checksum = "25a904646c0340239dcf7c51677b33928bf24fdf424b79a57909c0109075b2e7"
Add clipboard support
2019-06-07 18:30:50 +02: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 03:21:00 +01:00
"clipboard-win",
"objc",
"objc-foundation",
"objc_id",
"x11-clipboard",
Add clipboard support
2019-06-07 18:30:50 +02: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 03:21:00 +01:00
checksum = "e3a093d6fed558e5fe24c3dfc85a68bb68f1c824f440d3ba5aca189e2998786b"
Add clipboard support
2019-06-07 18:30:50 +02: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 03:21:00 +01:00
"winapi 0.3.8",
Add clipboard support
2019-06-07 18:30:50 +02:00
]
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "ddfc5b9aa5d4507acaf872de71051dfd0e309860e88966e1051e462a077aac4f"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
"bitflags",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
Add from_xlsx for importing excel files
2019-11-17 04:18:41 +01: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 03:21:00 +01:00
checksum = "8b0e9222c0cdf2c6ac27d73f664f9520266fa911c3106329d359f8861cb8bde9"
Add from_xlsx for importing excel files
2019-11-17 04:18:41 +01: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 03:21:00 +01:00
"encoding_rs",
Add from_xlsx for importing excel files
2019-11-17 04:18:41 +01:00
]
Add tree sink
2019-06-07 09:50:26 +02: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 03:21:00 +01:00
checksum = "f9107d78ed62b3fa5a86e7d18e647abed48cfd8f8fab6c72f4cdb982d196f7e6"
Add tree sink
2019-06-07 09:50:26 +02: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 03:21:00 +01: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 07:45:27 +01: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 03:21:00 +01:00
"serde-hjson 0.8.2",
"serde_json",
"toml 0.4.10",
"yaml-rust",
Add tree sink
2019-06-07 09:50:26 +02:00
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "constant_time_eq"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
version = "0.1.4"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "995a44c877f9212528ccc74b21a232f66ad69001e40ede5bcee2ac9ef2657120"
objectshell initial commit
2019-05-10 18:59:12 +02:00
Add opening urls
2019-06-08 20:09:17 +02: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 03:21:00 +01:00
checksum = "25b9e03f145fd4f2bf705e07b900cd41fc636598fe5dc452fd0db1441c3f496d"
Add opening urls
2019-06-08 20:09:17 +02:00
dependencies = [
Bump heim and necessary deps
2019-12-14 14:27:14 +01: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 03:21:00 +01:00
"libc",
Add opening urls
2019-06-08 20:09:17 +02: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 03:21:00 +01:00
checksum = "e7ca8a5221364ef15ce201e8ed2f609fc312682a8f4e0e3d4aa5879764e0fa3b"
Add opening urls
2019-06-08 20:09:17 +02:00
Bump heim and necessary deps
2019-12-14 14:27:14 +01: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 03:24:13 +02: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 03:21:00 +01:00
checksum = "ba125de2af0df55319f41944744ad91c71113bf74a4646efff39afe1f6842db1"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
"cfg-if",
Bat
2019-05-18 03:24:13 +02:00
]
Pin semver breaking dep
2019-08-08 19:33:19 +02: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 03:21:00 +01:00
checksum = "c8ec7fcd21571dc78f96cc96243cab8d8f035247c3efd16c687be154c3fa9efa"
Pin semver breaking dep
2019-08-08 19:33:19 +02: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 03:21:00 +01:00
"crossbeam-utils 0.6.6",
Restructure and make commands uniform
2019-05-22 09:12:03 +02: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 07:45:27 +01: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 15:47:30 +02:00
[[package]]
name = "crossbeam-deque"
Merge master
2019-11-16 18:17:05 +01: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 15:47:30 +02: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 03:21:00 +01: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 15:47:30 +02: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 03:21:00 +01: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 15:47:30 +02:00
]
[[package]]
name = "crossbeam-epoch"
Merge master
2019-11-16 18:17:05 +01: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 15:47:30 +02: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 03:21:00 +01: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 15:47:30 +02:00
dependencies = [
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 03:21:00 +01: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 15:47:30 +02: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 07:45:27 +01: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 15:47:30 +02: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 07:45:27 +01: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 15:47:30 +02: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 07:45:27 +01: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 03:21:00 +01: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 15:47:30 +02:00
]
Restructure and make commands uniform
2019-05-22 09:12:03 +02:00
[[package]]
name = "crossbeam-utils"
bump deps
2019-07-29 09:46:24 +02:00
version = "0.6.6"
Restructure and make commands uniform
2019-05-22 09:12:03 +02: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 03:21:00 +01:00
checksum = "04973fa96e96579258a5091af6003abde64af786b860f18622b82e026cca60e6"
Restructure and make commands uniform
2019-05-22 09:12:03 +02: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 03:21:00 +01:00
"cfg-if",
"lazy_static 1.4.0",
Restructure and make commands uniform
2019-05-22 09:12:03 +02:00
]
Merge master
2019-11-16 18:17:05 +01: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 03:21:00 +01:00
checksum = "ce446db02cdc3165b94ae73111e570793400d0794e46125cc4056c81cbb039f4"
Merge master
2019-11-16 18:17:05 +01:00
dependencies = [
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 03:21:00 +01:00
"cfg-if",
"lazy_static 1.4.0",
Restructure and make commands uniform
2019-05-22 09:12:03 +02:00
]
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
[[package]]
name = "crossterm"
Upgrade crossterm (#1288) * WIP * Finish porting to new crossterm * Fmt
2020-01-27 03:51:46 +01:00
version = "0.14.2"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade crossterm (#1288) * WIP * Finish porting to new crossterm * Fmt
2020-01-27 03:51:46 +01:00
checksum = "5750773d74a7dc612eac2ded3f55e9cdeeaa072210cd17c0192aedb48adb3618"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
dependencies = [
Upgrade crossterm (#1288) * WIP * Finish porting to new crossterm * Fmt
2020-01-27 03:51:46 +01:00
"bitflags",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"crossterm_winapi",
Upgrade crossterm (#1288) * WIP * Finish porting to new crossterm * Fmt
2020-01-27 03:51:46 +01: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 03:21:00 +01:00
"libc",
Upgrade crossterm (#1288) * WIP * Finish porting to new crossterm * Fmt
2020-01-27 03:51:46 +01: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 03:21:00 +01:00
"winapi 0.3.8",
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
]
[[package]]
name = "crossterm_winapi"
Upgrade crossterm (#1288) * WIP * Finish porting to new crossterm * Fmt
2020-01-27 03:51:46 +01:00
version = "0.5.1"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade crossterm (#1288) * WIP * Finish porting to new crossterm * Fmt
2020-01-27 03:51:46 +01:00
checksum = "8777c700901e2d5b50c406f736ed6b8f9e43645c7e104ddb74f8bc42b8ae62f6"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02: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 03:21:00 +01:00
"winapi 0.3.8",
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "csv"
Introduced ability to open csv documents.
2019-07-19 22:11:49 +02:00
version = "1.1.1"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "37519ccdfd73a75821cac9319d4fce15a81b9fcf75f951df5b9988aa3a0af87d"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01: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 07:45:27 +01:00
"serde 1.0.104",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
[[package]]
name = "csv-core"
Introduced ability to open csv documents.
2019-07-19 22:11:49 +02:00
version = "0.1.6"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "9b5cadb6b25c77aeff80ba701712494213f4a8418fcda2ee11b6560c3ad0bf4c"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
"memchr",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 17:26:45 +02:00
[[package]]
name = "ctor"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
version = "0.1.12"
Custom lexer
2019-05-29 17:26:45 +02: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 03:21:00 +01:00
checksum = "cd8ce37ad4184ab2ce004c33bf6379185d3b1c95801cab51026bd271bf68eedc"
Custom lexer
2019-05-29 17:26:45 +02: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 03:21:00 +01:00
"quote",
"syn",
Custom lexer
2019-05-29 17:26:45 +02:00
]
Handle Ctrl-C gracefully
2019-06-07 02:31:22 +02:00
[[package]]
name = "ctrlc"
version = "3.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 03:21:00 +01:00
checksum = "c7dfd2d8b4c82121dfdff120f818e09fc4380b0b7e17a742081a89b94853e87f"
Handle Ctrl-C gracefully
2019-06-07 02:31:22 +02: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 03:21:00 +01:00
"nix 0.14.1",
"winapi 0.3.8",
Handle Ctrl-C gracefully
2019-06-07 02:31:22 +02:00
]
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
[[package]]
name = "curl"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
version = "0.4.25"
switch from reqwest to surf
2019-08-24 21:36:19 +02: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 03:21:00 +01:00
checksum = "06aa71e9208a54def20792d877bc663d6aae0732b9852e612c4a933177c31283"
switch from reqwest to surf
2019-08-24 21:36:19 +02: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 03:21:00 +01:00
"curl-sys",
"libc",
"openssl-probe",
"openssl-sys",
"schannel",
"socket2",
"winapi 0.3.8",
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
]
[[package]]
name = "curl-sys"
Merge master
2019-11-16 18:17:05 +01:00
version = "0.4.24"
switch from reqwest to surf
2019-08-24 21:36:19 +02: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 03:21:00 +01:00
checksum = "f659f3ffac9582d6177bb86d1d2aa649f4eb9d0d4de9d03ccc08b402832ea340"
switch from reqwest to surf
2019-08-24 21:36:19 +02: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 03:21:00 +01: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 17:53:59 +02: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 03:21:00 +01:00
checksum = "ade5a88af8d9646bf770687321a9488a0f2b4610aa08b0373016cd1af37f0a31"
Update to heim v0.0.7.
2019-08-28 17:53:59 +02: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 03:21:00 +01:00
"darwin-libproc-sys",
"libc",
"memchr",
Update to heim v0.0.7.
2019-08-28 17:53:59 +02: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 03:21:00 +01:00
checksum = "c30d1a078d74da1183b02fed8a8b07afc412d3998334b53b750d0ed03b031541"
Update to heim v0.0.7.
2019-08-28 17:53:59 +02: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 03:21:00 +01:00
"libc",
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
]
Update bson to 0.14
2019-08-31 16:22:45 +02: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 03:21:00 +01:00
checksum = "e6458723bc760383275fbc02f4c769b2e5f3de782abaf5e7e0b9b7f0368a63ed"
Update bson to 0.14
2019-08-31 16:22:45 +02: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 03:21:00 +01: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 07:45:27 +01:00
"serde 1.0.104",
Update bson to 0.14
2019-08-31 16:22:45 +02:00
]
Add some logic for more binary formats
2019-07-05 09:53:09 +02: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 03:21:00 +01:00
checksum = "707b6a7b384888a70c8d2e8650b3e60170dfc6a67bb4aa67b6dfca57af4bedb4"
Add some logic for more binary formats
2019-07-05 09:53:09 +02: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 03:21:00 +01:00
"adler32",
"byteorder",
Add some logic for more binary formats
2019-07-05 09:53:09 +02:00
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "derive-new"
Random fixes
2019-08-31 23:19:59 +02:00
version = "0.5.8"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "71f31892cd5c62e414316f2963c5689242c43d8e7bbcaaeca97e5e28c95d91d9"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
"proc-macro2",
"quote",
"syn",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
Custom lexer
2019-05-29 17:26:45 +02: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 03:21:00 +01:00
checksum = "524cbf6897b527295dff137cec09ecf3a05f4fddffd7dfcd1585403449e74198"
Custom lexer
2019-05-29 17:26:45 +02:00
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
checksum = "72d337a64190607d4fcca2cb78982c5dd57f4916e19696b48a575fa746b6cb0f"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
"libc",
"winapi 0.3.8",
Bat
2019-05-18 03:24:13 +02:00
]
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "3fd78930633bd1c6e35c4b42b1df7b0cbc6bc191146e512bb3bedf243fcc3901"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
"libc",
"redox_users",
"winapi 0.3.8",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
Lots of misc improvements
2019-06-03 09:41:28 +02:00
[[package]]
name = "dirs"
bump deps
2019-07-29 09:46:24 +02:00
version = "2.0.2"
Lots of misc improvements
2019-06-03 09:41:28 +02: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 03:21:00 +01:00
checksum = "13aea89a5c93364a98e9b37b2fa237effbb694d5cfe01c5b70941f7eb087d5e3"
Lots of misc improvements
2019-06-03 09:41:28 +02: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 03:21:00 +01:00
"cfg-if",
"dirs-sys",
Lots of misc improvements
2019-06-03 09:41:28 +02:00
]
[[package]]
name = "dirs-sys"
bump deps
2019-07-29 09:46:24 +02:00
version = "0.3.4"
Lots of misc improvements
2019-06-03 09:41:28 +02: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 03:21:00 +01:00
checksum = "afa0b23de8fd801745c471deffa6e12d248f962c9fd4b4c33787b055599bde7b"
Lots of misc improvements
2019-06-03 09:41:28 +02: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 03:21:00 +01:00
"cfg-if",
"libc",
"redox_users",
"winapi 0.3.8",
Lots of misc improvements
2019-06-03 09:41:28 +02: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 15:47:30 +02: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 03:21:00 +01: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 15:47:30 +02:00
Lots of misc improvements
2019-06-03 09:41:28 +02:00
[[package]]
name = "dtoa"
version = "0.4.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 03:21:00 +01:00
checksum = "ea57b42383d091c85abcc2706240b94ab2a8fa1fc81c10ff23c4de06e2a90b5e"
Lots of misc improvements
2019-06-03 09:41:28 +02:00
A bit more infra
2019-05-11 09:00:33 +02: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 03:21:00 +01:00
checksum = "d0ad6bf6a88548d1126045c413548df1453d9be094a8ab9fd59bf1fdd338da4f"
A bit more infra
2019-05-11 09:00:33 +02:00
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "either"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
version = "1.5.3"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "bb1f6b1ce1c140482ea30ddd3335fc0024ac7ee112895426e0a629a6c20adfe3"
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "encode_unicode"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
version = "0.3.6"
Add a bunch more tokens and delimited ()
2019-06-12 19:44:45 +02: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 03:21:00 +01:00
checksum = "a357d28ed41a50f9c765dbfe56cbc04a64e53e5fc58ba79fbc34c10ef3df831f"
Add a bunch more tokens and delimited ()
2019-06-12 19:44:45 +02:00
Add from_xlsx for importing excel files
2019-11-17 04:18:41 +01: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 07:45:27 +01:00
version = "0.8.22"
Add from_xlsx for importing excel files
2019-11-17 04:18:41 +01: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 07:45:27 +01:00
checksum = "cd8d03faa7fe0c1431609dfad7bbe827af30f82e1e2ae6f7ee4fca6bd764bc28"
Add from_xlsx for importing excel files
2019-11-17 04:18:41 +01: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 03:21:00 +01:00
"cfg-if",
Add from_xlsx for importing excel files
2019-11-17 04:18:41 +01: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 22:14:52 +01: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 08:54:41 +02:00
[[package]]
name = "env_logger"
bump deps
2019-07-29 09:46:24 +02:00
version = "0.6.2"
A real parser (lalrpop)
2019-05-26 08:54:41 +02: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 03:21:00 +01:00
checksum = "aafcde04e90a5226a6443b7aabdb016ba2f8307c847d524724bd9b346dd1a2d3"
A real parser (lalrpop)
2019-05-26 08:54:41 +02: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 03:21:00 +01:00
"atty",
"humantime",
"log",
"regex",
"termcolor",
A real parser (lalrpop)
2019-05-26 08:54:41 +02: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 03:30:48 +01:00
[[package]]
name = "erased-serde"
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 03:21:00 +01:00
checksum = "3beee4bc16478a1b26f2e80ad819a52d24745e292f521a63c16eea5f74b7eb60"
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 03:30:48 +01: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 07:45:27 +01: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 03:30:48 +01:00
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "failure"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
version = "0.1.6"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "f8273f13c977665c5db7eb2b99ae520952fe5ac831ae4cd09d80c4c7042b5ed9"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
"backtrace",
"failure_derive",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
[[package]]
name = "failure_derive"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
version = "0.1.6"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "0bc225b78e0391e4b8683440bf2e63c2deeeb2ce5189eab46e2b68c6d3725d08"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
"proc-macro2",
"quote",
"syn",
"synstructure",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
Add SQLite support
2019-08-27 23:45:18 +02: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 03:21:00 +01:00
checksum = "4443176a9f2c162692bd3d352d745ef9413eec5782a80d8fd6f8a1ac692a07f7"
Add SQLite support
2019-08-27 23:45:18 +02: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 03:21:00 +01:00
checksum = "7360491ce676a36bf9bb3c56c1aa791658183a54d2744120f27285738d90465a"
Add SQLite support
2019-08-27 23:45:18 +02:00
Add tree sink
2019-06-07 09:50:26 +02: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 03:21:00 +01:00
checksum = "86d4de0081402f5e88cdac65c8dcdcc73118c1a7a465e2a05f0da05843a8ea33"
Add tree sink
2019-06-07 09:50:26 +02:00
Bat
2019-05-18 03:24:13 +02:00
[[package]]
name = "flate2"
Merge master
2019-11-16 18:17:05 +01:00
version = "1.0.13"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
checksum = "6bd6d6f4752952feb71363cffc9ebac9411b75b87c6ab6058c40c8900cf43c0f"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
"cfg-if",
"crc32fast",
"libc",
"miniz_oxide",
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
checksum = "2fad85553e09a6f881f739c29f0b00b0f01357c743266d478b68951ce23285f3"
Bat
2019-05-18 03:24:13 +02:00
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "fuchsia-cprng"
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 03:21:00 +01:00
checksum = "a06f77d526c1a601b7c4cdd98f54b5eaabffc14d5f2f0296febdc7f357c6d3ba"
objectshell initial commit
2019-05-10 18:59:12 +02: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 07:45:27 +01: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 20:48:33 +02:00
[[package]]
name = "futures"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
version = "0.1.29"
Pipe external to internal Each line is a string object
2019-05-24 20:48:33 +02: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 03:21:00 +01:00
checksum = "1b980f2816d6ee8673b6517b52cb0e808a180efc92e5c19d02cdda79066703ef"
Pipe external to internal Each line is a string object
2019-05-24 20:48:33 +02: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 07:45:27 +01:00
[[package]]
name = "futures"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b6f16056ecbb57525ff698bb955162d0cd03bee84e6241c27ff75c08d8ca5987"
dependencies = [
"futures-channel",
"futures-core",
"futures-io",
"futures-sink",
"futures-task",
"futures-util",
]
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
[[package]]
name = "futures-channel"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fcae98ca17d102fd8a3603727b9259fcf7fa4239b603d2142926189bc8999b86"
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 07:45:27 +01:00
"futures-sink",
Bump heim and necessary deps
2019-12-14 14:27:14 +01: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 19:30:51 +02:00
[[package]]
Small restructuring
2019-05-23 06:30:43 +02:00
name = "futures-channel-preview"
Bump dep versions
2019-11-10 18:48:49 +01: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 19:30:51 +02: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 03:21:00 +01:00
checksum = "d5e5f4df964fa9c1c2f8bddeb5c3611631cacd93baf810fc8bb2fb4b495c263a"
Small restructuring
2019-05-23 06:30:43 +02: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 03:21:00 +01:00
"futures-core-preview",
"futures-sink-preview",
Small restructuring
2019-05-23 06:30:43 +02: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 19:30:51 +02:00
--no-edit
2019-11-04 16:47:03 +01:00
[[package]]
name = "futures-core"
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 03:21:00 +01:00
checksum = "79564c427afefab1dfb3298535b21eda083ef7935b4f0ecbfcb121f0aec10866"
--no-edit
2019-11-04 16:47:03 +01: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 19:30:51 +02:00
[[package]]
Small restructuring
2019-05-23 06:30:43 +02:00
name = "futures-core-preview"
Bump dep versions
2019-11-10 18:48:49 +01:00
version = "0.3.0-alpha.19"
Add opening urls
2019-06-08 20:09:17 +02: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 03:21:00 +01:00
checksum = "b35b6263fb1ef523c3056565fa67b1d16f0a8604ff12b11b08c25f28a734c60a"
Add opening urls
2019-06-08 20:09:17 +02:00
Small restructuring
2019-05-23 06:30:43 +02:00
[[package]]
name = "futures-executor-preview"
Bump dep versions
2019-11-10 18:48:49 +01: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 19:30:51 +02: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 03:21:00 +01: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 19:30:51 +02: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 03:21:00 +01:00
"futures-core-preview",
"futures-util-preview",
"num_cpus",
Small restructuring
2019-05-23 06:30:43 +02: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 07:45:27 +01:00
[[package]]
name = "futures-io"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e676577d229e70952ab25f3945795ba5b16d63ca794ca9d2c860e5595d20b5ff"
Small restructuring
2019-05-23 06:30:43 +02:00
[[package]]
name = "futures-io-preview"
Bump dep versions
2019-11-10 18:48:49 +01:00
version = "0.3.0-alpha.19"
Small restructuring
2019-05-23 06:30:43 +02: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 03:21:00 +01:00
checksum = "f4914ae450db1921a56c91bde97a27846287d062087d4a652efc09bb3a01ebda"
Small restructuring
2019-05-23 06:30:43 +02:00
--no-edit
2019-11-04 16:47:03 +01:00
[[package]]
name = "futures-macro"
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 03:21:00 +01:00
checksum = "52e7c56c15537adb4f76d0b7a76ad131cb4d2f4f32d3b0bcabcbe1c7c5e87764"
--no-edit
2019-11-04 16:47:03 +01: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 03:21:00 +01:00
"proc-macro-hack",
"proc-macro2",
"quote",
"syn",
--no-edit
2019-11-04 16:47:03 +01:00
]
Small restructuring
2019-05-23 06:30:43 +02:00
[[package]]
name = "futures-preview"
Bump dep versions
2019-11-10 18:48:49 +01:00
version = "0.3.0-alpha.19"
Small restructuring
2019-05-23 06:30:43 +02: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 03:21:00 +01:00
checksum = "3b1dce2a0267ada5c6ff75a8ba864b4e679a9e2aa44262af7a3b5516d530d76e"
Small restructuring
2019-05-23 06:30:43 +02: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 03:21:00 +01:00
"futures-channel-preview",
"futures-core-preview",
"futures-executor-preview",
"futures-io-preview",
"futures-sink-preview",
"futures-util-preview",
Small restructuring
2019-05-23 06:30:43 +02: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 07:45:27 +01:00
[[package]]
name = "futures-sink"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "171be33efae63c2d59e6dbba34186fe0d6394fb378069a76dfd80fdcffd43c16"
Small restructuring
2019-05-23 06:30:43 +02:00
[[package]]
name = "futures-sink-preview"
Bump dep versions
2019-11-10 18:48:49 +01:00
version = "0.3.0-alpha.19"
Small restructuring
2019-05-23 06:30:43 +02: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 03:21:00 +01:00
checksum = "86f148ef6b69f75bb610d4f9a2336d4fc88c4b5b67129d1a340dd0fd362efeec"
Small restructuring
2019-05-23 06:30:43 +02:00
--no-edit
2019-11-04 16:47:03 +01:00
[[package]]
name = "futures-task"
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 03:21:00 +01:00
checksum = "0bae52d6b29cf440e298856fec3965ee6fa71b06aa7495178615953fd669e5f9"
--no-edit
2019-11-04 16:47:03 +01:00
Experiment with async/await-enabled ps
2019-08-30 21:07:07 +02:00
[[package]]
name = "futures-timer"
Move some plugins back to being core shippable plugins
2019-12-10 01:05:40 +01:00
version = "1.0.3"
Experiment with async/await-enabled ps
2019-08-30 21:07:07 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Move some plugins back to being core shippable plugins
2019-12-10 01:05:40 +01:00
checksum = "7946248e9429ff093345d3e8fdf4eb0f9b2d79091611c9c14f744971a6f8be45"
dependencies = [
"futures-core-preview",
"pin-utils",
]
Experiment with async/await-enabled ps
2019-08-30 21:07:07 +02: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 07:45:27 +01:00
[[package]]
name = "futures-timer"
version = "2.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a1de7508b218029b0f01662ed8f61b1c964b3ae99d6f25462d0f55a595109df6"
--no-edit
2019-11-04 16:47:03 +01:00
[[package]]
name = "futures-util"
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 03:21:00 +01:00
checksum = "c0d66274fb76985d3c62c886d1da7ac4c0903a8c9f754e8fe0f35a6a6cc39e76"
--no-edit
2019-11-04 16:47:03 +01: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 07:45:27 +01: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 03:21:00 +01: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 07:45:27 +01: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 03:21:00 +01: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 07:45:27 +01: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 03:21:00 +01: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 07:45:27 +01: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 03:21:00 +01:00
"pin-utils",
"proc-macro-hack",
"proc-macro-nested",
"slab",
--no-edit
2019-11-04 16:47:03 +01:00
]
Small restructuring
2019-05-23 06:30:43 +02:00
[[package]]
name = "futures-util-preview"
Bump dep versions
2019-11-10 18:48:49 +01:00
version = "0.3.0-alpha.19"
Small restructuring
2019-05-23 06:30:43 +02: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 03:21:00 +01:00
checksum = "5ce968633c17e5f97936bd2797b6e38fb56cf16a7422319f7ec2e30d3c470e8d"
Small restructuring
2019-05-23 06:30:43 +02: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 07:45:27 +01: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 03:21:00 +01: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 20:48:33 +02:00
]
[[package]]
name = "futures_codec"
Restructuring
2019-08-02 21:15:07 +02:00
version = "0.2.5"
Pipe external to internal Each line is a string object
2019-05-24 20:48:33 +02: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 03:21:00 +01:00
checksum = "36552cd31353fd135114510d53b8d120758120c36aa636a9341970f9efb1e4a0"
Pipe external to internal Each line is a string object
2019-05-24 20:48:33 +02:00
dependencies = [
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
"bytes 0.4.12",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"futures-preview",
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 19:30:51 +02: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 15:47:30 +02: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 07:45:27 +01: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 15:47:30 +02: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 07:45:27 +01: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 15:47:30 +02: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 03:21:00 +01: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 15:47:30 +02:00
]
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
[[package]]
name = "getrandom"
Merge master
2019-11-16 18:17:05 +01:00
version = "0.1.13"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02: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 03:21:00 +01:00
checksum = "e7db7ca94ed4cd01190ceee0d8a8052f08a247aa1b469a7f68c6a3b71afcf407"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02: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 03:21:00 +01:00
"cfg-if",
"libc",
"wasi",
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
]
Evaluator MVP (#39) Evaluator, MVP
2019-05-28 08:45:18 +02:00
[[package]]
name = "getset"
Bump dep versions
2019-11-10 18:48:49 +01:00
version = "0.0.9"
Evaluator MVP (#39) Evaluator, MVP
2019-05-28 08:45:18 +02: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 03:21:00 +01:00
checksum = "5bb3f5b7d8d70c9bd23cf29b2b38094661418fb0ea79f1b0cc2019a11d6f5429"
Evaluator MVP (#39) Evaluator, MVP
2019-05-28 08:45:18 +02: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 03:21:00 +01:00
"proc-macro2",
"quote",
"syn",
Evaluator MVP (#39) Evaluator, MVP
2019-05-28 08:45:18 +02: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 03:30:48 +01: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 03:21:00 +01: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 03:30:48 +01: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 03:21:00 +01: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 03:30:48 +01:00
]
Add git branch to prompt
2019-06-01 23:11:28 +02:00
[[package]]
name = "git2"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
version = "0.11.0"
Add git branch to prompt
2019-06-01 23:11:28 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
checksum = "77519ef7c5beee314d0804d4534f01e0f9e8d9acdee2b7a48627e590b27e0ec4"
Add git branch to prompt
2019-06-01 23:11:28 +02: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 03:21:00 +01:00
"bitflags",
"libc",
"libgit2-sys",
"log",
"url",
Add git branch to prompt
2019-06-01 23:11:28 +02:00
]
Update plugin protocol for begin, and create new sys plugin
2019-07-27 09:45:00 +02: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 03:21:00 +01:00
checksum = "9b919933a397b79c37e33b77bb2aa3dc8eb6e165ad809e58ff75bc7db2e34574"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 09:45:00 +02:00
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
[[package]]
name = "h2"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b9433d71e471c1736fd5a61b671fc0b148d7a2992f666c958d03cd8feb3b88d1"
dependencies = [
"bytes 0.5.3",
"fnv",
"futures-core",
"futures-sink",
"futures-util",
"http 0.2.0",
"indexmap",
"log",
"slab",
"tokio",
"tokio-util",
]
Add opening urls
2019-06-08 20:09:17 +02:00
[[package]]
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
name = "heck"
version = "0.3.1"
Add opening urls
2019-06-08 20:09:17 +02: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 03:21:00 +01:00
checksum = "20564e78d53d2bb135c343b3f47714a56af2061f1c928fdb541dc7b9fdd94205"
Add opening urls
2019-06-08 20:09:17 +02: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 03:21:00 +01:00
"unicode-segmentation",
Add opening urls
2019-06-08 20:09:17 +02:00
]
Update plugin protocol for begin, and create new sys plugin
2019-07-27 09:45:00 +02:00
[[package]]
name = "heim"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
version = "0.0.9"
Lots of fixes ahead of release
2019-08-21 08:39:57 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
checksum = "28f11cfed41a4703f8f56ccbe411073c52bd3996d92e3ccac90d36bd0e86e0eb"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 09:45:00 +02: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 03:21:00 +01: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 09:45:00 +02:00
]
[[package]]
name = "heim-common"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
version = "0.0.9"
Lots of fixes ahead of release
2019-08-21 08:39:57 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
checksum = "f97d185137ab6437750cb22a115d4c64027620d48c57893d31720abcba42c388"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 09:45:00 +02: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 03:21:00 +01:00
"cfg-if",
Bump heim and necessary deps
2019-12-14 14:27:14 +01: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 03:21:00 +01: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 07:45:27 +01: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 03:21:00 +01:00
"pin-utils",
Bump heim and necessary deps
2019-12-14 14:27:14 +01: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 03:21:00 +01:00
"winapi 0.3.8",
Update plugin protocol for begin, and create new sys plugin
2019-07-27 09:45:00 +02:00
]
[[package]]
name = "heim-cpu"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
version = "0.0.9"
Lots of fixes ahead of release
2019-08-21 08:39:57 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
checksum = "328091d34621a28af550523e1c139749fa4bc4590a8ea91b160a0f4b82dd8b06"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 09:45:00 +02: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 03:21:00 +01: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 09:45:00 +02:00
]
[[package]]
name = "heim-derive"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
version = "0.0.9"
Lots of fixes ahead of release
2019-08-21 08:39:57 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
checksum = "dc97d9bf8ca9af8a02a533acea548756f23d4759474a1df8e79eb2b57f3cf7ac"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 09:45:00 +02: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 03:21:00 +01:00
"proc-macro2",
"quote",
"syn",
Update plugin protocol for begin, and create new sys plugin
2019-07-27 09:45:00 +02:00
]
[[package]]
name = "heim-disk"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
version = "0.0.9"
Lots of fixes ahead of release
2019-08-21 08:39:57 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
checksum = "82179359c7b215ae46fe8ac0f9015b8e5dfd6368cd0d113f261b28cb8993713f"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 09:45:00 +02: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 03:21:00 +01:00
"bitflags",
"cfg-if",
Bump heim and necessary deps
2019-12-14 14:27:14 +01: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 03:21:00 +01: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 09:45:00 +02:00
]
[[package]]
name = "heim-host"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
version = "0.0.9"
Lots of fixes ahead of release
2019-08-21 08:39:57 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
checksum = "64b9c8c5f7d1479102a503e3f233241bfb819bf916f02b15e10ba5fbfee7a7f3"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 09:45:00 +02: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 03:21:00 +01: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 09:45:00 +02:00
]
[[package]]
name = "heim-memory"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
version = "0.0.9"
Lots of fixes ahead of release
2019-08-21 08:39:57 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
checksum = "d04e9e068b57049062622cf4a182a45f320459e266c39dfc52ca65fc8c178e3a"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 09:45:00 +02: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 03:21:00 +01: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 09:45:00 +02:00
]
[[package]]
name = "heim-net"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
version = "0.0.9"
Lots of fixes ahead of release
2019-08-21 08:39:57 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
checksum = "4c6323430ecae9b74378b37d0078768989c98b570daacec1d899737d90d72a5b"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 09:45:00 +02: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 03:21:00 +01: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 07:45:27 +01:00
"nix 0.16.1",
Update plugin protocol for begin, and create new sys plugin
2019-07-27 09:45:00 +02:00
]
[[package]]
name = "heim-process"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
version = "0.0.9"
Lots of fixes ahead of release
2019-08-21 08:39:57 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
checksum = "b20a58b335dc9837088b2c9290822b55c661071cb542f0002e62ed18e8464379"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 09:45:00 +02: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 03:21:00 +01: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 09:45:00 +02:00
]
Pin semver breaking dep
2019-08-08 19:33:19 +02:00
[[package]]
name = "heim-runtime"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
version = "0.0.5"
Lots of fixes ahead of release
2019-08-21 08:39:57 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
checksum = "f87591c7b202868445a7da04b3d8f987b0672dd68c3d66e24fe8f759171dd612"
Pin semver breaking dep
2019-08-08 19:33:19 +02: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 03:21:00 +01:00
"cfg-if",
Bump heim and necessary deps
2019-12-14 14:27:14 +01: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 03:21:00 +01:00
"heim-common",
"lazy_static 1.4.0",
"threadpool",
Pin semver breaking dep
2019-08-08 19:33:19 +02:00
]
Update to heim v0.0.7.
2019-08-28 17:53:59 +02:00
[[package]]
name = "heim-sensors"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
version = "0.0.4"
Update to heim v0.0.7.
2019-08-28 17:53:59 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
checksum = "6f663425e6ed38a6356ee5751a2ebae421f7449fd0507b7e698c7e1e9fabee0c"
Update to heim v0.0.7.
2019-08-28 17:53:59 +02: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 03:21:00 +01:00
"cfg-if",
"heim-common",
"heim-derive",
"heim-runtime",
Update to heim v0.0.7.
2019-08-28 17:53:59 +02:00
]
Update plugin protocol for begin, and create new sys plugin
2019-07-27 09:45:00 +02:00
[[package]]
name = "heim-virt"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
version = "0.0.9"
Lots of fixes ahead of release
2019-08-21 08:39:57 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
checksum = "7dd975e9ca42170c0f65102b867e69c3d060027f9bb02fb29cc554f7a0e5680b"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 09:45:00 +02: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 03:21:00 +01:00
"cfg-if",
"heim-common",
"heim-runtime",
"raw-cpuid",
Update plugin protocol for begin, and create new sys plugin
2019-07-27 09:45:00 +02:00
]
Merge master
2019-11-16 18:17:05 +01:00
[[package]]
name = "hermit-abi"
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 07:45:27 +01:00
version = "0.1.5"
Merge master
2019-11-16 18:17:05 +01: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 07:45:27 +01:00
checksum = "f629dc602392d3ec14bfc8a09b5e644d7ffd725102b48b81e59f90f2633621d7"
Merge master
2019-11-16 18:17:05 +01: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 03:21:00 +01:00
"libc",
Merge master
2019-11-16 18:17:05 +01:00
]
Update plugin protocol for begin, and create new sys plugin
2019-07-27 09:45:00 +02: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 03:21:00 +01:00
checksum = "805026a5d0141ffc30abb3be3173848ad46a1b1664fe632428479619a3644d77"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 09:45:00 +02:00
Add Cargo.lock
2019-09-24 21:02:35 +02: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 03:21:00 +01:00
checksum = "023b39be39e3a2da62a94feb433e91e8bcd37676fbc8bea371daf52b7a769a3e"
Add Cargo.lock
2019-09-24 21:02:35 +02:00
Add opening urls
2019-06-08 20:09:17 +02: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 01:34:33 +01:00
version = "0.1.21"
Add opening urls
2019-06-08 20:09:17 +02: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 01:34:33 +01:00
checksum = "d6ccf5ede3a895d8856620237b2f02972c1bbc78d2965ad7fe8838d4a0ed41f0"
Add opening urls
2019-06-08 20:09:17 +02:00
dependencies = [
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 = [
"bytes 0.5.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 03:21:00 +01:00
"fnv",
"itoa",
Add opening urls
2019-06-08 20:09:17 +02:00
]
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
[[package]]
name = "http-body"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "13d5ff830006f7646652e057693569bfe0d51760c0085a071769d142a205111b"
dependencies = [
"bytes 0.5.3",
"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 03:24:13 +02:00
[[package]]
name = "humantime"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
version = "1.3.0"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
checksum = "df004cfca50ef23c36850aaaa59ad52cc70d0e90243c3c7737a4dd32dc7a3c4f"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
"quick-error",
Bat
2019-05-18 03:24:13 +02:00
]
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
[[package]]
name = "hyper"
version = "0.13.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8bf49cfb32edee45d890537d9057d1b02ed55f53b7b6a30bae83a38c9231749e"
dependencies = [
"bytes 0.5.3",
"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"
version = "0.19.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b89109920197f2c90d75e82addbb96bf424570790d310cc2b18f0b33f4a9cc43"
dependencies = [
"bytes 0.5.3",
"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 07:45:27 +01:00
[[package]]
name = "ichwh"
Update `ichwh` to 3.0 (#1267) The [newest update for ichwh][changes] introduced some breaking changes. This PR bumps the version and refactors the `which` command to take these into account. [changes]: https://gitlab.com/avandesa/ichwh-rs/blob/master/CHANGELOG.md#030-2020-01-22
2020-01-23 00:26:49 +01:00
version = "0.3.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 07:45:27 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update `ichwh` to 3.0 (#1267) The [newest update for ichwh][changes] introduced some breaking changes. This PR bumps the version and refactors the `which` command to take these into account. [changes]: https://gitlab.com/avandesa/ichwh-rs/blob/master/CHANGELOG.md#030-2020-01-22
2020-01-23 00:26:49 +01:00
checksum = "ec27ed05786e59eb2e012b8693ab59abda5d76c7578ef1cde2eb5ff631c342ce"
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 07:45:27 +01:00
dependencies = [
"async-std",
"cfg-if",
"futures 0.3.1",
"thiserror",
]
bump deps
2019-07-29 09:46:24 +02: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 03:21:00 +01:00
checksum = "02e2673c30ee86b5b96a9cb52ad15718aa1f966f5ab9ad54a8b95d5ca33120a9"
bump deps
2019-07-29 09:46:24 +02: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 03:21:00 +01:00
"matches",
"unicode-bidi",
"unicode-normalization",
bump deps
2019-07-29 09:46:24 +02:00
]
Add some logic for more binary formats
2019-07-05 09:53:09 +02:00
[[package]]
name = "image"
Upgrade crossterm (#1288) * WIP * Finish porting to new crossterm * Fmt
2020-01-27 03:51:46 +01:00
version = "0.22.4"
Add some logic for more binary formats
2019-07-05 09:53:09 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade crossterm (#1288) * WIP * Finish porting to new crossterm * Fmt
2020-01-27 03:51:46 +01:00
checksum = "53cb19c4e35102e5c6fb9ade5e0e236c5588424dc171a849af3141bf0b47768a"
Add some logic for more binary formats
2019-07-05 09:53:09 +02: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 03:21:00 +01:00
"byteorder",
"jpeg-decoder",
"num-iter",
"num-rational",
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 03:21:00 +01:00
"png",
Add some logic for more binary formats
2019-07-05 09:53:09 +02:00
]
Internals cleanup and | select ...fields
2019-05-15 20:14:51 +02:00
[[package]]
name = "indexmap"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
version = "1.3.1"
Internals cleanup and | select ...fields
2019-05-15 20:14:51 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
checksum = "0b54058f0a6ff80b6803da8faf8997cde53872b38f4023728f6830b06cd3c0dc"
Improve signature infrastructure The `config` command uses different kinds of named arguments, which illustrates how it works.
2019-06-01 07:50:16 +02:00
dependencies = [
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 07:45:27 +01: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 07:50:16 +02:00
]
Internals cleanup and | select ...fields
2019-05-15 20:14:51 +02:00
Add some logic for more binary formats
2019-07-05 09:53:09 +02: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 03:21:00 +01:00
checksum = "1cdb29978cc5797bd8dcc8e5bf7de604891df2a8dc576973d71a281e916db2ff"
Add some logic for more binary formats
2019-07-05 09:53:09 +02: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 03:21:00 +01:00
"adler32",
Add some logic for more binary formats
2019-07-05 09:53:09 +02: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 03:30:48 +01: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 07:45:27 +01: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 03:30:48 +01: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 07:45:27 +01: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 03:30:48 +01: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 03:21:00 +01: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 03:30:48 +01: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 07:45:27 +01: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 03:30:48 +01: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 07:45:27 +01: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 03:30:48 +01: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 03:21:00 +01: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 03:30:48 +01:00
]
Pipe external to internal Each line is a string object
2019-05-24 20:48:33 +02:00
[[package]]
name = "iovec"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
version = "0.1.4"
Pipe external to internal Each line is a string object
2019-05-24 20:48:33 +02: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 03:21:00 +01:00
checksum = "b2b3ea6ff95e175473f8ffe6a7eb7c00d054240321b84c57051175fe3c1e075e"
Pipe external to internal Each line is a string object
2019-05-24 20:48:33 +02: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 03:21:00 +01:00
"libc",
Pipe external to internal Each line is a string object
2019-05-24 20:48:33 +02:00
]
Update futures-preview to 0.3.0-alpha.18
2019-08-29 15:42:49 +02:00
[[package]]
name = "isahc"
Merge master
2019-11-16 18:17:05 +01:00
version = "0.7.6"
Update futures-preview to 0.3.0-alpha.18
2019-08-29 15:42:49 +02: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 03:21:00 +01:00
checksum = "17b77027f12e53ae59a379f7074259d32eb10867e6183388020e922832d9c3fb"
Update futures-preview to 0.3.0-alpha.18
2019-08-29 15:42:49 +02:00
dependencies = [
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 07:45:27 +01: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 03:21:00 +01:00
"crossbeam-utils 0.6.6",
"curl",
"curl-sys",
"futures-io-preview",
"futures-util-preview",
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 03:21:00 +01:00
"lazy_static 1.4.0",
"log",
"slab",
"sluice",
Update futures-preview to 0.3.0-alpha.18
2019-08-29 15:42:49 +02:00
]
Add tree sink
2019-06-07 09:50:26 +02: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 03:21:00 +01:00
checksum = "e31a8281fc93ec9693494da65fbf28c0c2aa60a2eaec25dc58e2f31952e95edc"
Add tree sink
2019-06-07 09:50:26 +02: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 03:21:00 +01:00
"cfg-if",
"libc",
"redox_syscall",
"winapi 0.3.8",
Add tree sink
2019-06-07 09:50:26 +02:00
]
Better errors and more fleshed out semantics
2019-05-30 06:19:46 +02: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 03:21:00 +01:00
checksum = "0d47946d458e94a1b7bcabbf6521ea7c037062c81f534615abcad76e84d4970d"
Better errors and more fleshed out semantics
2019-05-30 06:19:46 +02: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 03:21:00 +01:00
"either",
Better errors and more fleshed out semantics
2019-05-30 06:19:46 +02:00
]
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
version = "0.8.2"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "f56a2d0bc861f9165be4eb3442afd3c236d8a98afd426f65d92324ae1091a484"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
"either",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
[[package]]
name = "itoa"
version = "0.4.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 03:21:00 +01:00
checksum = "501266b7edd0174f8530248f87f99c88fbe60ca4ef3dd486835b8d8d53136f7f"
objectshell initial commit
2019-05-10 18:59:12 +02:00
Add basic 'did you mean' support
2019-09-13 05:44:21 +02:00
[[package]]
name = "jobserver"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
version = "0.1.17"
Add basic 'did you mean' support
2019-09-13 05:44:21 +02: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 03:21:00 +01:00
checksum = "f2b1d42ef453b30b7387e113da1c83ab1605d90c5b4e0eb8e96d016ed3b8c160"
Add basic 'did you mean' support
2019-09-13 05:44:21 +02: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 03:21:00 +01:00
"getrandom",
"libc",
"log",
Add basic 'did you mean' support
2019-09-13 05:44:21 +02:00
]
Add some logic for more binary formats
2019-07-05 09:53:09 +02:00
[[package]]
name = "jpeg-decoder"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
version = "0.1.18"
Add some logic for more binary formats
2019-07-05 09:53:09 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
checksum = "0256f0aec7352539102a9efbcb75543227b7ab1117e0f95450023af730128451"
Add some logic for more binary formats
2019-07-05 09:53:09 +02: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 03:21:00 +01:00
"byteorder",
Add some logic for more binary formats
2019-07-05 09:53:09 +02:00
]
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
[[package]]
name = "js-sys"
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 07:45:27 +01:00
version = "0.3.33"
switch from reqwest to surf
2019-08-24 21:36:19 +02: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 07:45:27 +01:00
checksum = "367647c532db6f1555d7151e619540ec5f713328235b8c062c6b4f63e84adfe3"
switch from reqwest to surf
2019-08-24 21:36:19 +02: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 03:21:00 +01:00
"wasm-bindgen",
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
]
Restructure and make commands uniform
2019-05-22 09:12:03 +02: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 03:21:00 +01:00
checksum = "7507624b29483431c0ba2d82aece8ca6cdba9382bff4ddd0f7490560c056098d"
Restructure and make commands uniform
2019-05-22 09:12:03 +02: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 03:21:00 +01:00
"winapi 0.2.8",
"winapi-build",
Restructure and make commands uniform
2019-05-22 09:12:03 +02: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 07:45:27 +01: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 06:19:46 +02:00
[[package]]
name = "language-reporting"
Update cargo.lock
2019-10-16 04:09:47 +02: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 03:21:00 +01:00
checksum = "4e6a84e1e6cccd818617d299427ad1519f127af2738b1d3a581835ef56ae298b"
Better errors and more fleshed out semantics
2019-05-30 06:19:46 +02: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 03:21:00 +01: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 07:45:27 +01: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 03:21:00 +01:00
"serde_derive",
"termcolor",
Better errors and more fleshed out semantics
2019-05-30 06:19:46 +02:00
]
Lots of misc improvements
2019-06-03 09:41:28 +02: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 03:21:00 +01:00
checksum = "76f033c7ad61445c5b347c7382dd1237847eb1bce590fe50365dcb33d546be73"
Lots of misc improvements
2019-06-03 09:41:28 +02:00
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "lazy_static"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
version = "1.4.0"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "e2abad23fbc42b3700f2f279844dc832adb2b2eb069b2df918f455c4e18cc646"
objectshell initial commit
2019-05-10 18:59:12 +02:00
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
checksum = "b294d6fa9ee409a054354afc4352b0b9ef7ca222c69b8812cbea9e7d2bf3783f"
Bat
2019-05-18 03:24:13 +02:00
WIP
2019-06-22 05:43:37 +02:00
[[package]]
name = "lexical-core"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
version = "0.4.6"
WIP
2019-06-22 05:43:37 +02: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 03:21:00 +01:00
checksum = "2304bccb228c4b020f3a4835d247df0a02a7c4686098d4167762cfbbe4c5cb14"
WIP
2019-06-22 05:43:37 +02: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 03:21:00 +01:00
"arrayvec 0.4.12",
"cfg-if",
"rustc_version",
"ryu",
"static_assertions",
WIP
2019-06-22 05:43:37 +02:00
]
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
version = "0.2.66"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "d515b1f41455adea1313a4a2ac8a8a477634fbae63cc6100e3aebb207ce61558"
objectshell initial commit
2019-05-10 18:59:12 +02:00
Add git branch to prompt
2019-06-01 23:11:28 +02:00
[[package]]
name = "libgit2-sys"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
version = "0.10.0"
Add git branch to prompt
2019-06-01 23:11:28 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
checksum = "d9ec6bca50549d34a392611dde775123086acbd994e3fff64954777ce2dc2e51"
Add git branch to prompt
2019-06-01 23:11:28 +02: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 03:21:00 +01:00
"cc",
"libc",
"libz-sys",
"pkg-config",
Add git branch to prompt
2019-06-01 23:11:28 +02:00
]
switch from reqwest to surf
2019-08-24 21:36:19 +02: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 03:21:00 +01:00
checksum = "02254d44f4435dd79e695f2c2b83cd06a47919adea30216ceaf0c57ca0a72463"
switch from reqwest to surf
2019-08-24 21:36:19 +02: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 03:21:00 +01:00
"cc",
"libc",
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
]
Add SQLite support
2019-08-27 23:45:18 +02:00
[[package]]
name = "libsqlite3-sys"
Restructure and streamline token expansion (#1123) Restructure and streamline token expansion The purpose of this commit is to streamline the token expansion code, by removing aspects of the code that are no longer relevant, removing pointless duplication, and eliminating the need to pass the same arguments to `expand_syntax`. The first big-picture change in this commit is that instead of a handful of `expand_` functions, which take a TokensIterator and ExpandContext, a smaller number of methods on the `TokensIterator` do the same job. The second big-picture change in this commit is fully eliminating the coloring traits, making coloring a responsibility of the base expansion implementations. This also means that the coloring tracer is merged into the expansion tracer, so you can follow a single expansion and see how the expansion process produced colored tokens. One side effect of this change is that the expander itself is marginally more error-correcting. The error correction works by switching from structured expansion to `BackoffColoringMode` when an unexpected token is found, which guarantees that all spans of the source are colored, but may not be the most optimal error recovery strategy. That said, because `BackoffColoringMode` only extends as far as a closing delimiter (`)`, `]`, `}`) or pipe (`|`), it does result in fairly granular correction strategy. The current code still produces an `Err` (plus a complete list of colored shapes) from the parsing process if any errors are encountered, but this could easily be addressed now that the underlying expansion is error-correcting. This commit also colors any spans that are syntax errors in red, and causes the parser to include some additional information about what tokens were expected at any given point where an error was encountered, so that completions and hinting could be more robust in the future. Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com> Co-authored-by: Andrés N. Robalino <andres@androbtech.com>
2020-01-21 23:45:03 +01:00
version = "0.16.0"
Add SQLite support
2019-08-27 23:45:18 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Restructure and streamline token expansion (#1123) Restructure and streamline token expansion The purpose of this commit is to streamline the token expansion code, by removing aspects of the code that are no longer relevant, removing pointless duplication, and eliminating the need to pass the same arguments to `expand_syntax`. The first big-picture change in this commit is that instead of a handful of `expand_` functions, which take a TokensIterator and ExpandContext, a smaller number of methods on the `TokensIterator` do the same job. The second big-picture change in this commit is fully eliminating the coloring traits, making coloring a responsibility of the base expansion implementations. This also means that the coloring tracer is merged into the expansion tracer, so you can follow a single expansion and see how the expansion process produced colored tokens. One side effect of this change is that the expander itself is marginally more error-correcting. The error correction works by switching from structured expansion to `BackoffColoringMode` when an unexpected token is found, which guarantees that all spans of the source are colored, but may not be the most optimal error recovery strategy. That said, because `BackoffColoringMode` only extends as far as a closing delimiter (`)`, `]`, `}`) or pipe (`|`), it does result in fairly granular correction strategy. The current code still produces an `Err` (plus a complete list of colored shapes) from the parsing process if any errors are encountered, but this could easily be addressed now that the underlying expansion is error-correcting. This commit also colors any spans that are syntax errors in red, and causes the parser to include some additional information about what tokens were expected at any given point where an error was encountered, so that completions and hinting could be more robust in the future. Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com> Co-authored-by: Andrés N. Robalino <andres@androbtech.com>
2020-01-21 23:45:03 +01:00
checksum = "5e5b95e89c330291768dc840238db7f9e204fd208511ab6319b56193a7f2ae25"
Add SQLite support
2019-08-27 23:45:18 +02: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 03:21:00 +01:00
"cc",
"pkg-config",
"vcpkg",
Add SQLite support
2019-08-27 23:45:18 +02:00
]
Add git branch to prompt
2019-06-01 23:11:28 +02: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 03:21:00 +01:00
checksum = "2eb5e43362e38e2bca2fd5f5134c4d4564a23a5c28e9b95411652021a8675ebe"
Add git branch to prompt
2019-06-01 23:11:28 +02: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 03:21:00 +01:00
"cc",
"libc",
"pkg-config",
"vcpkg",
Add git branch to prompt
2019-06-01 23:11:28 +02:00
]
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
checksum = "f30344350a2a51da54c1d53be93fade8a237e545dbcc4bdbe635413f2117cab9"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
"safemem",
Bat
2019-05-18 03:24:13 +02:00
]
Lots of misc improvements
2019-06-03 09:41:28 +02: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 03:21:00 +01:00
checksum = "6d262045c5b87c0861b3f004610afd0e2c851e2908d08b6c870cbb9d5f494ecd"
Lots of misc improvements
2019-06-03 09:41:28 +02: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 03:21:00 +01:00
"serde 0.8.23",
"serde_test",
Lots of misc improvements
2019-06-03 09:41:28 +02:00
]
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
checksum = "ae91b68aebc4ddb91978b11a1b02ddd8602a05ec19002801c5666000e05e0f83"
Bat
2019-05-18 03:24:13 +02:00
Last unwraps (#1160) * Work through most of the last unwraps * Finish removing unwraps
2020-01-04 07:44:17 +01:00
[[package]]
name = "lock_api"
version = "0.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e57b3997725d2b60dbec1297f6c2e2957cc383db1cebd6be812163f969c7d586"
dependencies = [
"scopeguard",
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "log"
bump deps
2019-07-29 09:46:24 +02:00
version = "0.4.8"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "14b6052be84e6b71ab17edffc2eeabf5c2c3ae1fdb464aae35ac50c67a44e1f7"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
"cfg-if",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
Add SQLite support
2019-08-27 23:45:18 +02: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 03:21:00 +01:00
checksum = "31e24f1ad8321ca0e8a1e0ac13f23cb668e6f5466c2c57319f6a5cf1cc8e3b1c"
Add SQLite support
2019-08-27 23:45:18 +02: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 03:21:00 +01:00
"linked-hash-map 0.5.2",
Add SQLite support
2019-08-27 23:45:18 +02:00
]
Update plugin protocol for begin, and create new sys plugin
2019-07-27 09:45:00 +02:00
[[package]]
name = "macaddr"
Merge master
2019-11-16 18:17:05 +01:00
version = "0.1.2"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 09:45:00 +02: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 03:21:00 +01:00
checksum = "bee538cb1031f87f970ba28f0e5ebfcdaf63ed1a000a4176b4117537c33d19fb"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 09:45:00 +02:00
add some battery stats
2019-08-11 05:01:09 +02: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 03:21:00 +01:00
checksum = "86dd2487cdfea56def77b88438a2c915fb45113c5319bfe7e14306ca4cd0b0e1"
add some battery stats
2019-08-11 05:01:09 +02: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 03:21:00 +01:00
"libc",
add some battery stats
2019-08-11 05:01:09 +02:00
]
Update plugin protocol for begin, and create new sys plugin
2019-07-27 09:45:00 +02: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 03:21:00 +01:00
checksum = "b823e83b2affd8f40a9ee8c29dbc56404c1e34cd2710921f2801e2cf29527afa"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 09:45:00 +02: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 03:21:00 +01:00
"libc",
Update plugin protocol for begin, and create new sys plugin
2019-07-27 09:45:00 +02:00
]
Add clipboard support
2019-06-07 18:30:50 +02: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 03:21:00 +01:00
checksum = "62bb907fe88d54d8d9ce32a3cceab4218ed2f6b7d35617cafe9adf84e43919cb"
Add clipboard support
2019-06-07 18:30:50 +02: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 03:21:00 +01:00
"libc",
Add clipboard support
2019-06-07 18:30:50 +02:00
]
Add git branch to prompt
2019-06-01 23:11:28 +02: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 03:21:00 +01:00
checksum = "7ffc5c5338469d4d3ea17d269fa8ea3512ad247247c30bd2df69e68309ed0a08"
Merge master
2019-11-16 18:17:05 +01:00
Rebase on master
2019-08-25 15:57:47 +02:00
[[package]]
name = "md5"
Update bson to 0.14
2019-08-31 16:22:45 +02:00
version = "0.6.1"
Rebase on master
2019-08-25 15:57:47 +02: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 03:21:00 +01:00
checksum = "7e6bcd6433cff03a4bfc3d9834d504467db1f1cf6d0ea765d37d330249ed629d"
Rebase on master
2019-08-25 15:57:47 +02:00
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "memchr"
bump deps
2019-07-29 09:46:24 +02:00
version = "2.2.1"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "88579771288728879b57485cc7d6b07d648c9f0141eb955f8ab7f9d45394468e"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
"libc",
objectshell initial commit
2019-05-10 18:59:12 +02: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 15:47:30 +02:00
[[package]]
name = "memoffset"
Merge master
2019-11-16 18:17:05 +01: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 15:47:30 +02: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 03:21:00 +01: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 15:47:30 +02: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 03:21:00 +01: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 15:47:30 +02:00
]
Add opening urls
2019-06-08 20:09:17 +02:00
[[package]]
name = "mime"
Add basic 'did you mean' support
2019-09-13 05:44:21 +02:00
version = "0.3.14"
Add opening urls
2019-06-08 20:09:17 +02: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 03:21:00 +01:00
checksum = "dd1d63acd1b78403cc0c325605908475dd9b9a3acbf65ed8bcab97e27014afcf"
Add opening urls
2019-06-08 20:09:17 +02:00
[[package]]
name = "mime_guess"
Pin semver breaking dep
2019-08-08 19:33:19 +02:00
version = "2.0.1"
Add opening urls
2019-06-08 20:09:17 +02: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 03:21:00 +01:00
checksum = "1a0ed03949aef72dbdf3116a383d7b38b4768e6f960528cd6a6044aa9ed68599"
Add opening urls
2019-06-08 20:09:17 +02: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 03:21:00 +01:00
"mime",
"unicase",
Bat
2019-05-18 03:24:13 +02:00
]
[[package]]
name = "miniz_oxide"
Merge master
2019-11-16 18:17:05 +01:00
version = "0.3.5"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
checksum = "6f3f74f726ae935c3f514300cc6773a0c9492abc5e972d42ba0c0ebb88757625"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
"adler32",
Bat
2019-05-18 03:24:13 +02: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 07:45:27 +01: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 05:44:21 +02: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 03:21:00 +01:00
checksum = "fd659d7d6b4554da2c0e7a486d5952b24dfce0e0bac88ab53b270f4efe1010a6"
Add basic 'did you mean' support
2019-09-13 05:44:21 +02:00
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02: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 03:21:00 +01:00
checksum = "6b3c31defbcb081163db18437fd88c2a267cb3e26f7bd5e4b186e4b1b38fe8c8"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02: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 03:21:00 +01: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 07:45:27 +01: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 03:21:00 +01:00
"serde_derive",
"wasm-bindgen",
Add opening urls
2019-06-08 20:09:17 +02: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 07:45:27 +01: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 02:31:22 +02: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 21:13:29 +02:00
version = "0.14.1"
Handle Ctrl-C gracefully
2019-06-07 02:31:22 +02: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 03:21:00 +01:00
checksum = "6c722bee1037d430d0f8e687bbdbf222f27cc6e4e68d5caf630857bb2b6dbdce"
Handle Ctrl-C gracefully
2019-06-07 02:31:22 +02: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 03:21:00 +01:00
"bitflags",
"cc",
"cfg-if",
"libc",
"void",
Handle Ctrl-C gracefully
2019-06-07 02:31:22 +02:00
]
Update to heim v0.0.7.
2019-08-28 17:53:59 +02: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 03:21:00 +01:00
checksum = "3b2e0b4f3320ed72aaedb9a5ac838690a8047c7b275da22711fddff4f8a14229"
Update to heim v0.0.7.
2019-08-28 17:53:59 +02: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 03:21:00 +01:00
"bitflags",
"cc",
"cfg-if",
"libc",
"void",
Update to heim v0.0.7.
2019-08-28 17:53:59 +02:00
]
Bump heim and necessary deps
2019-12-14 14:27:14 +01: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 07:45:27 +01:00
version = "0.16.1"
Bump heim and necessary deps
2019-12-14 14:27:14 +01: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 07:45:27 +01:00
checksum = "dd0eaf8df8bab402257e0a5c17a254e4cc1f72a93588a1ddfb5d356c801aa7cb"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
dependencies = [
"bitflags",
"cc",
"cfg-if",
"libc",
"void",
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "nodrop"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
version = "0.1.14"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "72ef4a56884ca558e5ddb05a1d1e7e1bfd9a68d9ed024c21704cc98872dae1bb"
objectshell initial commit
2019-05-10 18:59:12 +02:00
Add tree sink
2019-06-07 09:50:26 +02: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 03:21:00 +01:00
checksum = "2ad2a91a8e869eeb30b9cb3119ae87773a8f4ae617f41b1eb9c154b2905f7bd6"
Add tree sink
2019-06-07 09:50:26 +02: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 03:21:00 +01:00
"memchr",
"version_check 0.1.5",
Add tree sink
2019-06-07 09:50:26 +02:00
]
Paths
2019-06-13 07:33:38 +02:00
[[package]]
WIP
2019-06-22 05:43:37 +02:00
name = "nom"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
version = "5.1.0"
WIP
2019-06-22 05:43:37 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
checksum = "c433f4d505fe6ce7ff78523d2fa13a0b9f2690e181fc26168bcbe5ccc5d14e07"
Paths
2019-06-13 07:33:38 +02: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 03:21:00 +01:00
"lexical-core",
"memchr",
"version_check 0.1.5",
Paths
2019-06-13 07:33:38 +02: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-18 00:26:27 +02:00
[[package]]
name = "nom-tracable"
Bump dep versions
2019-11-10 18:48:49 +01: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-18 00:26:27 +02: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 03:21:00 +01: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-18 00:26:27 +02:00
dependencies = [
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 03:21:00 +01: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-18 00:26:27 +02:00
]
[[package]]
name = "nom-tracable-macros"
Merge master
2019-11-16 18:17:05 +01: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-18 00:26:27 +02: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 03:21:00 +01: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-18 00:26:27 +02: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 03:21:00 +01: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-18 00:26:27 +02:00
]
Simple parsing
2019-05-11 06:45:57 +02:00
[[package]]
Revert "Revert "Migrate most uses of the Span concept to Tag"" This reverts commit bee7c5639cc78d65e6656518627a86009a522500.
2019-09-14 18:30:24 +02:00
name = "nom_locate"
version = "1.0.0"
Cleanup for upcoming release
2019-07-16 21:10:25 +02: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 03:21:00 +01:00
checksum = "f932834fd8e391fc7710e2ba17e8f9f8645d846b55aa63207e17e110a1e1ce35"
Simple parsing
2019-05-11 06:45:57 +02: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 03:21:00 +01:00
"bytecount",
"memchr",
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
"nom 5.1.0",
Simple parsing
2019-05-11 06:45:57 +02:00
]
Pin semver breaking dep
2019-08-08 19:33:19 +02: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 03:21:00 +01:00
checksum = "f26e041cd983acbc087e30fcba770380cfa352d0e392e175b2344ebaf7ea0602"
Pin semver breaking dep
2019-08-08 19:33:19 +02: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 03:21:00 +01:00
"winapi 0.3.8",
Pin semver breaking dep
2019-08-08 19:33:19 +02:00
]
Update name
2019-05-17 01:39:58 +02:00
[[package]]
name = "nu"
Bump to 0.9.0 (#1297)
2020-01-29 03:17:02 +01:00
version = "0.9.0"
Update name
2019-05-17 01:39:58 +02: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 03:21:00 +01:00
"ansi_term 0.12.1",
"app_dirs",
"async-stream",
"base64 0.11.0",
Move some plugins back to being core shippable plugins
2019-12-10 01:05:40 +01:00
"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 03:21:00 +01:00
"bigdecimal",
"bson",
"byte-unit",
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
"bytes 0.4.12",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"calamine",
"cfg-if",
"chrono",
"clap",
"clipboard",
Move some plugins back to being core shippable plugins
2019-12-10 01:05:40 +01:00
"crossterm",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"csv",
"ctrlc",
"derive-new",
"dirs 2.0.2",
"dunce",
"futures-preview",
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 07:45:27 +01:00
"futures-timer 1.0.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 03:21:00 +01:00
"futures-util",
"futures_codec",
"getset",
"git2",
"glob",
Move some plugins back to being core shippable plugins
2019-12-10 01:05:40 +01:00
"heim",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"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 07:45:27 +01: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 03:21:00 +01:00
"indexmap",
"itertools 0.8.2",
"language-reporting",
"log",
"natural",
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 03:21:00 +01:00
"nom-tracable",
"nom_locate",
Extract build.rs
2019-12-02 22:14:51 +01: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 03:21:00 +01: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 22:14:52 +01: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 03:21:00 +01:00
"nu-parser",
Nu plugins now depend on nu-plugin crate.
2019-12-27 14:30:14 +01: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 03:21:00 +01:00
"nu-protocol",
"nu-source",
Rename test-support to nu-test-support
2019-12-17 19:41:47 +01:00
"nu-test-support",
Move the remainder of the plugins to crates
2019-12-09 19:39:51 +01:00
"nu-value-ext",
"nu_plugin_average",
Move binaryview to a sub-crate
2019-12-04 18:51:20 +01:00
"nu_plugin_binaryview",
WIP move post/fetch to plugins
2019-12-07 04:46:05 +01:00
"nu_plugin_fetch",
Trying this as a workaround to the [[bin]] issue
2019-12-10 04:57:55 +01:00
"nu_plugin_inc",
Move the remainder of the plugins to crates
2019-12-09 19:39:51 +01:00
"nu_plugin_match",
WIP move post/fetch to plugins
2019-12-07 04:46:05 +01:00
"nu_plugin_post",
Trying this as a workaround to the [[bin]] issue
2019-12-10 04:57:55 +01:00
"nu_plugin_ps",
"nu_plugin_str",
Move the remainder of the plugins to crates
2019-12-09 19:39:51 +01:00
"nu_plugin_sum",
Trying this as a workaround to the [[bin]] issue
2019-12-10 04:57:55 +01:00
"nu_plugin_sys",
"nu_plugin_textview",
Move the remainder of the plugins to crates
2019-12-09 19:39:51 +01:00
"nu_plugin_tree",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"num-bigint",
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
"num-traits 0.2.11",
Move some plugins back to being core shippable plugins
2019-12-10 01:05:40 +01:00
"onig_sys",
Last unwraps (#1160) * Work through most of the last unwraps * Finish removing unwraps
2020-01-04 07:44:17 +01: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 03:21:00 +01:00
"pin-utils",
"pretty-hex",
"pretty_assertions",
"pretty_env_logger",
"prettytable-rs",
"ptree",
"query_interface",
"regex",
"roxmltree",
"rusqlite",
"rustyline",
Restructure and streamline token expansion (#1123) Restructure and streamline token expansion The purpose of this commit is to streamline the token expansion code, by removing aspects of the code that are no longer relevant, removing pointless duplication, and eliminating the need to pass the same arguments to `expand_syntax`. The first big-picture change in this commit is that instead of a handful of `expand_` functions, which take a TokensIterator and ExpandContext, a smaller number of methods on the `TokensIterator` do the same job. The second big-picture change in this commit is fully eliminating the coloring traits, making coloring a responsibility of the base expansion implementations. This also means that the coloring tracer is merged into the expansion tracer, so you can follow a single expansion and see how the expansion process produced colored tokens. One side effect of this change is that the expander itself is marginally more error-correcting. The error correction works by switching from structured expansion to `BackoffColoringMode` when an unexpected token is found, which guarantees that all spans of the source are colored, but may not be the most optimal error recovery strategy. That said, because `BackoffColoringMode` only extends as far as a closing delimiter (`)`, `]`, `}`) or pipe (`|`), it does result in fairly granular correction strategy. The current code still produces an `Err` (plus a complete list of colored shapes) from the parsing process if any errors are encountered, but this could easily be addressed now that the underlying expansion is error-correcting. This commit also colors any spans that are syntax errors in red, and causes the parser to include some additional information about what tokens were expected at any given point where an error was encountered, so that completions and hinting could be more robust in the future. Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com> Co-authored-by: Andrés N. Robalino <andres@androbtech.com>
2020-01-21 23:45:03 +01:00
"semver",
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 07:45:27 +01: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 03:21:00 +01:00
"serde-hjson 0.9.1",
"serde_bytes",
"serde_ini",
"serde_json",
"serde_urlencoded",
"serde_yaml",
"shellexpand",
"starship",
"strip-ansi-escapes",
Move some plugins back to being core shippable plugins
2019-12-10 01:05:40 +01:00
"syntect",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"tempfile",
"term",
"termcolor",
"textwrap",
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 03:21:00 +01:00
"trash",
"typetag",
"umask",
"unicode-xid",
Move some plugins back to being core shippable plugins
2019-12-10 01:05:40 +01:00
"url",
A few ls improvements. New welcome message (#1195)
2020-01-11 21:49:20 +01:00
"users",
Improve shelling out (#1273) Improvements to shelling out
2020-01-23 20:24:31 +01: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 15:33:14 +01:00
]
Extract build.rs
2019-12-02 22:14:51 +01:00
[[package]]
name = "nu-build"
Bump to 0.9.0 (#1297)
2020-01-29 03:17:02 +01:00
version = "0.9.0"
Extract build.rs
2019-12-02 22:14:51 +01:00
dependencies = [
"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 07:45:27 +01:00
"serde 1.0.104",
Extract build.rs
2019-12-02 22:14:51 +01:00
"serde_json",
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
"toml 0.5.6",
Extract build.rs
2019-12-02 22:14:51 +01: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 03:30:48 +01:00
[[package]]
name = "nu-errors"
Bump to 0.9.0 (#1297)
2020-01-29 03:17:02 +01:00
version = "0.9.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 03:30:48 +01: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 03:21:00 +01:00
"ansi_term 0.12.1",
"bigdecimal",
"derive-new",
Restructure and streamline token expansion (#1123) Restructure and streamline token expansion The purpose of this commit is to streamline the token expansion code, by removing aspects of the code that are no longer relevant, removing pointless duplication, and eliminating the need to pass the same arguments to `expand_syntax`. The first big-picture change in this commit is that instead of a handful of `expand_` functions, which take a TokensIterator and ExpandContext, a smaller number of methods on the `TokensIterator` do the same job. The second big-picture change in this commit is fully eliminating the coloring traits, making coloring a responsibility of the base expansion implementations. This also means that the coloring tracer is merged into the expansion tracer, so you can follow a single expansion and see how the expansion process produced colored tokens. One side effect of this change is that the expander itself is marginally more error-correcting. The error correction works by switching from structured expansion to `BackoffColoringMode` when an unexpected token is found, which guarantees that all spans of the source are colored, but may not be the most optimal error recovery strategy. That said, because `BackoffColoringMode` only extends as far as a closing delimiter (`)`, `]`, `}`) or pipe (`|`), it does result in fairly granular correction strategy. The current code still produces an `Err` (plus a complete list of colored shapes) from the parsing process if any errors are encountered, but this could easily be addressed now that the underlying expansion is error-correcting. This commit also colors any spans that are syntax errors in red, and causes the parser to include some additional information about what tokens were expected at any given point where an error was encountered, so that completions and hinting could be more robust in the future. Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com> Co-authored-by: Andrés N. Robalino <andres@androbtech.com>
2020-01-21 23:45:03 +01:00
"getset",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"language-reporting",
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 03:21:00 +01:00
"nom_locate",
Extract build.rs
2019-12-02 22:14:51 +01: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 03:21:00 +01:00
"nu-source",
"num-bigint",
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 07:45:27 +01: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 03:21:00 +01:00
"serde_json",
"serde_yaml",
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 03:30:48 +01: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 22:14:52 +01:00
[[package]]
name = "nu-macros"
Bump to 0.9.0 (#1297)
2020-01-29 03:17:02 +01:00
version = "0.9.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 22:14:52 +01: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 03:30:48 +01:00
[[package]]
name = "nu-parser"
Bump to 0.9.0 (#1297)
2020-01-29 03:17:02 +01:00
version = "0.9.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 03:30:48 +01: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 03:21:00 +01: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 22:14:52 +01:00
"enumflags2",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"getset",
"indexmap",
"itertools 0.8.2",
"language-reporting",
"log",
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 03:21:00 +01:00
"nom-tracable",
"nom_locate",
Extract build.rs
2019-12-02 22:14:51 +01: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 03:21:00 +01:00
"nu-errors",
"nu-protocol",
"nu-source",
"num-bigint",
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 03:21:00 +01:00
"pretty",
Fix the workspace I commented out
2019-12-18 18:58:23 +01:00
"pretty_assertions",
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
"pretty_env_logger",
"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 07:45:27 +01: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 03:21:00 +01:00
"shellexpand",
"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 03:30:48 +01:00
]
Nu plugins now depend on nu-plugin crate.
2019-12-27 14:30:14 +01:00
[[package]]
name = "nu-plugin"
Bump to 0.9.0 (#1297)
2020-01-29 03:17:02 +01:00
version = "0.9.0"
Nu plugins now depend on nu-plugin crate.
2019-12-27 14:30:14 +01: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 07:45:27 +01:00
"serde 1.0.104",
Nu plugins now depend on nu-plugin crate.
2019-12-27 14:30:14 +01: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 03:30:48 +01:00
[[package]]
name = "nu-protocol"
Bump to 0.9.0 (#1297)
2020-01-29 03:17:02 +01:00
version = "0.9.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 03:30:48 +01: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 03:21:00 +01:00
"ansi_term 0.12.1",
"bigdecimal",
Move the remainder of the plugins to crates
2019-12-09 19:39:51 +01: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 03:21:00 +01:00
"chrono",
"derive-new",
"getset",
"indexmap",
"language-reporting",
Move the remainder of the plugins to crates
2019-12-09 19:39:51 +01:00
"natural",
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 03:21:00 +01:00
"nom-tracable",
"nom_locate",
Extract build.rs
2019-12-02 22:14:51 +01: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 03:21:00 +01:00
"nu-errors",
"nu-source",
"num-bigint",
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 03:21:00 +01: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 07:45:27 +01: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 03:21:00 +01:00
"serde_bytes",
"serde_json",
"serde_yaml",
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 03:21:00 +01: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 03:30:48 +01: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 15:33:14 +01:00
[[package]]
name = "nu-source"
Bump to 0.9.0 (#1297)
2020-01-29 03:17:02 +01:00
version = "0.9.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 15:33:14 +01: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 03:21:00 +01:00
"derive-new",
"getset",
"language-reporting",
"nom-tracable",
"nom_locate",
Extract build.rs
2019-12-02 22:14:51 +01: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 03:21:00 +01: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 07:45:27 +01: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 03:21:00 +01:00
"termcolor",
Restructure and make commands uniform
2019-05-22 09:12:03 +02:00
]
Rename test-support to nu-test-support
2019-12-17 19:41:47 +01:00
[[package]]
name = "nu-test-support"
Bump to 0.9.0 (#1297)
2020-01-29 03:17:02 +01:00
version = "0.9.0"
Rename test-support to nu-test-support
2019-12-17 19:41:47 +01:00
dependencies = [
"app_dirs",
"dunce",
"getset",
"glob",
Baseline environment and configuration work. (#1287)
2020-01-28 04:13:22 +01:00
"indexmap",
"nu",
Keep dummies in default features for convenience. (#1212)
2020-01-13 07:17:56 +01: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 10:05:53 +01:00
"nu-parser",
Baseline environment and configuration work. (#1287)
2020-01-28 04:13:22 +01: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 10:05:53 +01:00
"nu-source",
Rename test-support to nu-test-support
2019-12-17 19:41:47 +01:00
"tempfile",
]
Move the remainder of the plugins to crates
2019-12-09 19:39:51 +01:00
[[package]]
name = "nu-value-ext"
Bump to 0.9.0 (#1297)
2020-01-29 03:17:02 +01:00
version = "0.9.0"
Move the remainder of the plugins to crates
2019-12-09 19:39:51 +01:00
dependencies = [
Baseline environment and configuration work. (#1287)
2020-01-28 04:13:22 +01:00
"indexmap",
Move the remainder of the plugins to crates
2019-12-09 19:39:51 +01:00
"itertools 0.8.2",
"nu-build",
"nu-errors",
"nu-parser",
"nu-protocol",
"nu-source",
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
"num-traits 0.2.11",
Move the remainder of the plugins to crates
2019-12-09 19:39:51 +01:00
]
[[package]]
name = "nu_plugin_average"
Bump to 0.9.0 (#1297)
2020-01-29 03:17:02 +01:00
version = "0.9.0"
Move the remainder of the plugins to crates
2019-12-09 19:39:51 +01:00
dependencies = [
"nu-build",
"nu-errors",
Nu plugins now depend on nu-plugin crate.
2019-12-27 14:30:14 +01:00
"nu-plugin",
Move the remainder of the plugins to crates
2019-12-09 19:39:51 +01:00
"nu-protocol",
"nu-source",
]
Move binaryview to a sub-crate
2019-12-04 18:51:20 +01:00
[[package]]
name = "nu_plugin_binaryview"
Bump to 0.9.0 (#1297)
2020-01-29 03:17:02 +01:00
version = "0.9.0"
Move binaryview to a sub-crate
2019-12-04 18:51:20 +01:00
dependencies = [
"ansi_term 0.12.1",
"crossterm",
"image",
"neso",
"nu-build",
"nu-errors",
Nu plugins now depend on nu-plugin crate.
2019-12-27 14:30:14 +01:00
"nu-plugin",
Move binaryview to a sub-crate
2019-12-04 18:51:20 +01:00
"nu-protocol",
"nu-source",
"pretty-hex",
"rawkey",
Extract ps and sys subcrates. Move helper methods to UntaggedValue
2019-12-04 20:52:31 +01:00
]
WIP move post/fetch to plugins
2019-12-07 04:46:05 +01:00
[[package]]
name = "nu_plugin_fetch"
Bump to 0.9.0 (#1297)
2020-01-29 03:17:02 +01:00
version = "0.9.0"
WIP move post/fetch to plugins
2019-12-07 04:46:05 +01:00
dependencies = [
"futures-preview",
"nu-build",
"nu-errors",
Nu plugins now depend on nu-plugin crate.
2019-12-27 14:30:14 +01:00
"nu-plugin",
WIP move post/fetch to plugins
2019-12-07 04:46:05 +01:00
"nu-protocol",
"nu-source",
"surf",
"url",
]
Trying this as a workaround to the [[bin]] issue
2019-12-10 04:57:55 +01:00
[[package]]
name = "nu_plugin_inc"
Bump to 0.9.0 (#1297)
2020-01-29 03:17:02 +01:00
version = "0.9.0"
Trying this as a workaround to the [[bin]] issue
2019-12-10 04:57:55 +01:00
dependencies = [
"nu-build",
"nu-errors",
Nu plugins now depend on nu-plugin crate.
2019-12-27 14:30:14 +01:00
"nu-plugin",
Trying this as a workaround to the [[bin]] issue
2019-12-10 04:57:55 +01:00
"nu-protocol",
"nu-source",
"nu-value-ext",
"semver",
]
Move the remainder of the plugins to crates
2019-12-09 19:39:51 +01:00
[[package]]
name = "nu_plugin_match"
Bump to 0.9.0 (#1297)
2020-01-29 03:17:02 +01:00
version = "0.9.0"
Move the remainder of the plugins to crates
2019-12-09 19:39:51 +01:00
dependencies = [
"futures-preview",
"nu-build",
"nu-errors",
Nu plugins now depend on nu-plugin crate.
2019-12-27 14:30:14 +01:00
"nu-plugin",
Move the remainder of the plugins to crates
2019-12-09 19:39:51 +01:00
"nu-protocol",
"nu-source",
"regex",
]
WIP move post/fetch to plugins
2019-12-07 04:46:05 +01:00
[[package]]
name = "nu_plugin_post"
Bump to 0.9.0 (#1297)
2020-01-29 03:17:02 +01:00
version = "0.9.0"
WIP move post/fetch to plugins
2019-12-07 04:46:05 +01:00
dependencies = [
"base64 0.11.0",
"futures-preview",
"nu-build",
"nu-errors",
Nu plugins now depend on nu-plugin crate.
2019-12-27 14:30:14 +01:00
"nu-plugin",
WIP move post/fetch to plugins
2019-12-07 04:46:05 +01:00
"nu-protocol",
"nu-source",
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
"num-traits 0.2.11",
WIP move post/fetch to plugins
2019-12-07 04:46:05 +01:00
"serde_json",
"surf",
"url",
]
Trying this as a workaround to the [[bin]] issue
2019-12-10 04:57:55 +01:00
[[package]]
name = "nu_plugin_ps"
Bump to 0.9.0 (#1297)
2020-01-29 03:17:02 +01:00
version = "0.9.0"
Trying this as a workaround to the [[bin]] issue
2019-12-10 04:57:55 +01:00
dependencies = [
"futures-preview",
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 07:45:27 +01:00
"futures-timer 1.0.3",
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
"futures-util",
Trying this as a workaround to the [[bin]] issue
2019-12-10 04:57:55 +01:00
"heim",
"nu-build",
"nu-errors",
Nu plugins now depend on nu-plugin crate.
2019-12-27 14:30:14 +01:00
"nu-plugin",
Trying this as a workaround to the [[bin]] issue
2019-12-10 04:57:55 +01:00
"nu-protocol",
"nu-source",
"pin-utils",
]
[[package]]
name = "nu_plugin_str"
Bump to 0.9.0 (#1297)
2020-01-29 03:17:02 +01:00
version = "0.9.0"
Trying this as a workaround to the [[bin]] issue
2019-12-10 04:57:55 +01:00
dependencies = [
"nu-build",
"nu-errors",
Nu plugins now depend on nu-plugin crate.
2019-12-27 14:30:14 +01:00
"nu-plugin",
Trying this as a workaround to the [[bin]] issue
2019-12-10 04:57:55 +01:00
"nu-protocol",
"nu-source",
"nu-value-ext",
"num-bigint",
"regex",
]
Move the remainder of the plugins to crates
2019-12-09 19:39:51 +01:00
[[package]]
name = "nu_plugin_sum"
Bump to 0.9.0 (#1297)
2020-01-29 03:17:02 +01:00
version = "0.9.0"
Move the remainder of the plugins to crates
2019-12-09 19:39:51 +01:00
dependencies = [
"nu-build",
"nu-errors",
Nu plugins now depend on nu-plugin crate.
2019-12-27 14:30:14 +01:00
"nu-plugin",
Move the remainder of the plugins to crates
2019-12-09 19:39:51 +01:00
"nu-protocol",
"nu-source",
]
Trying this as a workaround to the [[bin]] issue
2019-12-10 04:57:55 +01:00
[[package]]
name = "nu_plugin_sys"
Bump to 0.9.0 (#1297)
2020-01-29 03:17:02 +01:00
version = "0.9.0"
Trying this as a workaround to the [[bin]] issue
2019-12-10 04:57:55 +01:00
dependencies = [
"battery",
"futures-preview",
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
"futures-util",
Trying this as a workaround to the [[bin]] issue
2019-12-10 04:57:55 +01:00
"heim",
"nu-build",
"nu-errors",
Nu plugins now depend on nu-plugin crate.
2019-12-27 14:30:14 +01:00
"nu-plugin",
Trying this as a workaround to the [[bin]] issue
2019-12-10 04:57:55 +01:00
"nu-protocol",
"nu-source",
]
[[package]]
name = "nu_plugin_textview"
Bump to 0.9.0 (#1297)
2020-01-29 03:17:02 +01:00
version = "0.9.0"
Trying this as a workaround to the [[bin]] issue
2019-12-10 04:57:55 +01:00
dependencies = [
"ansi_term 0.12.1",
"crossterm",
"nu-build",
"nu-errors",
Nu plugins now depend on nu-plugin crate.
2019-12-27 14:30:14 +01:00
"nu-plugin",
Trying this as a workaround to the [[bin]] issue
2019-12-10 04:57:55 +01:00
"nu-protocol",
"nu-source",
"onig_sys",
"syntect",
"url",
]
Move the remainder of the plugins to crates
2019-12-09 19:39:51 +01:00
[[package]]
name = "nu_plugin_tree"
Bump to 0.9.0 (#1297)
2020-01-29 03:17:02 +01:00
version = "0.9.0"
Move the remainder of the plugins to crates
2019-12-09 19:39:51 +01:00
dependencies = [
"derive-new",
"nu-build",
"nu-errors",
Nu plugins now depend on nu-plugin crate.
2019-12-27 14:30:14 +01:00
"nu-plugin",
Move the remainder of the plugins to crates
2019-12-09 19:39:51 +01: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 19:29:04 +02:00
[[package]]
name = "num-bigint"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
version = "0.2.5"
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 19:29:04 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
checksum = "f6f115de20ad793e857f76da2563ff4a09fbcfd6fe93cca0c5d996ab5f3ee38d"
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 19:29:04 +02:00
dependencies = [
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 03:21:00 +01:00
"num-integer",
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 07:45:27 +01: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 19:29:04 +02:00
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "num-integer"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
version = "0.1.42"
objectshell initial commit
2019-05-10 18:59:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
checksum = "3f6ea62e9d81a77cd3ee9a2a5b9b609447857f3d358704331e4ef39eb247fcba"
objectshell initial commit
2019-05-10 18:59:12 +02:00
dependencies = [
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
"autocfg 1.0.0",
"num-traits 0.2.11",
Restructure and make commands uniform
2019-05-22 09:12:03 +02:00
]
Add some logic for more binary formats
2019-07-05 09:53:09 +02:00
[[package]]
name = "num-iter"
version = "0.1.39"
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 03:21:00 +01:00
checksum = "76bd5272412d173d6bf9afdf98db8612bbabc9a7a830b7bfc9c188911716132e"
Add some logic for more binary formats
2019-07-05 09:53:09 +02:00
dependencies = [
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 03:21:00 +01:00
"num-integer",
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
"num-traits 0.2.11",
Add some logic for more binary formats
2019-07-05 09:53:09 +02:00
]
[[package]]
name = "num-rational"
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 03:21:00 +01:00
checksum = "f2885278d5fe2adc2f75ced642d52d879bffaceb5a2e0b1d4309ffdfb239b454"
Add some logic for more binary formats
2019-07-05 09:53:09 +02:00
dependencies = [
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 03:21:00 +01:00
"num-integer",
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
"num-traits 0.2.11",
Add some logic for more binary formats
2019-07-05 09:53:09 +02:00
]
Lots of misc improvements
2019-06-03 09:41:28 +02: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 03:21:00 +01:00
checksum = "92e5113e9fd4cc14ded8e499429f396a20f98c772a47cc8622a736e1ec843c31"
Lots of misc improvements
2019-06-03 09:41:28 +02:00
dependencies = [
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
"num-traits 0.2.11",
Lots of misc improvements
2019-06-03 09:41:28 +02:00
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "num-traits"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
version = "0.2.11"
objectshell initial commit
2019-05-10 18:59:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
checksum = "c62be47e61d1842b9170f0fdeec8eba98e60e90e5446449a0545e5152acd7096"
Restructure and make commands uniform
2019-05-22 09:12:03 +02:00
dependencies = [
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
"autocfg 1.0.0",
Restructure and make commands uniform
2019-05-22 09:12:03 +02:00
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "num_cpus"
Merge master
2019-11-16 18:17:05 +01:00
version = "1.11.1"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "76dac5ed2a876980778b8b85f75a71b6cbf0db0b1232ee12f826bccb00d09d72"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
"hermit-abi",
"libc",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
Add clipboard support
2019-06-07 18:30:50 +02:00
[[package]]
name = "objc"
Merge master
2019-11-16 18:17:05 +01:00
version = "0.2.7"
Add clipboard support
2019-06-07 18:30:50 +02: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 03:21:00 +01:00
checksum = "915b1b472bc21c53464d6c8461c9d3af805ba1ef837e1cac254428f4a77177b1"
Add clipboard support
2019-06-07 18:30:50 +02: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 03:21:00 +01:00
"malloc_buf",
Add clipboard support
2019-06-07 18:30:50 +02: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 03:21:00 +01:00
checksum = "1add1b659e36c9607c7aab864a76c7a4c2760cd0cd2e120f3fb8b952c7e22bf9"
Add clipboard support
2019-06-07 18:30:50 +02: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 03:21:00 +01:00
"block",
"objc",
"objc_id",
Add clipboard support
2019-06-07 18:30:50 +02: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 03:21:00 +01:00
checksum = "c92d4ddb4bd7b50d730c215ff871754d0da6b2178849f8a2a2ab69712d0c073b"
Add clipboard support
2019-06-07 18:30:50 +02: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 03:21:00 +01:00
"objc",
Add clipboard support
2019-06-07 18:30:50 +02:00
]
Improve signature infrastructure The `config` command uses different kinds of named arguments, which illustrates how it works.
2019-06-01 07:50:16 +02: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 03:21:00 +01:00
checksum = "5d2c49021782e5233cd243168edfa8037574afed4eba4bbaf538b3d8d1789d8c"
Improve signature infrastructure The `config` command uses different kinds of named arguments, which illustrates how it works.
2019-06-01 07:50:16 +02: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 03:21:00 +01: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 07:50:16 +02: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 15:47:30 +02:00
[[package]]
name = "once_cell"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 15:47:30 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
checksum = "f5941ec2d5ee5916c709580d71553b81a633df245bcc73c04dcbd62152ceefc4"
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 15:47:30 +02:00
Bat
2019-05-18 03:24:13 +02:00
[[package]]
name = "onig"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
version = "4.3.3"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
checksum = "8518fcb2b1b8c2f45f0ad499df4fda6087fc3475ca69a185c173b8315d2fb383"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
"bitflags",
"lazy_static 1.4.0",
"libc",
"onig_sys",
Bat
2019-05-18 03:24:13 +02:00
]
[[package]]
name = "onig_sys"
Revert bump
2019-08-10 08:31:31 +02:00
version = "69.1.0"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
checksum = "388410bf5fa341f10e58e6db3975f4bea1ac30247dd79d37a9e5ced3cb4cc3b0"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
"cc",
"pkg-config",
Bat
2019-05-18 03:24:13 +02:00
]
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
[[package]]
name = "open"
version = "1.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "94b424e1086328b0df10235c6ff47be63708071881bead9e76997d9291c0134b"
dependencies = [
"winapi 0.3.8",
]
Add git branch to prompt
2019-06-01 23:11:28 +02: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 03:21:00 +01:00
checksum = "77af24da69f9d9341038eba93a073b1fdaaa1b788221b00a69bce9e762cb32de"
Add git branch to prompt
2019-06-01 23:11:28 +02:00
[[package]]
name = "openssl-sys"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
version = "0.9.53"
Add git branch to prompt
2019-06-01 23:11:28 +02: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 03:21:00 +01:00
checksum = "465d16ae7fc0e313318f7de5cecf57b2fbe7511fd213978b457e1c96ff46736f"
Add git branch to prompt
2019-06-01 23:11:28 +02:00
dependencies = [
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 03:21:00 +01:00
"cc",
"libc",
"pkg-config",
"vcpkg",
Add git branch to prompt
2019-06-01 23:11:28 +02:00
]
Update bson to 0.14
2019-08-31 16:22:45 +02: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 03:21:00 +01:00
checksum = "d7ce14664caf5b27f5656ff727defd68ae1eb75ef3c4d95259361df1eb376bef"
Update bson to 0.14
2019-08-31 16:22:45 +02:00
Added a first pass at sort-by
2019-05-17 17:55:50 +02: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 03:21:00 +01:00
checksum = "18869315e81473c951eb56ad5558bbc56978562d3ecfb87abb7a1e944cea4518"
Added a first pass at sort-by
2019-05-17 17:55:50 +02:00
dependencies = [
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
"num-traits 0.2.11",
Restructure and make commands uniform
2019-05-22 09:12:03 +02:00
]
Add tree sink
2019-06-07 09:50:26 +02: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 03:21:00 +01:00
checksum = "a86ed3f5f244b372d6b1a00b72ef7f8876d0bc6a78a4c9985c53614041512063"
Add tree sink
2019-06-07 09:50:26 +02:00
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
[[package]]
name = "os_info"
version = "1.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a418a25db1f8465de856d534c6f0c6f3725ad1f089f9a842a7d7c0209ba58e90"
dependencies = [
"lazy_static 1.4.0",
"log",
"regex",
"serde 1.0.104",
"serde_derive",
"winapi 0.3.8",
]
Custom lexer
2019-05-29 17:26:45 +02: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 03:21:00 +01:00
checksum = "53cdc5b785b7a58c5aad8216b3dfa114df64b0b06ae6e1501cef91df2fbdf8f9"
Custom lexer
2019-05-29 17:26:45 +02: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 03:21:00 +01:00
"winapi 0.3.8",
Last unwraps (#1160) * Work through most of the last unwraps * Finish removing unwraps
2020-01-04 07:44:17 +01: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 17:26:45 +02: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 15:47:30 +02: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 03:21:00 +01: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 15:47:30 +02:00
bump deps
2019-07-29 09:46:24 +02:00
[[package]]
name = "percent-encoding"
Pin semver breaking dep
2019-08-08 19:33:19 +02:00
version = "2.1.0"
bump deps
2019-07-29 09:46:24 +02: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 03:21:00 +01:00
checksum = "d4fd5641d01c8f18a23da7b6fe29298ff4b55afcccdf78973b24cf3175fee32e"
bump deps
2019-07-29 09:46:24 +02:00
Add tree sink
2019-06-07 09:50:26 +02: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 03:21:00 +01:00
checksum = "9c3659d1ee90221741f65dd128d9998311b0e40c5d3c23a62445938214abce4f"
Add tree sink
2019-06-07 09:50:26 +02: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 03:21:00 +01:00
"fixedbitset",
"ordermap",
Add tree sink
2019-06-07 09:50:26 +02:00
]
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
[[package]]
name = "pin-project"
version = "0.4.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "94b90146c7216e4cb534069fb91366de4ea0ea353105ee45ed297e2d1619e469"
dependencies = [
"pin-project-internal",
]
[[package]]
name = "pin-project-internal"
version = "0.4.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "44ca92f893f0656d3cba8158dd0f2b99b94de256a4a54e870bd6922fcc6c8355"
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 07:45:27 +01:00
[[package]]
name = "pin-project-lite"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f0af6cbca0e6e3ce8692ee19fb8d734b641899e07b68eb73e9bbbd32f1703991"
Small restructuring
2019-05-23 06:30:43 +02: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 03:21:00 +01:00
checksum = "5894c618ce612a3fa23881b152b608bafb8c56cfc22f434a3ba3120b40f7b587"
Small restructuring
2019-05-23 06:30:43 +02:00
Bat
2019-05-18 03:24:13 +02:00
[[package]]
name = "pkg-config"
Merge master
2019-11-16 18:17:05 +01:00
version = "0.3.17"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
checksum = "05da548ad6865900e60eaba7f589cc0783590a92e940c26953ff81ddbab2d677"
Bat
2019-05-18 03:24:13 +02:00
Update plugin protocol for begin, and create new sys plugin
2019-07-27 09:45:00 +02:00
[[package]]
name = "platforms"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
version = "0.2.1"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
checksum = "feb3b2b1033b8a60b4da6ee470325f887758c95d5320f52f9ce0df055a55940e"
Bat
2019-05-18 03:24:13 +02:00
[[package]]
name = "plist"
Merge master
2019-06-22 03:38:17 +02:00
version = "0.4.2"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
checksum = "5f2a9f075f6394100e7c105ed1af73fb1859d6fd14e49d4290d578120beb167f"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01: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 07:45:27 +01: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 03:21:00 +01:00
"xml-rs",
Bat
2019-05-18 03:24:13 +02:00
]
Add some logic for more binary formats
2019-07-05 09:53:09 +02:00
[[package]]
name = "png"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
version = "0.15.2"
Add some logic for more binary formats
2019-07-05 09:53:09 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
checksum = "247cb804bd7fc86d0c2b153d1374265e67945875720136ca8fe451f11c6aed52"
Add some logic for more binary formats
2019-07-05 09:53:09 +02: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 03:21:00 +01:00
"bitflags",
"crc32fast",
"deflate",
"inflate",
Add some logic for more binary formats
2019-07-05 09:53:09 +02:00
]
Add from_xlsx for importing excel files
2019-11-17 04:18:41 +01: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 03:21:00 +01:00
checksum = "780fb4b6698bbf9cf2444ea5d22411cef2953f0824b98f33cf454ec5615645bd"
Add from_xlsx for importing excel files
2019-11-17 04:18:41 +01:00
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
[[package]]
name = "ppv-lite86"
Merge master
2019-11-16 18:17:05 +01:00
version = "0.2.6"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02: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 03:21:00 +01:00
checksum = "74490b50b9fbe561ac330df47c08f3f33073d2d00c150f719147d7c54522fa1b"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
--no-edit
2019-11-04 16:47:03 +01: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 03:21:00 +01:00
checksum = "f60c0d9f6fc88ecdd245d90c1920ff76a430ab34303fc778d33b1d0a4c3bf6d3"
--no-edit
2019-11-04 16:47:03 +01: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 03:21:00 +01:00
"typed-arena",
--no-edit
2019-11-04 16:47:03 +01:00
]
Add pretty binary viewing
2019-07-04 07:23:05 +02:00
[[package]]
name = "pretty-hex"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
version = "0.1.1"
Add pretty binary viewing
2019-07-04 07:23:05 +02: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 03:21:00 +01:00
checksum = "be91bcc43e73799dc46a6c194a55e7aae1d86cc867c860fd4a436019af21bd8c"
Add pretty binary viewing
2019-07-04 07:23:05 +02:00
Custom lexer
2019-05-29 17:26:45 +02: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 03:21:00 +01:00
checksum = "3f81e1644e1b54f5a68959a29aa86cde704219254669da328ecfdf6a1f09d427"
Custom lexer
2019-05-29 17:26:45 +02: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 03:21:00 +01:00
"ansi_term 0.11.0",
"ctor",
"difference",
"output_vt100",
Custom lexer
2019-05-29 17:26:45 +02:00
]
A real parser (lalrpop)
2019-05-26 08:54:41 +02:00
[[package]]
name = "pretty_env_logger"
Remove X11 requirement
2019-08-23 05:29:08 +02:00
version = "0.3.1"
A real parser (lalrpop)
2019-05-26 08:54:41 +02: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 03:21:00 +01:00
checksum = "717ee476b1690853d222af4634056d830b5197ffd747726a9a1eee6da9f49074"
A real parser (lalrpop)
2019-05-26 08:54:41 +02: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 03:21:00 +01:00
"chrono",
"env_logger",
"log",
A real parser (lalrpop)
2019-05-26 08:54:41 +02:00
]
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "0fd04b170004fa2daccf418a7f8253aaf033c27760b5f225889024cf66d7ac2e"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
"atty",
"csv",
"encode_unicode",
"lazy_static 1.4.0",
"term",
"unicode-width",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
--no-edit
2019-11-04 16:47:03 +01: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 03:21:00 +01:00
checksum = "ecd45702f76d6d3c75a80564378ae228a85f0b59d2f3ed43c91b4a69eb2ebfc5"
--no-edit
2019-11-04 16:47:03 +01: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 03:21:00 +01:00
"proc-macro2",
"quote",
"syn",
--no-edit
2019-11-04 16:47:03 +01: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 03:21:00 +01:00
checksum = "369a6ed065f249a159e06c45752c780bda2fb53c995718f9e484d08daa9eb42e"
--no-edit
2019-11-04 16:47:03 +01:00
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "proc-macro2"
Merge master
2019-11-16 18:17:05 +01:00
version = "1.0.6"
switch from reqwest to surf
2019-08-24 21:36:19 +02: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 03:21:00 +01:00
checksum = "9c9e470a8dc4aeae2dee2f335e8f533e2d4b347e1434e5671afc49b054592f27"
switch from reqwest to surf
2019-08-24 21:36:19 +02: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 03:21:00 +01:00
"unicode-xid",
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
]
Add tree sink
2019-06-07 09:50:26 +02: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 03:21:00 +01:00
checksum = "6b0a3be00b19ee7bd33238c1c523a7ab4df697345f6b36f90827a7860ea938d4"
Add tree sink
2019-06-07 09:50:26 +02: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 03:21:00 +01: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 07:45:27 +01: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 03:21:00 +01:00
"serde-value",
"serde_derive",
"tint",
Add tree sink
2019-06-07 09:50:26 +02: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 03:30:48 +01: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 03:21:00 +01: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 03:30:48 +01:00
Bat
2019-05-18 03:24:13 +02:00
[[package]]
name = "quick-error"
version = "1.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 03:21:00 +01:00
checksum = "9274b940887ce9addde99c4eee6b5c44cc494b182b97e73dc8ffdcb3397fd3f0"
Bat
2019-05-18 03:24:13 +02:00
Add from_xlsx for importing excel files
2019-11-17 04:18:41 +01: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 07:45:27 +01:00
version = "0.17.2"
Add from_xlsx for importing excel files
2019-11-17 04:18:41 +01: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 07:45:27 +01:00
checksum = "fe1e430bdcf30c9fdc25053b9c459bb1a4672af4617b6c783d7d91dc17c6bbb0"
Add from_xlsx for importing excel files
2019-11-17 04:18:41 +01: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 03:21:00 +01:00
"encoding_rs",
"memchr",
Add from_xlsx for importing excel files
2019-11-17 04:18:41 +01:00
]
switch from reqwest to surf
2019-08-24 21:36:19 +02: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 03:21:00 +01:00
checksum = "053a8c8bcc71fcce321828dc897a98ab9760bef03a4fc36693c231e5b3216cfe"
switch from reqwest to surf
2019-08-24 21:36:19 +02: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 03:21:00 +01:00
"proc-macro2",
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
]
Bat
2019-05-18 03:24:13 +02:00
[[package]]
name = "rand"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
version = "0.7.2"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02: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 03:21:00 +01:00
checksum = "3ae1b169243eaf61759b8475a998f0a385e42042370f3a7dbaf35246eacc8412"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02: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 03:21:00 +01:00
"getrandom",
"libc",
"rand_chacha",
"rand_core 0.5.1",
"rand_hc",
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
]
[[package]]
name = "rand_chacha"
bump deps
2019-07-29 09:46:24 +02:00
version = "0.2.1"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02: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 03:21:00 +01:00
checksum = "03a2a90da8c7523f554344f921aa97283eadf6ac484a6d2a7d0212fa7f8d6853"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02: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 03:21:00 +01:00
"c2-chacha",
"rand_core 0.5.1",
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "rand_core"
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 03:21:00 +01:00
checksum = "7a6fdeb83b075e8266dcc8762c22776f6877a63111121f5f8c7411e5be7eed4b"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
"rand_core 0.4.2",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
[[package]]
name = "rand_core"
Pin semver breaking dep
2019-08-08 19:33:19 +02:00
version = "0.4.2"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "9c33a3c44ca05fa6f1807d8e6743f3824e8509beca625669633be0acbdf509dc"
objectshell initial commit
2019-05-10 18:59:12 +02:00
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
[[package]]
name = "rand_core"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
version = "0.5.1"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
checksum = "90bde5296fc891b0cef12a6d03ddccc162ce7b2aff54160af9338f8d40df6d19"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
"getrandom",
Bat
2019-05-18 03:24:13 +02:00
]
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02: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 03:21:00 +01:00
checksum = "ca3129af7b92a17112d59ad498c6f81eaf463253766b90396d39ea7a39d6613c"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02: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 03:21:00 +01:00
"rand_core 0.5.1",
Bat
2019-05-18 03:24:13 +02:00
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "rand_os"
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 03:21:00 +01:00
checksum = "7b75f676a1e053fc562eafbb47838d67c84801e38fc1ba459e8f180deabd5071"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
"cloudabi",
"fuchsia-cprng",
"libc",
"rand_core 0.4.2",
"rdrand",
"winapi 0.3.8",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
Update plugin protocol for begin, and create new sys plugin
2019-07-27 09:45:00 +02:00
[[package]]
name = "raw-cpuid"
Add Cargo.lock
2019-09-24 21:02:35 +02:00
version = "7.0.3"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 09:45:00 +02: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 03:21:00 +01:00
checksum = "b4a349ca83373cfa5d6dbb66fd76e58b2cca08da71a5f6400de0a0a6a9bceeaf"
Update plugin protocol for begin, and create new sys plugin
2019-07-27 09:45:00 +02: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 03:21:00 +01:00
"bitflags",
"cc",
"rustc_version",
Update plugin protocol for begin, and create new sys plugin
2019-07-27 09:45:00 +02:00
]
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
[[package]]
name = "rawkey"
Move off of git deps
2019-08-02 05:58:10 +02:00
version = "0.1.2"
Cleanup for upcoming release
2019-07-16 21:10:25 +02: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 03:21:00 +01:00
checksum = "33ec17a493dcb820725c002bc253f6f3ba4e4dc635e72c238540691b05e43897"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02: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 03:21:00 +01:00
"readkey",
"user32-sys",
"winapi 0.3.8",
"x11",
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02: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 15:47:30 +02: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 07:45:27 +01: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 15:47:30 +02: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 07:45:27 +01: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 15:47:30 +02: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 03:21:00 +01: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 15:47:30 +02: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 07:45:27 +01: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 15:47:30 +02: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 07:45:27 +01: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 15:47:30 +02: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 03:21:00 +01: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 15:47:30 +02:00
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "rdrand"
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 03:21:00 +01:00
checksum = "678054eb77286b51581ba43620cc911abf02758c91f93f479767aed0f90458b2"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
"rand_core 0.3.1",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02: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 07:45:27 +01:00
version = "0.1.7"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02: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 07:45:27 +01:00
checksum = "86d401b6d6a1725a59f1b4e813275d289dff3ad09c72b373a10a7a8217ba3146"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "redox_syscall"
bump deps
2019-07-29 09:46:24 +02:00
version = "0.1.56"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "2439c63f3f6139d1b57529d16bc3b8bb855230c8efcc5d3a896c8bea7c3b1e84"
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "redox_users"
Pin semver breaking dep
2019-08-08 19:33:19 +02:00
version = "0.3.1"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "4ecedbca3bf205f8d8f5c2b44d83cd0690e39ee84b951ed649e9f1841132b66d"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
"failure",
"rand_os",
"redox_syscall",
"rust-argon2",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
[[package]]
name = "regex"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
version = "1.3.1"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "dc220bd33bdce8f093101afe22a037b8eb0e5af33592e6a9caafff0d4cb81cbd"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
"aho-corasick",
"memchr",
"regex-syntax",
"thread_local",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
Introduced ability to open csv documents.
2019-07-19 22:11:49 +02:00
[[package]]
name = "regex-automata"
bump deps
2019-07-29 09:46:24 +02:00
version = "0.1.8"
Introduced ability to open csv documents.
2019-07-19 22:11:49 +02: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 03:21:00 +01:00
checksum = "92b73c2a1770c255c240eaa4ee600df1704a38dc3feaa6e949e7fcd4f8dc09f9"
Introduced ability to open csv documents.
2019-07-19 22:11:49 +02: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 03:21:00 +01:00
"byteorder",
Introduced ability to open csv documents.
2019-07-19 22:11:49 +02:00
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "regex-syntax"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
version = "0.6.12"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "11a7e20d1cce64ef2fed88b66d347f88bd9babb82845b2b858f3edbf59a4f716"
objectshell initial commit
2019-05-10 18:59:12 +02:00
Add opening urls
2019-06-08 20:09:17 +02:00
[[package]]
name = "remove_dir_all"
Merge master
2019-06-22 03:38:17 +02:00
version = "0.5.2"
Add opening urls
2019-06-08 20:09:17 +02: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 03:21:00 +01:00
checksum = "4a83fa3702a688b9359eccba92d153ac33fd2e8462f9e0e3fdf155239ea7792e"
Add opening urls
2019-06-08 20:09:17 +02: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 03:21:00 +01:00
"winapi 0.3.8",
Add opening urls
2019-06-08 20:09:17 +02:00
]
Better errors and more fleshed out semantics
2019-05-30 06:19:46 +02:00
[[package]]
name = "render-tree"
version = "0.1.1"
Update cargo.lock
2019-10-16 04:09:47 +02: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 03:21:00 +01:00
checksum = "68ed587df09cfb7ce1bc6fe8f77e24db219f222c049326ccbfb948ec67e31664"
Better errors and more fleshed out semantics
2019-05-30 06:19:46 +02: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 03:21:00 +01:00
"itertools 0.7.11",
"log",
"termcolor",
Better errors and more fleshed out semantics
2019-05-30 06:19:46 +02:00
]
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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",
"bytes 0.5.3",
"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",
"wasm-bindgen-futures 0.4.6",
"web-sys",
"webpki-roots",
"winreg",
]
Add .ini loading/saving
2019-06-16 08:43:40 +02: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 03:21:00 +01:00
checksum = "194d8e591e405d1eecf28819740abed6d719d1a2db87fc0bcdedee9a26d55560"
Add .ini loading/saving
2019-06-16 08:43:40 +02:00
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
[[package]]
name = "ring"
version = "0.16.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6747f8da1f2b1fabbee1aaa4eb8a11abf9adef0bf58a41cee45db5d59cecdfac"
dependencies = [
"cc",
"lazy_static 1.4.0",
"libc",
"spin",
"untrusted",
"web-sys",
"winapi 0.3.8",
]
Add xml open support
2019-06-11 08:26:03 +02:00
[[package]]
name = "roxmltree"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
version = "0.9.0"
Add xml open support
2019-06-11 08:26:03 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
checksum = "708ee8345e5b70c86aca5ab03bb7d961349b5b2fa7939d3b131af487101de2f3"
Add xml open support
2019-06-11 08:26:03 +02: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 03:21:00 +01:00
"xmlparser",
Add xml open support
2019-06-11 08:26:03 +02:00
]
Add SQLite support
2019-08-27 23:45:18 +02:00
[[package]]
name = "rusqlite"
Restructure and streamline token expansion (#1123) Restructure and streamline token expansion The purpose of this commit is to streamline the token expansion code, by removing aspects of the code that are no longer relevant, removing pointless duplication, and eliminating the need to pass the same arguments to `expand_syntax`. The first big-picture change in this commit is that instead of a handful of `expand_` functions, which take a TokensIterator and ExpandContext, a smaller number of methods on the `TokensIterator` do the same job. The second big-picture change in this commit is fully eliminating the coloring traits, making coloring a responsibility of the base expansion implementations. This also means that the coloring tracer is merged into the expansion tracer, so you can follow a single expansion and see how the expansion process produced colored tokens. One side effect of this change is that the expander itself is marginally more error-correcting. The error correction works by switching from structured expansion to `BackoffColoringMode` when an unexpected token is found, which guarantees that all spans of the source are colored, but may not be the most optimal error recovery strategy. That said, because `BackoffColoringMode` only extends as far as a closing delimiter (`)`, `]`, `}`) or pipe (`|`), it does result in fairly granular correction strategy. The current code still produces an `Err` (plus a complete list of colored shapes) from the parsing process if any errors are encountered, but this could easily be addressed now that the underlying expansion is error-correcting. This commit also colors any spans that are syntax errors in red, and causes the parser to include some additional information about what tokens were expected at any given point where an error was encountered, so that completions and hinting could be more robust in the future. Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com> Co-authored-by: Andrés N. Robalino <andres@androbtech.com>
2020-01-21 23:45:03 +01:00
version = "0.20.0"
Add SQLite support
2019-08-27 23:45:18 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Restructure and streamline token expansion (#1123) Restructure and streamline token expansion The purpose of this commit is to streamline the token expansion code, by removing aspects of the code that are no longer relevant, removing pointless duplication, and eliminating the need to pass the same arguments to `expand_syntax`. The first big-picture change in this commit is that instead of a handful of `expand_` functions, which take a TokensIterator and ExpandContext, a smaller number of methods on the `TokensIterator` do the same job. The second big-picture change in this commit is fully eliminating the coloring traits, making coloring a responsibility of the base expansion implementations. This also means that the coloring tracer is merged into the expansion tracer, so you can follow a single expansion and see how the expansion process produced colored tokens. One side effect of this change is that the expander itself is marginally more error-correcting. The error correction works by switching from structured expansion to `BackoffColoringMode` when an unexpected token is found, which guarantees that all spans of the source are colored, but may not be the most optimal error recovery strategy. That said, because `BackoffColoringMode` only extends as far as a closing delimiter (`)`, `]`, `}`) or pipe (`|`), it does result in fairly granular correction strategy. The current code still produces an `Err` (plus a complete list of colored shapes) from the parsing process if any errors are encountered, but this could easily be addressed now that the underlying expansion is error-correcting. This commit also colors any spans that are syntax errors in red, and causes the parser to include some additional information about what tokens were expected at any given point where an error was encountered, so that completions and hinting could be more robust in the future. Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com> Co-authored-by: Andrés N. Robalino <andres@androbtech.com>
2020-01-21 23:45:03 +01:00
checksum = "2a194373ef527035645a1bc21b10dc2125f73497e6e155771233eb187aedd051"
Add SQLite support
2019-08-27 23:45:18 +02: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 03:21:00 +01:00
"bitflags",
"fallible-iterator",
"fallible-streaming-iterator",
"libsqlite3-sys",
"lru-cache",
"memchr",
"time",
Add SQLite support
2019-08-27 23:45:18 +02:00
]
Pin semver breaking dep
2019-08-08 19:33:19 +02:00
[[package]]
name = "rust-argon2"
Update rust-argon2 in Cargo.lock Rids us of crossbeam v0.5 and lots of other crates. For most users this only effects Cargo.lock though, as rust-argon2 is only compiled when targeting redox.
2019-09-06 10:34:31 +02:00
version = "0.5.1"
Pin semver breaking dep
2019-08-08 19:33:19 +02: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 03:21:00 +01:00
checksum = "4ca4eaef519b494d1f2848fc602d18816fed808a981aedf4f1f00ceb7c9d32cf"
Pin semver breaking dep
2019-08-08 19:33:19 +02: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 03:21:00 +01:00
"base64 0.10.1",
"blake2b_simd",
"crossbeam-utils 0.6.6",
Pin semver breaking dep
2019-08-08 19:33:19 +02:00
]
Add tree sink
2019-06-07 09:50:26 +02: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 03:21:00 +01:00
checksum = "3e52c148ef37f8c375d49d5a73aa70713125b7f19095948a923f80afdeb22ec2"
Add tree sink
2019-06-07 09:50:26 +02:00
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "rustc-demangle"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
version = "0.1.16"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "4c691c0e608126e00913e33f0ccf3727d5fc84573623b8d65b2df340b5201783"
objectshell initial commit
2019-05-10 18:59:12 +02:00
Update bson to 0.14
2019-08-31 16:22:45 +02: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 03:21:00 +01:00
checksum = "dcf128d1287d2ea9d80910b5f1120d0b8eede3fbf1abe91c40d39ea7d51e6fda"
Update bson to 0.14
2019-08-31 16:22:45 +02:00
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
checksum = "138e3e0acb6c9fb258b19b67cb8abd63c00679d2851805ea151465464fe9030a"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
"semver",
Bat
2019-05-18 03:24:13 +02:00
]
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 18:59:12 +02: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 04:41:17 +01:00
version = "6.0.0"
Bump rustyline (#1146) * Slightly improve new which command * Bump rustyline
2020-01-01 18:54:25 +01: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 04:41:17 +01:00
checksum = "de64be8eecbe428b6924f1d8430369a01719fbb182c26fa431ddbb0a95f5315d"
objectshell initial commit
2019-05-10 18:59:12 +02:00
dependencies = [
Bump heim and necessary deps
2019-12-14 14:27:14 +01: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 03:21:00 +01: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 18:59:12 +02:00
]
Bump and cleanup plugin name match
2019-07-04 05:06:43 +02:00
[[package]]
name = "ryu"
Merge master
2019-11-16 18:17:05 +01:00
version = "1.0.2"
Bump and cleanup plugin name match
2019-07-04 05:06:43 +02: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 03:21:00 +01:00
checksum = "bfa8506c1de11c9c4e4c38863ccbe02a305c8188e85a05a784c9e11e1c3910c8"
Bump and cleanup plugin name match
2019-07-04 05:06:43 +02:00
Bat
2019-05-18 03:24:13 +02:00
[[package]]
name = "safemem"
Merge master
2019-11-16 18:17:05 +01:00
version = "0.3.3"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
checksum = "ef703b7cb59335eae2eb93ceb664c0eb7ea6bf567079d843e09420219668e072"
Bat
2019-05-18 03:24:13 +02:00
[[package]]
name = "same-file"
bump deps
2019-07-29 09:46:24 +02:00
version = "1.0.5"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
checksum = "585e8ddcedc187886a30fa705c47985c3fa88d06624095856b36ca0b82ff4421"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
"winapi-util",
Bat
2019-05-18 03:24:13 +02:00
]
Add opening urls
2019-06-08 20:09:17 +02:00
[[package]]
name = "schannel"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
version = "0.1.16"
Add opening urls
2019-06-08 20:09:17 +02: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 03:21:00 +01:00
checksum = "87f550b06b6cba9c8b8be3ee73f391990116bf527450d2556e9b9ce263b9a021"
Add opening urls
2019-06-08 20:09:17 +02: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 03:21:00 +01:00
"lazy_static 1.4.0",
"winapi 0.3.8",
Add opening urls
2019-06-08 20:09:17 +02: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 15:47:30 +02: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 03:21:00 +01: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 15:47:30 +02:00
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 03:24:13 +02: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 03:21:00 +01:00
checksum = "1d7eb9ef2c18661902cc47e535f9bc51b78acd254da71d375c2f6720d9a40403"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
"semver-parser",
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
checksum = "388a1df253eca08550bef6c72392cfe7c30914bf41df5269b68cbd6ff8f570a3"
Bat
2019-05-18 03:24:13 +02:00
Lots of misc improvements
2019-06-03 09:41:28 +02: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 03:21:00 +01:00
checksum = "9dad3f759919b92c3068c696c15c3d17238234498bbdcc80f2c469606f948ac8"
Lots of misc improvements
2019-06-03 09:41:28 +02:00
objectshell initial commit
2019-05-10 18:59:12 +02: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 07:45:27 +01:00
version = "1.0.104"
objectshell initial commit
2019-05-10 18:59:12 +02: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 07:45:27 +01:00
checksum = "414115f25f818d7dfccec8ee535d76949ae78584fc4f79a6f45a904bf8ab4449"
Add opening urls
2019-06-08 20:09:17 +02: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 03:21:00 +01:00
"serde_derive",
Add opening urls
2019-06-08 20:09:17 +02:00
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
Add tree sink
2019-06-07 09:50:26 +02: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 03:21:00 +01:00
checksum = "0b833c5ad67d52ced5f5938b2980f32a9c1c5ef047f0b4fb3127e7a423c76153"
Add tree sink
2019-06-07 09:50:26 +02: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 03:21:00 +01: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 09:50:26 +02:00
]
Lots of misc improvements
2019-06-03 09:41:28 +02:00
[[package]]
name = "serde-hjson"
Remove X11 requirement
2019-08-23 05:29:08 +02:00
version = "0.9.1"
Lots of misc improvements
2019-06-03 09:41:28 +02: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 03:21:00 +01:00
checksum = "6a3a4e0ea8a88553209f6cc6cfe8724ecad22e1acf372793c27d995290fe74f8"
Lots of misc improvements
2019-06-03 09:41:28 +02: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 03:21:00 +01: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 09:41:28 +02:00
]
Add tree sink
2019-06-07 09:50:26 +02: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 03:21:00 +01:00
checksum = "7a663f873dedc4eac1a559d4c6bc0d0b2c34dc5ac4702e105014b8281489e44f"
Add tree sink
2019-06-07 09:50:26 +02: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 03:21:00 +01: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 07:45:27 +01:00
"serde 1.0.104",
Add tree sink
2019-06-07 09:50:26 +02:00
]
Bump deps and add serde_bytes support
2019-07-15 20:34:44 +02:00
[[package]]
name = "serde_bytes"
Upgrade some dependencies
2019-12-08 18:56:21 +01:00
version = "0.11.3"
Bump deps and add serde_bytes support
2019-07-15 20:34:44 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade some dependencies
2019-12-08 18:56:21 +01:00
checksum = "325a073952621257820e7a3469f55ba4726d8b28657e7e36653d1c36dc2c84ae"
Bump deps and add serde_bytes support
2019-07-15 20:34:44 +02: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 07:45:27 +01:00
"serde 1.0.104",
Bump deps and add serde_bytes support
2019-07-15 20:34:44 +02:00
]
Bat
2019-05-18 03:24:13 +02: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 07:45:27 +01:00
version = "1.0.104"
Bat
2019-05-18 03:24:13 +02: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 07:45:27 +01:00
checksum = "128f9e303a5a29922045a830221b8f78ec74a5f544944f3d5984f8ec3895ef64"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
"proc-macro2",
"quote",
"syn",
Bat
2019-05-18 03:24:13 +02:00
]
Add .ini loading/saving
2019-06-16 08:43:40 +02: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 03:21:00 +01:00
checksum = "eb236687e2bb073a7521c021949be944641e671b8505a94069ca37b656c81139"
Add .ini loading/saving
2019-06-16 08:43:40 +02: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 03:21:00 +01: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 07:45:27 +01: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 03:21:00 +01:00
"void",
Add a bunch more tokens and delimited ()
2019-06-12 19:44:45 +02:00
]
Bat
2019-05-18 03:24:13 +02:00
[[package]]
name = "serde_json"
Upgrade some dependencies
2019-12-08 18:56:21 +01:00
version = "1.0.44"
Bat
2019-05-18 03:24:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Upgrade some dependencies
2019-12-08 18:56:21 +01:00
checksum = "48c575e0cc52bdd09b47f330f646cf59afc586e9c4e3ccd6fc1f625b8ea1dad7"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01: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 07:45:27 +01:00
"serde 1.0.104",
Bat
2019-05-18 03:24:13 +02:00
]
Lots of misc improvements
2019-06-03 09:41:28 +02: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 03:21:00 +01:00
checksum = "110b3dbdf8607ec493c22d5d947753282f3bae73c0f56d322af1e8c78e4c23d5"
Lots of misc improvements
2019-06-03 09:41:28 +02: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 03:21:00 +01:00
"serde 0.8.23",
Lots of misc improvements
2019-06-03 09:41:28 +02:00
]
Add opening urls
2019-06-08 20:09:17 +02:00
[[package]]
name = "serde_urlencoded"
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
version = "0.6.1"
Add opening urls
2019-06-08 20:09:17 +02: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 03:21:00 +01:00
checksum = "9ec5d77e2d4c73717816afac02670d5c4f534ea95ed430442cad02e7a6e32c97"
Add opening urls
2019-06-08 20:09:17 +02: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 03:21:00 +01: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 07:45:27 +01: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 03:21:00 +01:00
"url",
Add opening urls
2019-06-08 20:09:17 +02:00
]
Lots of misc improvements
2019-06-03 09:41:28 +02:00
[[package]]
name = "serde_yaml"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
version = "0.8.11"
Lots of misc improvements
2019-06-03 09:41:28 +02: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 03:21:00 +01:00
checksum = "691b17f19fc1ec9d94ec0b5864859290dff279dbd7b03f017afda54eb36c3c35"
Lots of misc improvements
2019-06-03 09:41:28 +02: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 03:21:00 +01: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 07:45:27 +01: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 03:21:00 +01:00
"yaml-rust",
Lots of misc improvements
2019-06-03 09:41:28 +02:00
]
Improve signature infrastructure The `config` command uses different kinds of named arguments, which illustrates how it works.
2019-06-01 07:50:16 +02: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 03:21:00 +01:00
checksum = "9ee04b46101f57121c9da2b151988283b6beb79b34f5bb29a58ee48cb695122c"
Improve signature infrastructure The `config` command uses different kinds of named arguments, which illustrates how it works.
2019-06-01 07:50:16 +02: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 03:21:00 +01: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 07:50:16 +02: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 21:21:03 +02:00
[[package]]
name = "shellexpand"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 21:21:03 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 07:45:27 +01:00
dependencies = [
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 07:45:27 +01: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 21:21:03 +02:00
Upgrade crossterm (#1288) * WIP * Finish porting to new crossterm * Fmt
2020-01-27 03:51:46 +01: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 06:30:43 +02: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 03:21:00 +01:00
checksum = "c111b5bd5695e56cffe5129854aa230b39c93a305372fdbb2668ca2394eea9f8"
Small restructuring
2019-05-23 06:30:43 +02:00
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
[[package]]
name = "sluice"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
version = "0.4.2"
switch from reqwest to surf
2019-08-24 21:36:19 +02: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 03:21:00 +01:00
checksum = "0a7d06dfb3e8743bc19e6de8a302277471d08077d68946b307280496dc5a3531"
switch from reqwest to surf
2019-08-24 21:36:19 +02: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 03:21:00 +01:00
"futures-channel-preview",
"futures-core-preview",
"futures-io-preview",
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
]
Bat
2019-05-18 03:24:13 +02:00
[[package]]
name = "smallvec"
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 07:45:27 +01:00
version = "1.1.0"
Bat
2019-05-18 03:24:13 +02: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 07:45:27 +01:00
checksum = "44e59e0c9fa00817912ae6e4e6e3c4fe04455e75699d06eedc7d85917ed8e8f4"
Bat
2019-05-18 03:24:13 +02:00
switch from reqwest to surf
2019-08-24 21:36:19 +02: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 03:21:00 +01:00
checksum = "e8b74de517221a2cb01a53349cf54182acdc31a074727d3079068448c0676d85"
switch from reqwest to surf
2019-08-24 21:36:19 +02: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 03:21:00 +01:00
"cfg-if",
"libc",
"redox_syscall",
"winapi 0.3.8",
switch from reqwest to surf
2019-08-24 21:36:19 +02: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 03:21:00 +01:00
checksum = "4bf77cb82ba8453b42b6ae1d692e4cdc92f9a47beaf89a847c8be83f4e328ad3"
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 15:47:30 +02:00
[[package]]
name = "starship"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
version = "0.33.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 03:21:00 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
checksum = "91efa8a7ad3da400fa610a1f49f9aca455de4082913a48e2f3d6cad64813459d"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01: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 21:35:48 +01: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 03:21:00 +01:00
"once_cell",
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 03:21:00 +01:00
"path-slash",
"pretty_env_logger",
"rayon",
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 03:21:00 +01:00
"serde_json",
"starship_module_config_derive",
"sysinfo",
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 03:21:00 +01:00
"unicode-segmentation",
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 03:21:00 +01: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 15:47:30 +02:00
]
[[package]]
name = "starship_module_config_derive"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
version = "0.1.1"
chore: switch starship dependency back to the main one
2019-10-09 09:36:55 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump heim and necessary deps
2019-12-14 14:27:14 +01: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 15:47:30 +02: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 03:21:00 +01: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 15:47:30 +02:00
]
WIP
2019-06-22 05:43:37 +02:00
[[package]]
name = "static_assertions"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
version = "0.3.4"
WIP
2019-06-22 05:43:37 +02: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 03:21:00 +01:00
checksum = "7f3eb36b47e512f8f1c9e3d10c2c1965bc992bd9cdb024fa581e2194501c83d3"
WIP
2019-06-22 05:43:37 +02:00
Give rustyline non-ansi to begin with. Fixes Windows
2019-11-16 21:02:26 +01: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 03:21:00 +01:00
checksum = "9d63676e2abafa709460982ddc02a3bb586b6d15a49b75c212e06edd3933acee"
Give rustyline non-ansi to begin with. Fixes Windows
2019-11-16 21:02:26 +01: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 03:21:00 +01:00
"vte",
Give rustyline non-ansi to begin with. Fixes Windows
2019-11-16 21:02:26 +01:00
]
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
checksum = "8ea5119cdb4c55b55d432abb513a0429384878c15dde60cc77b1c99de1a95a6a"
Bat
2019-05-18 03:24:13 +02:00
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
[[package]]
name = "surf"
Bump dep versions
2019-11-10 18:48:49 +01:00
version = "1.0.3"
switch from reqwest to surf
2019-08-24 21:36:19 +02: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 03:21:00 +01:00
checksum = "741a8008f8a833ef16f47df94a30754478fb2c2bf822b9c2e6f7f09203b97ace"
switch from reqwest to surf
2019-08-24 21:36:19 +02: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 03:21:00 +01:00
"futures-preview",
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 03:21:00 +01: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 07:45:27 +01: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 03:21:00 +01:00
"serde_json",
"serde_urlencoded",
"url",
"wasm-bindgen",
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 03:21:00 +01:00
"web-sys",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
[[package]]
name = "syn"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
version = "1.0.11"
switch from reqwest to surf
2019-08-24 21:36:19 +02: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 03:21:00 +01:00
checksum = "dff0acdb207ae2fe6d5976617f887eb1e35a2ba52c13c7234c790960cdad9238"
switch from reqwest to surf
2019-08-24 21:36:19 +02: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 03:21:00 +01:00
"proc-macro2",
"quote",
"unicode-xid",
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "synstructure"
Merge master
2019-11-16 18:17:05 +01:00
version = "0.12.3"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "67656ea1dc1b41b1451851562ea232ec2e5a80242139f7e679ceccfb5d61f545"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
"proc-macro2",
"quote",
"syn",
"unicode-xid",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
Bat
2019-05-18 03:24:13 +02:00
[[package]]
name = "syntect"
Revert bump
2019-08-10 08:31:31 +02:00
version = "3.2.0"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
checksum = "e80b8831c5a543192ffc3727f01cf0e57579c6ac15558e3048bfb5708892167b"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01: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 07:45:27 +01: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 03:21:00 +01:00
"serde_derive",
"serde_json",
"walkdir",
"yaml-rust",
Bat
2019-05-18 03:24:13 +02: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 15:47:30 +02:00
[[package]]
name = "sysinfo"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
version = "0.10.4"
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 15:47:30 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
checksum = "99474859bbf2710ae8f09912a047cfe24d2c1076af9eb86661eb906ca7d1e994"
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 15:47:30 +02: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 03:21:00 +01:00
"cfg-if",
"doc-comment",
"libc",
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 03:21:00 +01: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 15:47:30 +02:00
]
Add opening urls
2019-06-08 20:09:17 +02:00
[[package]]
name = "tempfile"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
version = "3.1.0"
Add opening urls
2019-06-08 20:09:17 +02: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 03:21:00 +01:00
checksum = "7a6e24d9338a0a5be79593e2fa15a648add6138caa803e2d5bc782c371732ca9"
Add opening urls
2019-06-08 20:09:17 +02: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 03:21:00 +01:00
"cfg-if",
"libc",
"rand",
"redox_syscall",
"remove_dir_all",
"winapi 0.3.8",
Add opening urls
2019-06-08 20:09:17 +02:00
]
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "edd106a334b7657c10b7c540a0106114feadeb4dc314513e97df481d5d966f42"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
"byteorder",
"dirs 1.0.5",
"winapi 0.3.8",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
Wrap table cells as needed
2019-08-16 07:47:47 +02: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 03:21:00 +01:00
checksum = "9e5b9a66db815dcfd2da92db471106457082577c3c278d4138ab3e3b4e189327"
Wrap table cells as needed
2019-08-16 07:47:47 +02: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 03:21:00 +01:00
"kernel32-sys",
"libc",
"winapi 0.2.8",
Wrap table cells as needed
2019-08-16 07:47:47 +02:00
]
A real parser (lalrpop)
2019-05-26 08:54:41 +02:00
[[package]]
name = "termcolor"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
version = "1.1.0"
A real parser (lalrpop)
2019-05-26 08:54:41 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
checksum = "bb6bfa289a4d7c5766392812c0a1f4c1ba45afa1ad47803c11e1f407d846d75f"
A real parser (lalrpop)
2019-05-26 08:54:41 +02:00
dependencies = [
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
"winapi-util",
A real parser (lalrpop)
2019-05-26 08:54:41 +02:00
]
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
checksum = "d326610f408c7a4eb6f51c37c330e496b08506c9457c9d34287ecc38809fb060"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
"term_size",
"unicode-width",
Bat
2019-05-18 03:24:13 +02: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 07:45:27 +01:00
[[package]]
name = "thiserror"
version = "1.0.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6f357d1814b33bc2dc221243f8424104bfe72dbe911d5b71b3816a2dff1c977e"
dependencies = [
"thiserror-impl",
]
[[package]]
name = "thiserror-impl"
version = "1.0.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "eb2e25d25307eb8436894f727aba8f65d07adf02e5b35a13cebed48bd282bfef"
dependencies = [
"proc-macro2",
"quote",
"syn",
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "thread_local"
version = "0.3.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 03:21:00 +01:00
checksum = "c6b53e329000edc2b34dbe8545fd20e55a333362d0a321909685a19bd28c3f1b"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
"lazy_static 1.4.0",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
Pin semver breaking dep
2019-08-08 19:33:19 +02: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 03:21:00 +01:00
checksum = "e2f0c90a5f3459330ac8bc0d2f879c693bb7a2f59689c1083fc4ef83834da865"
Pin semver breaking dep
2019-08-08 19:33:19 +02: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 03:21:00 +01:00
"num_cpus",
Pin semver breaking dep
2019-08-08 19:33:19 +02:00
]
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "db8dcfca086c1143c9270ac42a2bbd8a7ee477b78ac8e45b19abfb0cbede4b6f"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
"libc",
"redox_syscall",
"winapi 0.3.8",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
Add tree sink
2019-06-07 09:50:26 +02: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 03:21:00 +01:00
checksum = "7af24570664a3074673dbbf69a65bdae0ae0b72f2949b1adfbacb736ee4d6896"
Add tree sink
2019-06-07 09:50:26 +02: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 03:21:00 +01:00
"lazy_static 0.2.11",
Add tree sink
2019-06-07 09:50:26 +02:00
]
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
[[package]]
name = "tokio"
version = "0.2.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ffa2fdcfa937b20cb3c822a635ceecd5fc1a27a6a474527e5516aa24b8c8820a"
dependencies = [
"bytes 0.5.3",
"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 20:48:33 +02:00
[[package]]
name = "tokio-io"
version = "0.1.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 03:21:00 +01:00
checksum = "5090db468dad16e1a7a54c8c67280c5e4b544f3d3e018f0b913b400261f85926"
Pipe external to internal Each line is a string object
2019-05-24 20:48:33 +02:00
dependencies = [
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 07:45:27 +01: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 03:21:00 +01:00
"log",
Pipe external to internal Each line is a string object
2019-05-24 20:48:33 +02:00
]
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 = [
"bytes 0.5.3",
"futures-core",
"futures-sink",
"log",
"pin-project-lite",
"tokio",
]
Add tree sink
2019-06-07 09:50:26 +02: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 03:21:00 +01:00
checksum = "758664fc71a3a69038656bee8b6be6477d2a6c315a6b81f7081f591bffa4111f"
Add tree sink
2019-06-07 09:50:26 +02: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 07:45:27 +01:00
"serde 1.0.104",
Add tree sink
2019-06-07 09:50:26 +02:00
]
Restructure and make commands uniform
2019-05-22 09:12:03 +02:00
[[package]]
name = "toml"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
version = "0.5.6"
Restructure and make commands uniform
2019-05-22 09:12:03 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
checksum = "ffc92d160b1eef40665be3a05630d003936a3bc7da7421277846c2613e92c71a"
Restructure and make commands uniform
2019-05-22 09:12:03 +02: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 07:45:27 +01:00
"serde 1.0.104",
Restructure and make commands uniform
2019-05-22 09:12:03 +02:00
]
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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-19 00:41:24 +02:00
[[package]]
name = "trash"
version = "1.0.0"
Restructure and make commands uniform
2019-05-22 09:12:03 +02: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 03:21:00 +01:00
checksum = "f2f24d31505f49e989b1ee2c03c323251f6763d5907d471b71192dac92e323f8"
Restructure and make commands uniform
2019-05-22 09:12:03 +02: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 03:21:00 +01:00
"winapi 0.3.8",
Restructure and make commands uniform
2019-05-22 09:12:03 +02:00
]
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 16:47:03 +01: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 03:21:00 +01:00
checksum = "a9b2228007eba4120145f785df0f6c92ea538f5a3635a612ecf4e334c8c1446d"
--no-edit
2019-11-04 16:47:03 +01:00
add some battery stats
2019-08-11 05:01:09 +02:00
[[package]]
name = "typenum"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
version = "1.11.2"
add some battery stats
2019-08-11 05:01:09 +02: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 03:21:00 +01:00
checksum = "6d2783fe2d6b8c1101136184eb41be8b1ad379e4657050b8aaff0c79ee7575f9"
add some battery stats
2019-08-11 05:01:09 +02: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 03:30:48 +01: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 03:21:00 +01: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 03:30:48 +01: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 03:21:00 +01: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 07:45:27 +01: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 03:21:00 +01: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 03:30:48 +01: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 03:21:00 +01: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 03:30:48 +01: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 03:21:00 +01: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 03:30:48 +01:00
]
Add umask to unix --full list
2019-11-19 06:46:47 +01: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 03:21:00 +01:00
checksum = "d3ec2e5aeb4aadd510db9124513a7fec4a9c3a331b7f57aa519440dab3707067"
Add umask to unix --full list
2019-11-19 06:46:47 +01:00
Add opening urls
2019-06-08 20:09:17 +02:00
[[package]]
name = "unicase"
Merge master
2019-11-16 18:17:05 +01:00
version = "2.6.0"
Add opening urls
2019-06-08 20:09:17 +02: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 03:21:00 +01:00
checksum = "50f37be617794602aabbeee0be4f259dc1778fabe05e2d67ee8f79326d5cb4f6"
Add opening urls
2019-06-08 20:09:17 +02: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 03:21:00 +01:00
"version_check 0.9.1",
Add opening urls
2019-06-08 20:09:17 +02:00
]
Add git branch to prompt
2019-06-01 23:11:28 +02: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 03:21:00 +01:00
checksum = "49f2bd0c6468a8230e1db229cff8029217cf623c767ea5d60bfbd42729ea54d5"
Add git branch to prompt
2019-06-01 23:11:28 +02: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 03:21:00 +01:00
"matches",
Add git branch to prompt
2019-06-01 23:11:28 +02:00
]
[[package]]
name = "unicode-normalization"
Switch to the new Cargo.lock format This was achieved by deleting Cargo.lock and letting a recent Cargo nightly re-create it. Support for the format was already introduced in Rust 1.38, but currently, stable releases of Cargo only retain it if encountered but don't generate such files by default. The new format is smaller, better suited to prevent merge conflicts and generates smaller diffs at dependency updates, leading to smaller git history. You can read more about it in this PR: https://github.com/rust-lang/cargo/pull/7070
2019-11-28 03:21:00 +01:00
version = "0.1.11"
Add git branch to prompt
2019-06-01 23:11:28 +02: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 03:21:00 +01:00
checksum = "b561e267b2326bb4cebfc0ef9e68355c7abe6c6f522aeac2f5bf95d56c59bdcf"
Add git branch to prompt
2019-06-01 23:11:28 +02: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 03:21:00 +01:00
"smallvec",
Add git branch to prompt
2019-06-01 23:11:28 +02:00
]
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "unicode-segmentation"
Merge master
2019-11-16 18:17:05 +01:00
version = "1.6.0"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "e83e153d1053cbb5a118eeff7fd5be06ed99153f00dbcd8ae310c5fb2b22edc0"
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "unicode-width"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
version = "0.1.7"
objectshell initial commit
2019-05-10 18:59:12 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
checksum = "caaa9d531767d1ff2150b9332433f32a24622147e5ebb1f26409d5da67afd479"
objectshell initial commit
2019-05-10 18:59:12 +02:00
bump deps
2019-07-29 09:46:24 +02: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 03:21:00 +01:00
checksum = "826e7639553986605ec5979c7dd957c7895e93eabed50ab2ffa7f6128a75097c"
bump deps
2019-07-29 09:46:24 +02:00
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 17:53:59 +02: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 03:21:00 +01:00
version = "0.26.0"
Update to heim v0.0.7.
2019-08-28 17:53:59 +02: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 03:21:00 +01:00
checksum = "4cec796ec5f7ac557631709079168286056205c51c60aac33f51764bdc7b8dc4"
Update to heim v0.0.7.
2019-08-28 17:53:59 +02:00
dependencies = [
Bump heim and necessary deps
2019-12-14 14:27:14 +01:00
"num-rational",
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 03:21:00 +01:00
"typenum",
Update to heim v0.0.7.
2019-08-28 17:53:59 +02:00
]
bump deps
2019-07-29 09:46:24 +02:00
[[package]]
name = "url"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
version = "2.1.1"
bump deps
2019-07-29 09:46:24 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
checksum = "829d4a8476c35c9bf0bbce5a3b23f4106f79728039b726d292bb93bc106787cb"
bump deps
2019-07-29 09:46:24 +02: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 03:21:00 +01:00
"idna",
"matches",
"percent-encoding",
bump deps
2019-07-29 09:46:24 +02:00
]
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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-05 00:17:18 +02: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 03:21:00 +01:00
checksum = "4ef4711d107b21b410a3a974b1204d9accc8b10dad75d8324b5d755de1617d47"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02: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 03:21:00 +01:00
"winapi 0.2.8",
"winapi-build",
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
]
A few ls improvements. New welcome message (#1195)
2020-01-11 21:49:20 +01: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 18:59:12 +02: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 03:21:00 +01:00
checksum = "8772a4ccbb4e89959023bc5b7cb8623a795caa7092d99f3aa9501b9484d4557d"
objectshell initial commit
2019-05-10 18:59:12 +02:00
Add git branch to prompt
2019-06-01 23:11:28 +02: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 03:21:00 +01:00
version = "0.2.8"
Add git branch to prompt
2019-06-01 23:11:28 +02: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 03:21:00 +01:00
checksum = "3fc439f2794e98976c88a2a2dafce96b930fe8010b0a256b3c2199a773933168"
Add git branch to prompt
2019-06-01 23:11:28 +02:00
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
checksum = "05c78687fb1a80548ae3250346c3db86a80a7cdd77bda190189f2d0a0987c81a"
Bat
2019-05-18 03:24:13 +02:00
Simple parsing
2019-05-11 06:45:57 +02: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 03:21:00 +01:00
checksum = "914b1a6776c4c929a602fafd8bc742e06365d4bcbe48c30f9cca5824f70dc9dd"
Simple parsing
2019-05-11 06:45:57 +02:00
Merge master
2019-11-16 18:17:05 +01: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 03:21:00 +01:00
checksum = "078775d0255232fb988e6fccf26ddc9d1ac274299aaedcedce21c6f72cc533ce"
Merge master
2019-11-16 18:17:05 +01:00
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "6a02e4885ed3bc0f2de90ea6dd45ebcbb66dacffe03547fadbb0eeae2770887d"
objectshell initial commit
2019-05-10 18:59:12 +02:00
Give rustyline non-ansi to begin with. Fixes Windows
2019-11-16 21:02:26 +01: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 03:21:00 +01:00
checksum = "4f42f536e22f7fcbb407639765c8fd78707a33109301f834a594758bedd6e8cf"
Give rustyline non-ansi to begin with. Fixes Windows
2019-11-16 21:02:26 +01: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 03:21:00 +01:00
"utf8parse",
Give rustyline non-ansi to begin with. Fixes Windows
2019-11-16 21:02:26 +01:00
]
Bat
2019-05-18 03:24:13 +02:00
[[package]]
name = "walkdir"
bump deps
2019-07-29 09:46:24 +02:00
version = "2.2.9"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
checksum = "9658c94fa8b940eab2250bd5a457f9c48b748420d71293b165c8cdbe2f55f71e"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
"same-file",
"winapi 0.3.8",
"winapi-util",
Bat
2019-05-18 03:24:13 +02:00
]
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 06:53:58 +02:00
[[package]]
name = "wasi"
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 03:21:00 +01:00
checksum = "b89c3ce4ce14bdc6fb6beaf9ec7928ca331de5df7e5ea278375642a2f478570d"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
Add opening urls
2019-06-08 20:09:17 +02:00
[[package]]
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
name = "wasm-bindgen"
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 07:45:27 +01:00
version = "0.2.56"
Add opening urls
2019-06-08 20:09:17 +02: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 07:45:27 +01:00
checksum = "99de4b68939a880d530aed51289a7c7baee154e3ea8ac234b542c49da7134aaf"
Add opening urls
2019-06-08 20:09:17 +02: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 03:21:00 +01:00
"cfg-if",
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01: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 03:21:00 +01:00
"wasm-bindgen-macro",
Add opening urls
2019-06-08 20:09:17 +02:00
]
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
[[package]]
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
name = "wasm-bindgen-backend"
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 07:45:27 +01:00
version = "0.2.56"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02: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 07:45:27 +01:00
checksum = "b58e66a093a7b7571cb76409763c495b8741ac4319ac20acc2b798f6766d92ee"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02: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 03:21:00 +01: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-05 00:17:18 +02:00
]
[[package]]
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
name = "wasm-bindgen-futures"
Fix #811 (#813)
2019-10-13 06:53:58 +02:00
version = "0.3.27"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02: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 03:21:00 +01:00
checksum = "83420b37346c311b9ed822af41ec2e82839bfe99867ec6c54e2da43b7538771c"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02: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 03:21:00 +01: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 07:45:27 +01: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 03:21:00 +01: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-05 00:17:18 +02:00
]
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
[[package]]
name = "wasm-bindgen-futures"
version = "0.4.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3bf1b55e0dc85085cfab2c0c520b977afcf16ac5801ee0de8dde42a4f5649b2a"
dependencies = [
"cfg-if",
"js-sys",
"wasm-bindgen",
"web-sys",
]
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
[[package]]
name = "wasm-bindgen-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 07:45:27 +01:00
version = "0.2.56"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02: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 07:45:27 +01:00
checksum = "a80f89daea7b0a67b11f6e9f911422ed039de9963dce00048a653b63d51194bf"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02: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 03:21:00 +01:00
"quote",
"wasm-bindgen-macro-support",
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
]
[[package]]
name = "wasm-bindgen-macro-support"
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 07:45:27 +01:00
version = "0.2.56"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02: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 07:45:27 +01:00
checksum = "4f9dbc3734ad6cff6b76b75b7df98c06982becd0055f651465a08f769bca5c61"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02: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 03:21:00 +01:00
"proc-macro2",
"quote",
"syn",
"wasm-bindgen-backend",
"wasm-bindgen-shared",
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
]
[[package]]
name = "wasm-bindgen-shared"
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 07:45:27 +01:00
version = "0.2.56"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02: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 07:45:27 +01:00
checksum = "d907984f8506b3554eab48b8efff723e764ddbf76d4cd4a3fe4196bc00c49a70"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
[[package]]
name = "wasm-bindgen-webidl"
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 07:45:27 +01:00
version = "0.2.56"
switch from reqwest to surf
2019-08-24 21:36:19 +02: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 07:45:27 +01:00
checksum = "f85a3825a459cf6a929d03bacb54dca37a614d43032ad1343ef2d4822972947d"
switch from reqwest to surf
2019-08-24 21:36:19 +02: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 03:21:00 +01:00
"anyhow",
"heck",
"log",
"proc-macro2",
"quote",
"syn",
"wasm-bindgen-backend",
"weedle",
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
]
[[package]]
name = "web-sys"
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 07:45:27 +01:00
version = "0.3.33"
switch from reqwest to surf
2019-08-24 21:36:19 +02: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 07:45:27 +01:00
checksum = "2fb60433d0dc12c803b9b017b3902d80c9451bab78d27bc3210bf2a7b96593f1"
switch from reqwest to surf
2019-08-24 21:36:19 +02: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 03:21:00 +01:00
"anyhow",
"js-sys",
"sourcefile",
"wasm-bindgen",
"wasm-bindgen-webidl",
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
]
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
[[package]]
name = "webpki"
version = "0.21.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d7e664e770ac0110e2384769bcc59ed19e329d81f555916a6e072714957b81b4"
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 21:36:19 +02: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 03:21:00 +01:00
checksum = "3bb43f70885151e629e2a19ce9e50bd730fd436cfd4b666894c9ce4de9141164"
switch from reqwest to surf
2019-08-24 21:36:19 +02: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 03:21:00 +01:00
"nom 4.2.3",
switch from reqwest to surf
2019-08-24 21:36:19 +02:00
]
Improve shelling out (#1273) Improvements to shelling out
2020-01-23 20:24:31 +01:00
[[package]]
name = "which"
version = "3.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5475d47078209a02e60614f7ba5e645ef3ed60f771920ac1906d7c1cc65024c8"
dependencies = [
"failure",
"libc",
]
Update plugin protocol for begin, and create new sys plugin
2019-07-27 09:45:00 +02:00
[[package]]
name = "widestring"
version = "0.4.0"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02: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 03:21:00 +01:00
checksum = "effc0e4ff8085673ea7b9b2e3c73f6bd4d118810c9009ed8f1e16bd96c331db6"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
Restructure and make commands uniform
2019-05-22 09:12:03 +02: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 03:21:00 +01:00
checksum = "167dc9d6949a9b857f3451275e911c3f44255842c1f7a76f33c55103a909087a"
Restructure and make commands uniform
2019-05-22 09:12:03 +02:00
objectshell initial commit
2019-05-10 18:59:12 +02:00
[[package]]
name = "winapi"
Update to heim v0.0.7.
2019-08-28 17:53:59 +02:00
version = "0.3.8"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "8093091eeb260906a183e6ae1abdba2ef5ef2257a21801128899c3fc699229c6"
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
"winapi-i686-pc-windows-gnu",
"winapi-x86_64-pc-windows-gnu",
objectshell initial commit
2019-05-10 18:59:12 +02:00
]
Restructure and make commands uniform
2019-05-22 09:12:03 +02: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 03:21:00 +01:00
checksum = "2d315eee3b34aca4797b2da6b13ed88266e6d612562a0c46390af8299fc699bc"
Restructure and make commands uniform
2019-05-22 09:12:03 +02:00
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "ac3b87c63620426dd9b991e5ce0329eff545bccbbb34f3be09ff6fb6ab51b7b6"
objectshell initial commit
2019-05-10 18:59:12 +02:00
Bat
2019-05-18 03:24:13 +02:00
[[package]]
name = "winapi-util"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
version = "0.1.3"
Bat
2019-05-18 03:24:13 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
checksum = "4ccfbf554c6ad11084fb7517daca16cfdcaccbdadba4fc336f032a8b12c2ad80"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
"winapi 0.3.8",
Bat
2019-05-18 03:24:13 +02:00
]
objectshell initial commit
2019-05-10 18:59:12 +02: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 03:21:00 +01:00
checksum = "712e227841d057c1ee1cd2fb22fa7e5a5461ae8e48fa2ca79ec42cfc1931183f"
objectshell initial commit
2019-05-10 18:59:12 +02:00
A real parser (lalrpop)
2019-05-26 08:54:41 +02:00
[[package]]
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
name = "winreg"
version = "0.6.2"
A real parser (lalrpop)
2019-05-26 08:54:41 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
checksum = "b2986deb581c4fe11b621998a5e53361efe6b48a151178d0cd9eeffa4dc6acc9"
A real parser (lalrpop)
2019-05-26 08:54:41 +02: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 03:21:00 +01:00
"winapi 0.3.8",
A real parser (lalrpop)
2019-05-26 08:54:41 +02: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 07:45:27 +01: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-05 00:17:18 +02:00
[[package]]
name = "x11"
version = "2.18.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 03:21:00 +01:00
checksum = "39697e3123f715483d311b5826e254b6f3cfebdd83cf7ef3358f579c3d68e235"
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02: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 03:21:00 +01:00
"libc",
"pkg-config",
Switch to rawkey reader. Add more binary reading
2019-07-05 00:17:18 +02:00
]
Add clipboard support
2019-06-07 18:30:50 +02:00
[[package]]
name = "x11-clipboard"
bump deps
2019-07-29 09:46:24 +02:00
version = "0.3.3"
Add clipboard support
2019-06-07 18:30:50 +02: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 03:21:00 +01:00
checksum = "89bd49c06c9eb5d98e6ba6536cf64ac9f7ee3a009b2f53996d405b3944f6bcea"
Add clipboard support
2019-06-07 18:30:50 +02: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 03:21:00 +01:00
"xcb",
Add clipboard support
2019-06-07 18:30:50 +02: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 03:21:00 +01:00
checksum = "5e917a3f24142e9ff8be2414e36c649d47d6cc2ba81f16201cdef96e533e02de"
Add clipboard support
2019-06-07 18:30:50 +02: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 03:21:00 +01:00
"libc",
"log",
Add clipboard support
2019-06-07 18:30:50 +02:00
]
Improve signature infrastructure The `config` command uses different kinds of named arguments, which illustrates how it works.
2019-06-01 07:50:16 +02: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 03:21:00 +01:00
checksum = "d089681aa106a86fade1b0128fb5daf07d5867a509ab036d99988dec80429a57"
Improve signature infrastructure The `config` command uses different kinds of named arguments, which illustrates how it works.
2019-06-01 07:50:16 +02:00
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
checksum = "541b12c998c5b56aa2b4e6f18f03664eef9a4fd0a246a55594efae6cc2d964b5"
Bat
2019-05-18 03:24:13 +02:00
Add xml open support
2019-06-11 08:26:03 +02:00
[[package]]
name = "xmlparser"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
version = "0.13.0"
Add xml open support
2019-06-11 08:26:03 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump some of our dependencies (#1234)
2020-01-17 21:35:48 +01:00
checksum = "b16981128b9e811347d0e72c25b2b22773da22b6dc30282846ad50427e89ba97"
Add xml open support
2019-06-11 08:26:03 +02:00
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
checksum = "65923dd1784f44da1d2c3dbbc5e822045628c590ba72123e1c73d3c230c4434d"
Bat
2019-05-18 03:24:13 +02: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 03:21:00 +01:00
"linked-hash-map 0.5.2",
Bat
2019-05-18 03:24:13 +02:00
]
Add from_xlsx for importing excel files
2019-11-17 04:18:41 +01:00
[[package]]
name = "zip"
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 03:21:00 +01:00
checksum = "3c21bb410afa2bd823a047f5bda3adb62f51074ac7e06263b2c97ecdd47e9fc6"
Add from_xlsx for importing excel files
2019-11-17 04:18:41 +01: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 03:21:00 +01:00
"crc32fast",
"flate2",
"podio",
]
Reference in New Issue Copy Permalink