quick-lint-js
fzf
quick-lint-js | fzf | |
---|---|---|
17 | 407 | |
1,480 | 59,739 | |
0.7% | - | |
9.8 | 9.6 | |
about 1 month ago | 7 days ago | |
C++ | Go | |
GNU General Public License v3.0 only | 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.
quick-lint-js
- Which LSP Server for Python and JavaScript?
-
it really a problem in Rust, or is this anti-Rust propaganda?
You were write. Fucking sleeper shill https://github.com/quick-lint/quick-lint-js/blob/master/tools/ci-analytics/github_api.go
- quick-lint-js: quick-lint-js finds bugs in JavaScript programs
-
Is coding in Rust as bad as in C++?
pretty insane this issue queue...not that most open source is lucrative but putting low ball price tags on it like this is...not my style let's just say https://github.com/quick-lint/quick-lint-js/issues
-
Is coding in Rust as bad as in C++? A practical comparison
My allocator is 258 SLOC.
-
Moving beyond C++ console applications applications and libraries ?
quick-lint-js (my project) is written in C++. It:
-
New Unicode library
generator: https://github.com/quick-lint/quick-lint-js/blob/7dacde3aacc95110b1ed3a56d8e6fa812aa624c0/tools/generate-lex-unicode/index.js table: https://github.com/quick-lint/quick-lint-js/blob/7dacde3aacc95110b1ed3a56d8e6fa812aa624c0/src/lex-unicode.cpp lookup: https://github.com/quick-lint/quick-lint-js/blob/7dacde3aacc95110b1ed3a56d8e6fa812aa624c0/src/lex.cpp#L89-L109
-
How to setup eslint to format on save with nvim's lsp config?
use /u/strager's quick-lint, its better.
-
quick-lint-js VS ESLint - a user suggested alternative
2 projects | 24 Dec 2021
-
deno_lint VS quick-lint-js - a user suggested alternative
2 projects | 24 Dec 2021
fzf
-
Ask HN: Any tool for managing large and variable command lines?
In addition, I think bash's `operate-and-get-next` can be very helpful. When you go back through your shell history, you can hit Ctrl+o instead of enter and it will execute the command then put the next one in your history on the command line, and keep track of where you are in your history. This way, you can rerun a bunch of commands by going to the first one and Ctrl+o till you are done. And you can edit those commands and hit Ctrl+o and still go to the next previously run command.
Note: fzf's history search feature breaks this. https://github.com/junegunn/fzf/issues/2399
-
pyfzf : Python Fuzzy Finder
fzf : https://github.com/junegunn/fzf
- Command Line Fuzzy Search
-
So You Think You Know Git – Git Tips and Tricks by Scott Chacon
Those are the most used aliases in my gitconfig.
"git fza" shows a list of modified/new files in an fzf window, and you can select each file with tab plus arrow keys. When you hit enter, those files are fed into "git add". Needs fzf: https://github.com/junegunn/fzf
"git gone" removes local branches that don't exist on the remote.
"git root" prints out the root of the repo. You can alias it to "cd $(git root)", and zip back to the repo root from a deep directory structure. This one is less useful now for me since I started using zoxide to jump around. https://github.com/ajeetdsouza/zoxide
-
Which command did you run 1731 days ago?
> my history is so noisy I had to find another way
The fzf search syntax can help, if you become familiar with it. It is also supported in atuin [2].
[1]: https://github.com/junegunn/fzf#search-syntax
[2]: https://docs.atuin.sh/configuration/config/#fuzzy-search-syn...
-
Z – Jump Around
You call it with `n` and get an interactive fuzzy search for your directories. If you do `n ` instead, it’ll start the find with `` already filled in (and if there’s only one match, jump to it directly). The `ls` is optional but I find that I like having the contents visible as soon as I change a directory.
I’m also including iCloud Drive but excluding the Library directory as that is too noisy. I have a separate `nl` function which searches just inside `~/Library` for when I need it, as well as other specialised `n` functions that search inside specific places that I need a lot.
¹ https://github.com/sharkdp/fd
² https://github.com/junegunn/fzf
-
alacritty-themes not working any more!!!
View on GitHub
-
Fish shell 3.7.0: last release branch before the full Rust rewrite
I do find the history pager stuff interesting, but ultimately not of tremendous use for me. I rebound all my history search stuff to use fzf[1] (via a fish plugin for such[2]), and so haven't been aware of the issues
[1] https://github.com/junegunn/fzf
[2] https://github.com/PatrickF1/fzf.fish
-
Ugrep – a more powerful, ultra fast, user-friendly, compatible grep
You can also use fzf with ripgrep to great effect:
[1]: https://github.com/junegunn/fzf/blob/master/ADVANCED.md#usin...
- Tell HN: My Favorite Tools
What are some alternatives?
weggli - weggli is a fast and robust semantic search tool for C and C++ codebases. It is designed to help security researchers identify interesting functionality in large codebases.
peco - Simplistic interactive filtering tool
rslint - A (WIP) Extremely fast JavaScript and TypeScript linter and Rust crate
zsh-autocomplete - 🤖 Real-time type-ahead completion for Zsh. Asynchronous find-as-you-type autocompletion.
opensg-1.8 - This is a stripped down version of OpenSG 1.8.
z - z - jump around
eslint-config-canonical - The most comprehensive ES code style guide.
zsh-autosuggestions - Fish-like autosuggestions for zsh
deno_lint - Blazing fast linter for JavaScript and TypeScript written in Rust
mcfly - Fly through your shell history. Great Scott!
ESLint - Find and fix problems in your JavaScript code.
ranger - A VIM-inspired filemanager for the console