zed-industries/zed
1
1
Fork 0
mirror of https://github.com/zed-industries/zed.git synced 2024-09-16 17:07:14 +03:00
Code Issues Packages Projects Releases Wiki Activity
8985fd87c2
zed/crates/cli/Cargo.toml

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

40 lines
724 B
TOML
Raw Normal View History

WIP: Start on a new `cli` crate Co-Authored-By: Nathan Sobo <nathan@zed.dev>
2022-04-15 17:55:26 +03:00
[package]
name = "cli"
version = "0.1.0"
edition = "2021"
Added complete scripts for generating third party license files
2023-01-18 23:28:02 +03:00
publish = false
Licenses: change license fields in Cargo.toml to AGPL-3.0-or-later. (#5535) Release Notes: - N/A
2024-01-27 15:51:16 +03:00
license = "GPL-3.0-or-later"
Remove license-file from Cargo.toml as it is apparently redundant (#4218) Release Notes: - N/A
2024-01-23 19:40:30 +03:00
Move Clippy configuration to the workspace level (#8891) This PR moves the Clippy configuration up to the workspace level. We're using the [`lints` table](https://doc.rust-lang.org/cargo/reference/workspaces.html#the-lints-table) to configure the Clippy ruleset in the workspace's `Cargo.toml`. Each crate in the workspace now has the following in their own `Cargo.toml` to inherit the lints from the workspace: ```toml [lints] workspace = true ``` This allows for configuring rust-analyzer to show Clippy lints in the editor by using the following configuration in your Zed `settings.json`: ```json { "lsp": { "rust-analyzer": { "initialization_options": { "check": { "command": "clippy" } } } } ``` Release Notes: - N/A
2024-03-05 20:01:17 +03:00
[lints]
workspace = true
Use ipc_channel crate to communicate between cli and app We still aren't handling CLI requests in the app, but this lays the foundation for bi-directional communication. Co-Authored-By: Max Brunsfeld <maxbrunsfeld@gmail.com>
2022-04-16 02:33:56 +03:00
[lib]
path = "src/cli.rs"
doctest = false
[[bin]]
name = "cli"
path = "src/main.rs"
WIP: Start on a new `cli` crate Co-Authored-By: Nathan Sobo <nathan@zed.dev>
2022-04-15 17:55:26 +03:00
[dependencies]
:art: Specify more dependencies at the workspace level
2023-04-25 03:41:55 +03:00
anyhow.workspace = true
Make the cli crate depend on workspace clap (#9507) This fixes an outstanding TODO. --------- Co-authored-by: Piotr Osiewicz <24362066+osiewicz@users.noreply.github.com>
2024-03-18 22:00:37 +03:00
clap.workspace = true
zed: Use CLI env for lang servers, tasks, terminal (#17075) This changes the Zed CLI `zed` to pass along the environment to the Zed project that it opens (if it opens a new one). In projects, this CLI environment will now take precedence over any environment that's acquired by running a login shell in a projects folder. The result is that `zed my/folder` now always behaves as if one would run `zed --foreground` without any previous Zed version running. Closes #7894 Closes #16293 Related issues: - It fixes the issue described in here: https://github.com/zed-industries/zed/issues/4977#issuecomment-2305272027 Release Notes: - Improved the Zed CLI `zed` to pass along the environment as it was on the CLI to the opened Zed project. That environment is then used when opening new terminals, spawning tasks, or language servers. Specifically: - If Zed was started via `zed my-folder`, a terminal spawned with `workspace: new terminal` will inherit these environment variables that existed on the CLI - Specific language servers that allow looking up the language server binary in the environments `$PATH` (such as `gopls`, `zls`, `rust-analyzer` if configured, ...) will look up the language server binary in the CLI environment too and use that environment when starting the process. - Language servers that are _not_ found in the CLI environment (or configured to not be found in there), will be spawned with the CLI environment in case that's set. That means users can do something like `RA_LOG=info zed .` and it will be picked up the rust-analyzer that was spawned. Demo/explanation: https://github.com/user-attachments/assets/455905cc-8b7c-4fc4-b98a-7e027d97cdfa
2024-08-29 19:09:06 +03:00
collections.workspace = true
Make the cli crate depend on workspace clap (#9507) This fixes an outstanding TODO. --------- Co-authored-by: Piotr Osiewicz <24362066+osiewicz@users.noreply.github.com>
2024-03-18 22:00:37 +03:00
ipc-channel = "0.18"
linux cli (#11585) - [x] Build out cli on linux - [x] Add support for --dev-server-token sent by the CLI - [x] Package cli into the .tar.gz - [x] Link the cli to ~/.local/bin in install.sh Release Notes: - linux: Add cli support for managing zed
2024-05-10 06:08:49 +03:00
once_cell.workspace = true
fix cli welcome screen (#13474) Release Notes: - Fixed first launch via cli --------- Co-authored-by: Mikayla <mikayla@zed.dev>
2024-06-24 21:55:30 +03:00
parking_lot.workspace = true
Extract paths out of `util` (#13182) This PR extracts the definition of the various Zed paths out of `util` and into a new `paths` crate. `util` is for generic utils, while these paths are Zed-specific. For instance, `gpui` depends on `util`, and it shouldn't have knowledge of these paths, since they are only used by Zed. Release Notes: - N/A
2024-06-18 02:27:42 +03:00
paths.workspace = true
cli: Treat first argument as name of release channel to use for the cli (#10856) With this commit, it is now possible to invoke cli with a release channel of bundle as an argument. E.g: `zed stable some_arguments` will find CLI binary of Stable channel installed on your machine and invoke it with `some_arguments` (so the first argument is essentially omitted). Fixes #10851 Release Notes: - CLI now accepts an optional name of release channel as it's first argument. For example, `zed stable` will always use your Stable installation's CLI. Trailing args are passed along.
2024-04-22 19:01:06 +03:00
release_channel.workspace = true
:art: Specify more dependencies at the workspace level
2023-04-25 03:41:55 +03:00
serde.workspace = true
chore: Move workspace dependencies to workspace.dependencies (#7454) We should prefer referring to local deps via `.workspace = true` from now on. Release Notes: - N/A
2024-02-06 22:41:36 +03:00
util.workspace = true
Add option to pipe from stdin on cli (#16084) Closes #5044 Release Notes: - Linux: Added CLI pipe support.
2024-08-22 22:31:58 +03:00
tempfile.workspace = true
Locate the Zed app from the CLI using NSWorkspace API
2022-04-19 23:42:33 +03:00
linux cli (#11585) - [x] Build out cli on linux - [x] Add support for --dev-server-token sent by the CLI - [x] Package cli into the .tar.gz - [x] Link the cli to ~/.local/bin in install.sh Release Notes: - linux: Add cli support for managing zed
2024-05-10 06:08:49 +03:00
[target.'cfg(target_os = "linux")'.dependencies]
exec.workspace = true
fork.workspace = true
Locate the Zed app from the CLI using NSWorkspace API
2022-04-19 23:42:33 +03:00
[target.'cfg(target_os = "macos")'.dependencies]
Respect user preferences when formatting timestamp (#7994) This is a follow up to #7945. The current behaviour reads the locale and infers from that which type of time format should be used (12 hour/24 hour). However, in macOS you can override this behaviour, e.g. you can use en_US locale but still use the 24 hour clock format (Can be customized under Settings > General > Date & Format > 24-hour time). You can even customize the date format. This PR uses the macOS specific `CFDateFormatter` API, which outputs time format strings, that respect those settings. Partially fixes #7956 (as its not implemented for linux) Release Notes: - Added localization support for all macOS specific date and time configurations in chat
2024-02-24 05:18:06 +03:00
core-foundation.workspace = true
Locate the Zed app from the CLI using NSWorkspace API
2022-04-19 23:42:33 +03:00
core-services = "0.2"
:lipstick: Co-Authored-By: Nathan Sobo <nathan@zed.dev>
2022-04-20 18:36:03 +03:00
plist = "1.3"
Reference in New Issue Copy Permalink