dotfiles
coc-rust-analyzer
dotfiles | coc-rust-analyzer | |
---|---|---|
18 | 16 | |
141 | 1,112 | |
- | - | |
8.8 | 8.5 | |
about 1 month ago | 4 days ago | |
Vim Script | TypeScript | |
- | MIT License |
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.
dotfiles
-
Ugrep – a more powerful, ultra fast, user-friendly, compatible grep
So ired is a toy. One wonders how many search results you've missed over the years because of ired's feature "it's so minimal that it's wrong!" I mean sometimes tools have bugs. ripgrep has had bugs too. But this one has been in ired since 2009.
What is it that you said? YIKES. Yeah. Seems appropriate.
[1]: https://github.com/BurntSushi/dotfiles/blob/eace294fd80bfde1...
[2]: https://github.com/radare/ired/blob/a1fa7904e6ad239dde950de5...
-
Framework 13 with AMD Ryzen 7040 Series Makes for a Great Linux Laptop
I've been using X11 on my Framework laptop for years. No desktop environment at all. Just my regulard old school window manager[1]. No KDE or GNOME. But also no XFCE.
The only thing I had to do to get scaling working for me was set two environment variables[2].
I was indeed worried about this when I bought the laptop. Prior to this, I avoided anything with resolutions higher than 1920x1200. But it turned out that everything mostly worked with a couple tweaks.
I think the only real issue I've run into is `git gui`. As I understand it, the GUI toolkit it uses doesn't support scaling? Not sure. I ended up working around it by just increasing font sizes. I suppose this exposes the weakness that is probably impacting you: the scaling on my laptop is being done by the GUI toolkits, not the display server or compositor. (I don't always run a compositor, but when I do, I use `picom`. Mostly just to avoid tearing.)
[1]: https://github.com/BurntSushi/wingo
[2]: https://github.com/BurntSushi/dotfiles/blob/ea3a88e6160f4244...
-
Docfd 0.8.5 TUI fuzzy document finder
Here's a really simple example: https://github.com/BurntSushi/dotfiles/blob/214aab9fdc45e7a507d41b564a1136eea9b298c9/bin/pre-rg
-
What setup do you use to program in rust?
The full details of my setup (and more) are here: https://github.com/BurntSushi/dotfiles
-
Fastest XML node parsing library in Rust
If it turns out to be the library (I'd wager not, 4 minutes feels excessive), then you could give roxmltree a try. This program deals with about 7GB of XML (my SMS history for the past few years) in about 15 seconds.
-
Do people write whole APIs in Rust?
Did you try roxmltree? It worked really well for me and was quite fast: https://github.com/BurntSushi/dotfiles/blob/90f2acf2f45548ca0ff2da827f3108be0a965b74/bin/rust/searchsms/main.rs
-
would you use rust for scripting?
find-invalid-utf8: walks a directory tree and prints invalid UTF-8 in files using nice hex escapes with coloring. This is useful for honing on in where invalid UTF-8 occur. You have a good bet of finding some by checking out any moderately sized repository of code. The Linux kernel used to have some. The Mozilla repo does. The CPython repo does too. This is why it's important for CLI tools to deal with invalid UTF-8 gracefully in some way.
-
What are some less popular but well-made crates you'd like others to know about?
Yeah it's great! I used it to implement a little utility to convert a subset of SMS/MMS messages from an XML backup to a more readable plain text version: https://github.com/BurntSushi/dotfiles/blob/0b075d79a6ff8812a1f48a37b9858938b3eadc58/bin/rust/searchsms/main.rs
-
Ask HN: Can I see your scripts?
My dotfiles: https://github.com/BurntSushi/dotfiles
Here are some selected scripts folks might find interesting.
Here's my backup script that I use to encrypt my data at rest before shipping it off to s3. Runs every night and is idempotent. I use s3 lifecycle rules to keep data around for 6 months after it's deleted. That way, if my script goofs, I can recover: https://github.com/BurntSushi/dotfiles/blob/2f58eedf3b7f7dae...
I have so many machines running Archlinux that I wrote my own little helper for installing Arch that configures the machine in the way I expect: https://github.com/BurntSushi/dotfiles/blob/2f58eedf3b7f7dae...
A tiny little script to recover the git commit message you spent 10 minutes writing, but "lost" because something caused the actual commit to fail (like a gpg error): https://github.com/BurntSushi/dotfiles/blob/2f58eedf3b7f7dae...
A script that produces a GitHub permalink from just a file path and some optional file numbers. Pass --clip to put it on your clipboard: https://github.com/BurntSushi/dotfiles/blob/2f58eedf3b7f7dae... --- I use it with this vimscript function to quickly generate permalinks from my editor: https://github.com/BurntSushi/dotfiles/blob/2f58eedf3b7f7dae...
A wrapper around 'gh' (previously: 'hub') that lets you run 'hub-rollup pr-number' and it will automatically rebase that PR into your current branch. This is useful for creating one big "rollup" branch of a bunch of PRs. It is idempotent. https://github.com/BurntSushi/dotfiles/blob/2f58eedf3b7f7dae...
Scale a video without having to memorize ffmpeg's crazy CLI syntax: https://github.com/BurntSushi/dotfiles/blob/2f58eedf3b7f7dae...
Under X11, copy something to your clipboard using the best tool available: https://github.com/BurntSushi/dotfiles/blob/2f58eedf3b7f7dae...
-
Is it common for you guys to have an update break your system?
Otherwise, the most common "breakage" I get is when I forget to update in a while. Used to be a mostly non-issue until package signing became a thing. Now I get lots of signing errors when I update. When that happens, I run this script and it usually fixes things: https://github.com/BurntSushi/dotfiles/blob/2f58eedf3b7f7dae7f0a7cea1a641459e25e5d07/bin/pacman-fix-keys
coc-rust-analyzer
-
How to configure vim like an IDE
Rust
-
rust-analyzer while learning
You can absolutely get nvim and rust analyzer working together. I personally use this: https://github.com/fannheyward/coc-rust-analyzer
-
New to Rust. How to setup Nvim as IDE?
nvim plugin](https://github.com/neoclide/coc.nvim) together with the rust analyzer plugin. It's given me the most complete, useful experience developing in rust on nvim. I absolutely love it and can't recommend it enough.
-
Is rust-analyzer necessary?
I use https://github.com/neoclide/coc.nvim with https://github.com/fannheyward/coc-rust-analyzer and this default config: https://github.com/ithinuel/dotfiles/blob/main/.config/nvim/coc-settings.json#L2-L9
-
Coc type annotations in rust
If you're using coc-rust-analyzer, did you try setting rust-analyzer.inlayHints.enable to false?
-
How to include coc extensions with my dotfiles?
Using this plugin I have installed several extensions like coc-clangd and coc-rust-analyzer .
-
Which IDE or Editor you use?
It works pretty well with coc-rust-analyzer actually. but I eventually found the file tree in VSCode very useful, also the debugging interface, so I use VSCode with the Vim plugin. It is the best of both worlds how I feel.
-
vim racer go to function definition
I would install coc.nvim and https://github.com/fannheyward/coc-rust-analyzer
-
Vim - Using clippy as a linter
Yeah sorry I thought you were saying to use the rust-analyzer vim plugin.
-
friendly reminder for our vscode folks, use rust-analyzer
VIM users too! It is available as a language server extension for CoC, called coc-rust-analyzer and it works just as well as the VSCode version.
What are some alternatives?
nvim-tree.lua - A file explorer tree for neovim written in lua
rust.vim - Vim configuration for Rust.
git-crypt - Transparent file encryption in git
rust-analyzer - A Rust compiler front-end for IDEs
rust-script - Run Rust files and expressions as scripts without any setup or compilation step.
rust-analyzer - A Rust compiler front-end for IDEs [Moved to: https://github.com/rust-lang/rust-analyzer]
vscodium - binary releases of VS Code without MS branding/telemetry/licensing
neovim-rust - Sample neovim and vim configurations for Rust development
tree-sitter - An incremental parsing system for programming tools
nocode - The best way to write secure and reliable applications. Write nothing; deploy nowhere.
coc-texlab - TexLab extension for coc.nvim