No description
Lionel DARNIS
542d943211
Key the local libcosmic fork as `cosmic` with `package = "libcosmic-yoda"` rather than keying it by package name, so every repo in the local stack declares it the same way. The extern name stays `cosmic` either way, so no source change is needed; the feature strings move with the key. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .github | ||
| .idea | ||
| debian | ||
| i18n | ||
| res | ||
| src | ||
| .gitattributes | ||
| .gitignore | ||
| build.rs | ||
| Cargo.lock | ||
| Cargo.toml | ||
| flake.lock | ||
| flake.nix | ||
| i18n.toml | ||
| justfile | ||
| LICENSE | ||
| README.md | ||
| redoxer.sh | ||
| TESTING.md | ||
COSMIC Text Editor
Text editor for the COSMIC desktop
Currently an incomplete pre-alpha, this project is a work in progress - issues are expected.
Testing
You can test by installing a current version of Rust and then building with cargo.
git clone https://github.com/pop-os/cosmic-edit
cd cosmic-edit
cargo build
You can get more detailed errors by using the RUST_LOG environment variables, that you can invoke for just that one command like this: RUST_LOG=debug cargo run. This will give you more detail about the application state. You can go even further with RUST_LOG=trace cargo run, that shows all logging details about the application.
Clippy Lints
PRs are welcome, as it builds a better product for everyone. It is recommended that you check your code with Clippy Lints turned on. You can find more about Configuring Clippy here.