vim-dim
fzf
vim-dim | fzf | |
---|---|---|
13 | 407 | |
242 | 59,920 | |
- | - | |
0.0 | 9.6 | |
over 3 years ago | about 8 hours ago | |
Vim Script | Go | |
- | 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.
vim-dim
-
Whats your favourite colorscheme in Vim/NeoVim?
I use a slightly improved version of default. https://github.com/jeffkreeftmeijer/vim-dim
-
Why doesnt the comment color change if I edit the "gray" hex. Replaced with "red" atm just to see if editing line 578 is the correct line to change comment color. vim8, gruvbox theme, vim-plug. Thanks!!
You can "inherit" the terminal's colorscheme. :h cterm-colors. An example vim colorscheme that uses this: https://github.com/jeffkreeftmeijer/vim-dim
- Consistent terminal colors with 16-ANSI-color Vim themes
-
Vim Color Schemes
I achieve that same consistency with virtually zero configuration by simply setting the colors in my terminal and forgetting about it. Stopped all the fiddling with color schemes quite a while ago.
Good explanation: https://jeffkreeftmeijer.com/vim-16-color/
- What's your neovim colorscheme?
-
Trying to reach terminal constancy using ANSI only colors
I created a color theme for vim based off vim-dim
-
Vim themes that exclusively use the 16 terminal colors?
I already know about noctu and dim, but they are still too busy for my taste and use weirdly chosen colors. Are there any more?
-
What's your favourite Fonts and Themes?
Hack font and dim/grim.
-
New dark Neovim theme TokyoNight written in Lua, with support for lsp, treesitter and lots of plugins.
This might be of interest: https://jeffkreeftmeijer.com/vim-16-color/
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?
gitsigns.nvim - Git integration for buffers
peco - Simplistic interactive filtering tool
bat - A cat(1) clone with wings.
zsh-autocomplete - 🤖 Real-time type-ahead completion for Zsh. Asynchronous find-as-you-type autocompletion.
Iosevka - Versatile typeface for code, from code.
z - z - jump around
base16-nvim - Neovim plugin for building a sync base16 colorscheme. Includes support for Treesitter and LSP highlight groups.
zsh-autosuggestions - Fish-like autosuggestions for zsh
tokyo-night-vscode-theme - A clean, dark Visual Studio Code theme that celebrates the lights of Downtown Tokyo at night.
mcfly - Fly through your shell history. Great Scott!
gruvbox-material - Gruvbox with Material Palette
ranger - A VIM-inspired filemanager for the console