extern/nushell
1
0
Fork 1
mirror of https://github.com/nushell/nushell.git synced 2024-11-22 08:23:24 +01:00
Code Issues Packages Projects Releases Wiki Activity
bb08a221e2
nushell/Cargo.toml

141 lines
4.5 KiB
TOML
Raw Normal View History

objectshell initial commit
2019-05-10 18:59:12 +02:00
[package]
Update name
2019-05-17 01:39:58 +02:00
name = "nu"
Bump to 0.15.1 (#1984)
2020-06-14 23:54:30 +02:00
version = "0.15.1"
Update Cargo.toml
2020-03-15 18:12:28 +01:00
authors = ["The Nu Project Contributors"]
Add experimental new parser (#1554) Move to an experimental new parser
2020-04-06 09:16:14 +02:00
description = "A new type of shell"
Update Cargo.toml
2019-06-02 18:50:41 +02:00
license = "MIT"
objectshell initial commit
2019-05-10 18:59:12 +02:00
edition = "2018"
Add readme and homepage/repo
2019-07-16 21:17:46 +02:00
readme = "README.md"
First working plugin
2019-06-27 06:56:48 +02:00
default-run = "nu"
Add readme and homepage/repo
2019-07-16 21:17:46 +02:00
repository = "https://github.com/nushell/nushell"
docs: use HTTPS where possible Signed-off-by: Jonah Snider <me@jonahsnider.ninja>
2019-09-29 21:03:51 +02:00
homepage = "https://www.nushell.sh"
update links to books
2019-12-15 13:56:26 +01:00
documentation = "https://www.nushell.sh/book/"
Exclude images to reduce crate by 3MB (#1316) Maybe there are more candidates for exclusion, but 'images/' seemed obviously unnecessary. Something I started realizing lately is that cargo puts most of the root directory into the crate archive, causing huge crates to appear on crates.io. Now that I am in China, I do seem to notice every kilobyte.
2020-01-31 16:38:26 +01:00
exclude = ["images"]
objectshell initial commit
2019-05-10 18:59:12 +02:00
Fix the workspace I commented out
2019-12-18 18:58:23 +01:00
[workspace]
Move most of the root package into a subcrate. (#1445) This improves incremental build time when working on what was previously the root package. For example, previously all plugins would be rebuilt with a change to `src/commands/classified/external.rs`, but now only `nu-cli` will have to be rebuilt (and anything that depends on it).
2020-03-04 19:58:20 +01:00
members = ["crates/*/"]
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
objectshell initial commit
2019-05-10 18:59:12 +02:00
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
[dependencies]
Bump to 0.15.1 (#1984)
2020-06-14 23:54:30 +02:00
nu-cli = { version = "0.15.1", path = "./crates/nu-cli" }
nu-source = { version = "0.15.1", path = "./crates/nu-source" }
nu-plugin = { version = "0.15.1", path = "./crates/nu-plugin" }
nu-protocol = { version = "0.15.1", path = "./crates/nu-protocol" }
nu-errors = { version = "0.15.1", path = "./crates/nu-errors" }
nu-parser = { version = "0.15.1", path = "./crates/nu-parser" }
nu-value-ext = { version = "0.15.1", path = "./crates/nu-value-ext" }
nu_plugin_binaryview = { version = "0.15.1", path = "./crates/nu_plugin_binaryview", optional=true }
nu_plugin_fetch = { version = "0.15.1", path = "./crates/nu_plugin_fetch", optional=true }
nu_plugin_inc = { version = "0.15.1", path = "./crates/nu_plugin_inc", optional=true }
nu_plugin_match = { version = "0.15.1", path = "./crates/nu_plugin_match", optional=true }
nu_plugin_post = { version = "0.15.1", path = "./crates/nu_plugin_post", optional=true }
nu_plugin_ps = { version = "0.15.1", path = "./crates/nu_plugin_ps", optional=true }
nu_plugin_start = { version = "0.15.1", path = "./crates/nu_plugin_start", optional=true }
nu_plugin_sys = { version = "0.15.1", path = "./crates/nu_plugin_sys", optional=true }
nu_plugin_textview = { version = "0.15.1", path = "./crates/nu_plugin_textview", optional=true }
nu_plugin_tree = { version = "0.15.1", path = "./crates/nu_plugin_tree", optional=true }
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
Bump more deps (#1921)
2020-05-30 22:54:47 +02:00
crossterm = { version = "0.17.5", optional = true }
semver = { version = "0.10.0", optional = true }
syntect = { version = "4.2", default-features = false, features = ["default-fancy"], optional = true}
Move most of the root package into a subcrate. (#1445) This improves incremental build time when working on what was previously the root package. For example, previously all plugins would be rebuilt with a change to `src/commands/classified/external.rs`, but now only `nu-cli` will have to be rebuilt (and anything that depends on it).
2020-03-04 19:58:20 +01:00
url = { version = "2.1.1", optional = true }
Bump some of our dependencies (#1809)
2020-05-17 00:34:10 +02:00
clap = "2.33.1"
Bump some deps (#1467)
2020-03-08 20:18:44 +01:00
ctrlc = "3.1.4"
A bit more infra
2019-05-11 09:00:33 +02:00
dunce = "1.0.0"
Futures v0.3 upgrade (#1344) * Upgrade futures, async-stream, and futures_codec These were the last three dependencies on futures-preview. `nu` itself is now fully dependent on `futures@0.3`, as opposed to `futures-preview` alpha. Because the update to `futures` from `0.3.0-alpha.19` to `0.3.0` removed the `Stream` implementation of `VecDeque` ([changelog][changelog]), most commands that convert a `VecDeque` to an `OutputStream` broke and had to be fixed. The current solution is to now convert `VecDeque`s to a `Stream` via `futures::stream::iter`. However, it may be useful for `futures` to create an `IntoStream` trait, implemented on the `std::collections` (or really any `IntoIterator`). If something like this happends, it may be worthwhile to update the trait implementations on `OutputStream` and refactor these commands again. While upgrading `futures_codec`, we remove a custom implementation of `LinesCodec`, as one has been added to the library. There's also a small refactor to make the stream output more idiomatic. [changelog]: https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md#030---2019-11-5 * Upgrade sys & ps plugin dependencies They were previously dependent on `futures-preview`, and `nu_plugin_ps` was dependent on an old version of `futures-timer`. * Remove dependency on futures-timer from nu * Update Cargo.lock * Fix formatting * Revert fmt regressions CI is still on 1.40.0, but the latest rustfmt v1.41.0 has changes to the `val @ pattern` syntax, causing the linting job to fail. * Fix clippy warnings
2020-02-06 04:46:48 +01:00
futures = { version = "0.3", features = ["compat", "io-compat"] }
Multi shells (#254) Add multi-shells
2019-08-07 19:49:11 +02:00
log = "0.4.8"
Switch stdin redirect to manual. Add test (#1367)
2020-02-10 07:55:07 +01:00
pretty_env_logger = "0.4.0"
Made starship usage configurable (#2049) Co-authored-by: Darren Schroeder <fdncred@hotmail.com>
2020-06-25 07:44:55 +02:00
starship = "0.42.0"
Small restructuring
2019-05-23 06:30:43 +02:00
Move most of the root package into a subcrate. (#1445) This improves incremental build time when working on what was previously the root package. For example, previously all plugins would be rebuilt with a change to `src/commands/classified/external.rs`, but now only `nu-cli` will have to be rebuilt (and anything that depends on it).
2020-03-04 19:58:20 +01:00
[dev-dependencies]
Bump to 0.15.1 (#1984)
2020-06-14 23:54:30 +02:00
nu-test-support = { version = "0.15.1", path = "./crates/nu-test-support" }
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
Move most of the root package into a subcrate. (#1445) This improves incremental build time when working on what was previously the root package. For example, previously all plugins would be rebuilt with a change to `src/commands/classified/external.rs`, but now only `nu-cli` will have to be rebuilt (and anything that depends on it).
2020-03-04 19:58:20 +01:00
[build-dependencies]
toml = "0.5.6"
Bump some of our dependencies (#1809)
2020-05-17 00:34:10 +02:00
serde = { version = "1.0.110", features = ["derive"] }
Bump to 0.15.1 (#1984)
2020-06-14 23:54:30 +02:00
nu-build = { version = "0.15.1", path = "./crates/nu-build" }
A few ls improvements. New welcome message (#1195)
2020-01-11 21:49:20 +01:00
Make neso dependency optional
2019-08-29 01:32:58 +02:00
[features]
Str plugin promoted to built-in Nu command.
2020-05-27 00:19:18 +02:00
default = ["sys", "ps", "textview", "inc"]
Made starship usage configurable (#2049) Co-authored-by: Darren Schroeder <fdncred@hotmail.com>
2020-06-25 07:44:55 +02:00
stable = ["default", "binaryview", "match", "tree", "post", "fetch", "clipboard-cli", "trash-support", "start"]
Keep dummies in default features for convenience. (#1212)
2020-01-13 07:17:56 +01:00
Update Cargo.toml
2019-12-19 18:18:06 +01:00
# Default
Bump a lot of deps (#1560)
2020-04-07 09:51:17 +02:00
textview = ["crossterm", "syntect", "url", "nu_plugin_textview"]
Opt-out unused heim features from sys/ps plugins. (#1335)
2020-02-04 07:51:14 +01:00
sys = ["nu_plugin_sys"]
ps = ["nu_plugin_ps"]
Default plugins are independent and called from Nu. (#1322)
2020-01-31 23:45:33 +01:00
inc = ["semver", "nu_plugin_inc"]
Move some plugins back to being core shippable plugins
2019-12-10 01:05:40 +01:00
Update Cargo.toml
2019-12-19 18:18:06 +01:00
# Stable
Move binaryview to a sub-crate
2019-12-04 18:51:20 +01:00
binaryview = ["nu_plugin_binaryview"]
Update Cargo.toml
2019-12-19 18:18:06 +01:00
fetch = ["nu_plugin_fetch"]
Move the remainder of the plugins to crates
2019-12-09 19:39:51 +01:00
match = ["nu_plugin_match"]
Update Cargo.toml
2019-12-19 18:18:06 +01:00
post = ["nu_plugin_post"]
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
trace = ["nu-parser/trace"]
Update Cargo.toml
2019-12-19 18:18:06 +01:00
tree = ["nu_plugin_tree"]
Bug fix start (#1738) * fix bug on linux; added start to the stable list * add to stable and fix clippy lint
2020-05-09 19:28:57 +02:00
start = ["nu_plugin_start"]
Make neso dependency optional
2019-08-29 01:32:58 +02:00
Make feature options available downstream to nu-cli subcrate. (#1450)
2020-03-04 21:31:12 +01:00
clipboard-cli = ["nu-cli/clipboard-cli"]
Made starship usage configurable (#2049) Co-authored-by: Darren Schroeder <fdncred@hotmail.com>
2020-06-25 07:44:55 +02:00
# starship-prompt = ["nu-cli/starship-prompt"]
Make trash support optional (#1572)
2020-04-11 08:53:53 +02:00
trash-support = ["nu-cli/trash-support"]
Make feature options available downstream to nu-cli subcrate. (#1450)
2020-03-04 21:31:12 +01:00
Move some plugins back to being core shippable plugins
2019-12-10 01:05:40 +01:00
# Core plugins that ship with `cargo install nu` by default
Trying this as a workaround to the [[bin]] issue
2019-12-10 04:57:55 +01:00
# Currently, Cargo limits us to installing only one binary
# unless we use [[bin]], so we use this as a workaround
Move some plugins back to being core shippable plugins
2019-12-10 01:05:40 +01:00
[[bin]]
Trying this as a workaround to the [[bin]] issue
2019-12-10 04:57:55 +01:00
name = "nu_plugin_core_textview"
Copy core plugins back so we can publish
2019-12-18 17:35:17 +01:00
path = "src/plugins/nu_plugin_core_textview.rs"
Move some plugins back to being core shippable plugins
2019-12-10 01:05:40 +01:00
required-features = ["textview"]
Move str and inc to core plugins
2019-12-10 01:59:13 +01:00
[[bin]]
Trying this as a workaround to the [[bin]] issue
2019-12-10 04:57:55 +01:00
name = "nu_plugin_core_inc"
Copy core plugins back so we can publish
2019-12-18 17:35:17 +01:00
path = "src/plugins/nu_plugin_core_inc.rs"
Move str and inc to core plugins
2019-12-10 01:59:13 +01:00
required-features = ["inc"]
Move some plugins back to being core shippable plugins
2019-12-10 01:05:40 +01:00
[[bin]]
Trying this as a workaround to the [[bin]] issue
2019-12-10 04:57:55 +01:00
name = "nu_plugin_core_ps"
Copy core plugins back so we can publish
2019-12-18 17:35:17 +01:00
path = "src/plugins/nu_plugin_core_ps.rs"
Move some plugins back to being core shippable plugins
2019-12-10 01:05:40 +01:00
required-features = ["ps"]
[[bin]]
Trying this as a workaround to the [[bin]] issue
2019-12-10 04:57:55 +01:00
name = "nu_plugin_core_sys"
Copy core plugins back so we can publish
2019-12-18 17:35:17 +01:00
path = "src/plugins/nu_plugin_core_sys.rs"
Move some plugins back to being core shippable plugins
2019-12-10 01:05:40 +01:00
required-features = ["sys"]
Ensure stable plugins get installed. (#1373)
2020-02-10 21:32:10 +01:00
# Stable plugins
[[bin]]
name = "nu_plugin_stable_fetch"
path = "src/plugins/nu_plugin_stable_fetch.rs"
required-features = ["fetch"]
[[bin]]
name = "nu_plugin_stable_binaryview"
path = "src/plugins/nu_plugin_stable_binaryview.rs"
required-features = ["binaryview"]
[[bin]]
name = "nu_plugin_stable_match"
path = "src/plugins/nu_plugin_stable_match.rs"
required-features = ["match"]
[[bin]]
name = "nu_plugin_stable_post"
path = "src/plugins/nu_plugin_stable_post.rs"
required-features = ["post"]
[[bin]]
name = "nu_plugin_stable_tree"
path = "src/plugins/nu_plugin_stable_tree.rs"
required-features = ["tree"]
Bug fix start (#1738) * fix bug on linux; added start to the stable list * add to stable and fix clippy lint
2020-05-09 19:28:57 +02:00
[[bin]]
name = "nu_plugin_stable_start"
path = "src/plugins/nu_plugin_stable_start.rs"
required-features = ["start"]
Move some plugins back to being core shippable plugins
2019-12-10 01:05:40 +01:00
# Main nu binary
First working plugin
2019-06-27 06:56:48 +02:00
[[bin]]
name = "nu"
path = "src/main.rs"
Reference in New Issue Copy Permalink