nodo
dotfiles
Our great sponsors
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.
nodo
-
Not allowed to use 3rd party code
Oh, certainly. One of the projects I really need to get back to has a hand-rolled argument parser because it's security critical and its needs are so simple and specialized.
-
Compiling in chroot? (for security)
(The repo is here if you want to subscribe for notification of updates when I get back to it.)
-
NPM malware and what it could imply for Cargo
It's using the placeholder name nodo (like "superuser do", but "you no do") and it's currently at https://github.com/ssokolow/nodo
-
Backdooring Rust crates for fun and profit
OK. It's at https://github.com/ssokolow/nodo/issues/1 until I come up with a non-placeholder name.
dotfiles
-
Silverblue container users: what does your environment look like?
Oh you'd still use a Git repository (e.g. like I do here), stow just takes care of creating the necessary symbolic links (and skipping those that already exist).
-
NPM malware and what it could imply for Cargo
I experimented a bit with running rust-analyzer under Bubblewrap when using it through NeoVim's LSP integration (see here). Overall it's doable, but it's a tedious process of finding out what needs to write and where, what capabilities you need, etc. I don't see this seeing adoption unless it becomes a first-class feature of the tool in question.
-
Systemd service sandboxing and security hardening 101
You can also use Bubblewrap, but getting it up and running requires a lot more fiddling around. For example, this is what I use to isolate Zoom from the rest of my system: https://gitlab.com/yorickpeterse/dotfiles/-/blob/0a0492c78b6...
In my case I'm using Bubblewrap because Firejail was only used for Zoom, and this felt a bit of a waste considering Bubblewrap was already installed.
-
What do you use the tabline for?
This is implemented using some custom Lua code.
- Lists of lua-based nvim config files?
-
Is there a way to set abbreviations through lua?
There's no first-class API for this. I use this setup. This is OK, though I only have two abbreviations, and it does feel a bit overkill for just that.
-
When using the terminal emulator and opening a file within a terminal emulator, open it instead in a new buffer.
I've been using neovim-remote for quite some time, and it works perfectly fine. Here is what I use to open NeoVim as usual outside of an existing NeoVim session, and inside the existing session whenever I run nvim from NeoVim's terminal emulator.
-
neovim lsp - how do you get diagnostic mesages to show at the bottom instead of in-line?
You can use this code I wrote for that. You then hook it up like this.
-
Which one would you rather use for completion?
Adjust the icons LSP uses for various symbol types like this. If you leave this out, you need to adjust these lines to use the correct text/icons instead.
-
Neovim 0.5 Is Overpowering
The documentation is there, but it's a bit lacking/confusing here and there. It's also mostly foundational work, and you still need to cobble things together (either manually or using a plugin).
With that said, you can build things quite nicely with it. For example, I have a custom linter setup, custom loclist/quickfix list formatting and populating from LSP data, and a bunch of other things; all using the foundational work coming in NeoVim 0.5.
If anybody is curious, you can find my NeoVim configuration here: https://gitlab.com/yorickpeterse/dotfiles/-/tree/master/dotf...
p.s. In case anybody wonders "why Lua?", for me this mostly comes down to this: I hate Lua, but I hate Vimscript even more.
What are some alternatives?
cargo-crev - A cryptographically verifiable code review system for the cargo (Rust) package manager.
nvim-autopairs - autopairs for neovim written in lua
cargo-supply-chain - Gather author, contributor and publisher data on crates in your dependency graph.
NeoVim-config - My neovim config written in Lua!
grapl - Graph platform for Detection and Response
completion-nvim - A async completion framework aims to provide completion to neovim's built in LSP written in Lua
cap-std - Capability-oriented version of the Rust standard library
asyncomplete.vim - async completion in pure vim script for vim8 and neovim
watt - Runtime for executing procedural macros as WebAssembly
config_manager - My configuration files and tools
wg - Coordination repository for the Secure Code Working Group
vim-vsnip - Snippet plugin for vim/nvim that supports LSP/VSCode's snippet format.