nvim-send
bacon
| nvim-send | bacon | |
|---|---|---|
| 1 | 25 | |
| 3 | 1,463 | |
| - | - | |
| 5.2 | 8.0 | |
| 6 months ago | 7 days ago | |
| Rust | Rust | |
| Apache License 2.0 | GNU Affero General Public License v3.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nvim-send
-
Announcing Bacon 2
cargo-limit uses a crate called nvim-send, which could be leveraged if someone wanted to add the feature: https://github.com/alopatindev/nvim-send
bacon
- Bacon – a background Rust code checker
-
Rust fact vs. fiction: 5 Insights from Google's Rust journey in 2022
Probably one of the biggest speed ups to your inner loop writing / running code is to use something like https://github.com/Canop/bacon/. I used a combination of the docs and GPT chats to increase my learning speed a lot.
-
Project Diagnostics
Nice, I'll have a look. I miss having bacon in a tmux split, wish TS had something like that.
-
Report on platform-compliance for cargo directories
As a macOS user, it boils my brain whenever I've to type in something like ~/Library/Application Support/org.rust-lang.Cargo/config.toml. macOS users have been begging CLI tools to support XDG variables on macOS too. Setting defaults is a strong indication to the community what should be the "preferred" locations. The defaults defined in your article will invariably lead to some authors saying that if that path is good enough for cargo, then it is good enough for their tool. Even the latest draft RFC acknowledges that macOS should use XDG variables too. I've written more about this here.
-
What's your current Vim+Rust setup?
bacon + nvim-bacon
-
What are some useful tools for Rust?
bacon
-
Are there any continuous testing tools with real-time line-by-line IDE feedback for Rust?
I love cargo-watch and still it use it situationally, but as a companion to my editor workflow I mostly switched to bacon. Being able to switch with one keystroke to another cargo subcommand is delightful.
-
What is your number one rust tool?
Try bacon for checks & test!
-
Alternative to watch -cq
Was it bacon perhaps?
- Something similar to Rust's `bacon` tool but for Python?
What are some alternatives?
nvim-completion - :zap: An async autocompletion framework for Neovim
rust - Empowering everyone to build reliable and efficient software.
nxcloud - A CLI client to interact with NextCloud
cargo-geiger - Detects usage of unsafe Rust in a Rust crate and its dependencies.
cargo-limit - Productivity improvements for Rust ecosystem: warnings are skipped until errors are fixed, LSP-independent Neovim integration, etc.
helix - A post-modern modal text editor.
remoc - Remoc 🦑 — Remote multiplexed objects, channels and RPC for Rust
miri - An interpreter for Rust's mid-level intermediate representation
safecloset - Cross-platform Secure TUI Secret Locker
darkfi - Anonymous. Uncensored. Sovereign.
tonic - A native gRPC client & server implementation with async/await support.
config - configuration.nix is better than dot files