Scott LembckeandMarshall Bowers
e2635a685e
Closes #14787. I made a quick draft implementation of this feature request: https://github.com/zed-industries/zed/issues/14787 I know how to use use gdb well, so lacking a built-in debugger is OK. BUT... Speaking personally, setting breakpoints is 50% of what I want an IDE to do for me when debugging. Having a feature where I can click, copy, "b [paste]", is a huge step up from typing the whole thing in manually. I figure this must be useful for other external tools, or even just regular-human-communication too. Open Questions: * Does this belong in the right click menu? (I put it next to "Copy Permalink" which is similar.) * Probably not useful enough to get a default keymap? * Relative vs absolute path? * Does this need tests? Release Notes: - Added `editor: copy file location` command to copy the current file location (FILE:LINE) to the clipboard ([#14787](https://github.com/zed-industries/zed/issues/14787)). --------- Co-authored-by: Marshall Bowers <elliott.codes@gmail.com>
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS and Linux you can download Zed directly or install Zed via your local package manager.
Other platforms are not yet available:
- Windows (tracking issue)
- Web (tracking issue)
Developing Zed
- Building Zed for macOS
- Building Zed for Linux
- Building Zed for Windows
- Running Collaboration Locally
Contributing
See CONTRIBUTING.md for ways you can contribute to Zed.
Also... we're hiring! Check out our jobs page for open roles.
Licensing
License information for third party dependencies must be correctly provided for CI to pass.
We use cargo-about to automatically comply with open source licenses. If CI is failing, check the following:
- Is it showing a
no license specifiederror for a crate you've created? If so, addpublish = falseunder[package]in your crate's Cargo.toml. - Is the error
failed to satisfy license requirementsfor a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to theacceptedarray inscript/licenses/zed-licenses.toml. - Is
cargo-aboutunable to find the license for a dependency? If so, add a clarification field at the end ofscript/licenses/zed-licenses.toml, as specified in the cargo-about book.