nixpkgs-mozilla
rust-analyzer
nixpkgs-mozilla | rust-analyzer | |
---|---|---|
13 | 207 | |
495 | 9,320 | |
1.4% | - | |
4.2 | 10.0 | |
4 days ago | about 2 years ago | |
Nix | Rust | |
MIT License | GNU General Public License v3.0 or later |
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.
nixpkgs-mozilla
-
NixOS + SteamVR + OpenXR + Godot
Do I know how to do this? No, but this real-world and the wiki might be places to start. I'll eventually have to figure this out myself so if I get around to that I'll post what I learn too
-
Installing firefox-nightly with overlays and home-manager?
Is there a way to still keep it pure? From the nixpkgs-mozilla repo:
-
Annoucing fenix monthly, Rust toolchains updated 1st of every month
Fenix provides the minimal, default, and complete profile of rust toolchains, latest profile of nightly toolchains, nightly version of rust analyzer and its vscode extension. It aims to be a replacement for rustup and the rust overlay provided by nixpkgs-mozilla.
-
Blog(ish): So I switched to Arch for a month...
Firefox-nightly is maintained in the official nixpkgs-mozilla repo, so you're incorrect on that point. It's unreasonable to ask me to pick out examples for you, just to prove that numbers have actual meaning. However, feel free to peruse recently added packages and see which ones do and don't make their way to the AUR.
-
Have a few questions about NixOS
4. I would suggest Mozilla's Rust overlay or fenix or similar instead of Rustup - that would be more of the "Nix-way" to acquire the toolchain and you can still manage multiple versions. Not sure what the Ruby equivalent is, I don't do Ruby.
-
Is NixOS a perfect tool for my task and should I learn it?
and for building software, I'd suggest using flakes for both the software repo and the system configuration, because then you can just add the software flake as an input to the configuration flake and that's it, and you have the build code separated from your system. Using e.g. "ssh+git://git.example.com/secret-project" as the input should work, though I don't know which user's SSH keys it will try to use. I think mozilla-overlay is a good example, the flake outputs are a couple overlays you can add to your system's nixpkgs (here's how to add overlays in nixos), especially take a look at phlay-overlay in the mozilla repo, it's an overlay that adds one package so it's pretty simple. You can do something similar without using flakes though, fetching the sources needs to be done differently though, I know there's the builtins.fetchGit and builtins.fetchTarball functions, the former I assume would work similarly with SSH keys, no idea about the latter. The rest, making a derivation for building the software and adding it to your configuration's nixpkgs, should work the same.
-
Widevine playback not working on NixOS Nightly
I am on NixOS at the moment, Widevine (Nightly) on Arch was working well. I installed Nightly from https://github.com/mozilla/nixpkgs-mozilla.
- Cannot get a newer version of a nodePackage with an override
- Help to get the latest version of Firefox
-
Fenix: rust toolchains for all channels and rust-analyzer nightly
Fenix provides the minimal, default, and complete profile of rust toolchains, latest profile of nightly toolchains, nightly version of rust analyzer and its vscode extension. It aims to be a replacement for rustup and the rust overlay provided by nixpkgs-mozilla.
rust-analyzer
-
rust-analyzer changelog #177
#14561 map tokens from include! expansion to the included file
-
Make LSP-Rust-analyzer works
return { tools = { -- autoSetHints = false, on_initialized = function() vim.api.nvim_create_autocmd({ "BufWritePost", "BufEnter", "CursorHold", "InsertLeave" }, { pattern = { "*.rs" }, callback = function() vim.lsp.codelens.refresh() end, }) end, auto = false, inlay_hints = { -- Only show inlay hints for the current line only_current_line = false, auto = false, -- Event which triggers a refersh of the inlay hints. -- You can make this "CursorMoved" or "CursorMoved,CursorMovedI" but -- not that this may cause higher CPU usage. -- This option is only respected when only_current_line and -- autoSetHints both are true. only_current_line_autocmd = "CursorHold", -- whether to show parameter hints with the inlay hints or not -- default: true show_parameter_hints = false, -- whether to show variable name before type hints with the inlay hints or not -- default: false show_variable_name = false, -- prefix for parameter hints -- default: "<-" -- parameter_hints_prefix = "<- ", parameter_hints_prefix = " ", -- prefix for all the other hints (type, chaining) -- default: "=>" -- other_hints_prefix = "=> ", other_hints_prefix = " ", -- whether to align to the lenght of the longest line in the file max_len_align = false, -- padding from the left if max_len_align is true max_len_align_padding = 1, -- whether to align to the extreme right or not right_align = false, -- padding from the right if right_align is true right_align_padding = 7, -- The color of the hints highlight = "Comment", }, hover_actions = { auto_focus = false, border = "rounded", width = 60, -- height = 30, }, }, server = { --[[ $ mkdir -p ~/.local/bin $ curl -L https://github.com/rust-analyzer/rust-analyzer/releases/latest/download/rust-analyzer-x86_64-unknown-linux-gnu.gz | gunzip -c - > ~/.local/bin/rust-analyzer $ chmod +x ~/.local/bin/rust-analyzer --]] -- cmd = { os.getenv "HOME" .. "/.local/bin/rust-analyzer" }, cmd = { os.getenv "HOME" .. "~/.cargo/bin/rust-analyzer" }, on_attach = require("user.lsp.handlers").on_attach, capabilities = require("user.lsp.handlers").capabilities, settings = { ["rust-analyzer"] = { lens = { enable = true, }, checkOnSave = { command = "clippy", }, }, }, }, }
-
rust-analyzer changelog #164
I would like changes like https://github.com/rust-analyzer/rust-analyzer/pull/13799 to be listed in 'Breaking Changes' category, to приманка draw the users' attention.
-
Mun v0.4.0 released
For those of you who haven’t heard of Mun before, Mun is an embeddable programming language empowering creation through iteration. The idea to create Mun originated out of frustration with the Lua dynamic scripting language and a desire to have similar hot reloading functionality available in Rust. As such, it’s not a direct competitor with Rust, but instead is intended to be used with Rust (or C/C++) as a host/embedded language pairing. Actually, Mun is completely written in Rust, building on similar crates as rust-analyzer and rustc. Its key features include:
-
rust-analyzer changelog #159
#13728 upgrade chalk to make solver fuel work again (works around most trait solving hangs).
-
rust-analyzer changelog #147
#13221 (first contribution) add option to move lenses above doc comments (rust-analyzer.lens.location):
-
Does Rust need proc-macros 2.0?
Rust-analyzer has a good overview: https://github.com/rust-analyzer/rust-analyzer/blob/master/docs/dev/syntax.md
-
rust-analyzer changelog #134
#12517 (first contribution) fix completion for methods in trait generated by macro.
-
LSP Rust Analyzer keeps telling me `Error NO_RESULT_CALLBACK_FOUND`
-- all the opts to send to nvim-lspconfig -- these override the defaults set by rust-tools.nvim -- see https://github.com/neovim/nvim-lspconfig/blob/master/doc/server_configurations.md#rust_analyzer server = { -- on_attach is a callback called when the language server attachs to the buffer -- on_attach = on_attach, settings = { -- to enable rust-analyzer settings visit: -- https://github.com/rust-analyzer/rust-analyzer/blob/master/docs/user/generated_config.adoc ["rust-analyzer"] = { -- enable clippy on save checkOnSave = { command = "clippy" }, assist = { importGranularity = "module", importPrefix = "self", }, cargo = { loadOutDirsFromCheck = true }, procMacro = { enable = true }, } } },
-
rust-analyzer changelog #130
#12349 publish universal VSIX to make Code happy.
What are some alternatives?
rust-overlay - Pure and reproducible nix overlay of binary distributed rust toolchains
vscode-rust - Rust extension for Visual Studio Code
rust-analyzer - A Rust compiler front-end for IDEs
Clippy - A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
TextSnatcher - How to Copy Text from Images ? Answer is TextSnatcher !. Perform OCR operations in seconds on Linux Desktop.
intellij-rust - Rust plugin for the IntelliJ Platform
rust - Empowering everyone to build reliable and efficient software.
rustfmt - Format Rust code
dwm-flexipatch - A dwm build with preprocessor directives to decide which patches to include during build time
eglot - A client for Language Server Protocol servers
fenix - Rust toolchains and rust-analyzer nightly for Nix [maintainer=@figsoda]