vim-moonfly-colors
fzf
vim-moonfly-colors | fzf | |
---|---|---|
19 | 407 | |
751 | 59,920 | |
- | - | |
8.6 | 9.6 | |
16 days ago | 4 days ago | |
Lua | Go | |
MIT License | 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-moonfly-colors
-
Color schemes with semantic highlights
moonfly
-
moonfly & nightfly themes now use the Neovim Lua API for all highlights
With the recent release of Neovim 0.9, now is right time for my themes moonfly and nightfly to fully embrace Lua and the native Neovim Lua API.
-
Any themes using the new highlighting feature in nightly?
I just added support for LSP semantic tokens to my two themes: moonfly and nightfly.
-
Good or bad idea to rename my colorscheme project names; and also thanks for 500 GitHub stars
A nice minor milestone reached today; both my colorschemes, moonfly and nightfly now have exactly 500 GitHub stars each.
-
Some of the darkest colorschemes I know
Another plugin: https://github.com/bluz71/vim-moonfly-colors which has the moonfly colorscheme which is quite dark.
-
[fly16] A bat theme for fzf/fzf.vim previewing that matches my moonfly & nightfly colorschemes;
As a long time fzf/fzf.vim user the syntax highlighting old by bat for previewing has always irked me. I have used bat's base16 theme which kind-of works ok, but it was still not great when I use my moonfly and nightfly colorschemes. I decided to go down the rabbit hole and do something to somewhat remedy the situation. The fly16 bat theme is the result. Basically it is a derivation of bat's base16 but with colors shifted around to better integrate with moonfly & nightfly, especially when using fzf.vim with previewing enabled (which will use bat if it is installed). Installation instructions are at the repo link above. Note, bat fundamentally uses a Rust'ized version of Sublime's syntax highlighting engine with TextMate grammar, hence, there will not be a perfect match between bat highlighting and Vim/Neovim highlighting. However, I have done tweaks here and there that narrow the difference to within an acceptable range. Some of you may be wondering, why not just use telescope which will actually use Neovim itself for previewing. A couple reasons (for me): - I am lazy - I really like fzf - I sometimes use Vim, and fzf.vim works in both Neovim and Vim, whilst Telescope is Neovim only - I use fzf in the command line, hence I also like using it in Neovim as well Cheers
-
nvim_set_hl is faster and you may want to use a lua theme to reduce your launch time
Hello, maintainer of moonfly and nightfly color-schemes speaking.
-
mistfly-statusline, the plugin previously named moonfly-statusline, now with adaptive colorscheme support
Maintainer of moonfly and nightfly colorschemes speaking. For a while I have also maintained a simple moonfly-flavoured statusline, previously named moonfly-statusline, now renamed to mistfly-statusline.
-
Dark (#000) colorschemes?
I've found a kindred spirit of sort. Most of the dark themes don't work well for me as the blueing black backgrounds, well give me the blues. While my current theme of choice isn't #000 black it is close enough for me. bluz71/vim-moonfly-colors the background is #080808
-
Whats your favourite colorscheme in Vim/NeoVim?
I like moonfly: https://github.com/bluz71/vim-moonfly-colors
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?
kanagawa.nvim - NeoVim dark colorscheme inspired by the colors of the famous painting by Katsushika Hokusai.
peco - Simplistic interactive filtering tool
ayu - 🎨🖌 Modern Sublime Text theme
zsh-autocomplete - 🤖 Real-time type-ahead completion for Zsh. Asynchronous find-as-you-type autocompletion.
vim-nightfly-colors - A dark midnight theme for modern Neovim & classic Vim
z - z - jump around
lightspeed.nvim - deprecated in favor of leap.nvim
zsh-autosuggestions - Fish-like autosuggestions for zsh
telescope.nvim - Find, Filter, Preview, Pick. All lua, all the time.
mcfly - Fly through your shell history. Great Scott!
sonokai - High Contrast & Vivid Color Scheme based on Monokai Pro
ranger - A VIM-inspired filemanager for the console