Sergio A. Vargas

Yes. First write in your .vimrc/init.vim ```vim Plug 'savq/melange' ``` Reload your config (`:source $MYVIMRC`) and run `:PlugInstall`. After that, you add to your config ```vim set termguicolors colorscheme melange...

Reading the nvim-tree.lua docs: > Syntax highlighting uses g:terminal_color_ from colorschemes, fallbacks to ugly colors otherwise. So the problem is likely that melange doesn't set these variables explicitly.

Hmmm, I'm not sure about what might be causing this. Some info that might be good to know: - What nvim version are you running? - Did you download it...

A very basic way of doing this was added in #106 . Still, let's keep the issue open to see how this could be improved in the future.

The deeper problem here is that placing the code that manifests a system, i.e. paq downloading plugins, along side other code that expects the system to exist already is complicated....

Active? no. Abandoned? also no. It's been a bit over a year since I made the first commit to the repo, and in that time I've actually learned _a lot_...

I decided to make a [1.0 release](https://github.com/savq/paq-nvim/releases/tag/v1.0.0) so that people know the current features are mostly stable and won't change in the near future. I also added a bug report...

@danshumaker I'll probably won't add your suggested feature, but you might be able to achieve something similar using autocommands. like: ```vim autocmd User PaqDoneSync PaqLogOpen ```

Yeah, This isn't really top priority. It's just to keep things tidy. A map can have the same implementation as a command, and it works with `.` too. I also...

Hey @austinjones, Your example does clear some things up, but @jeizsm comment makes me think this is a common source of confusion. With that in mind, my first intution/draft proposal...