Shihua Zeng

For anyone interested about the bug, the minimal config is: ```lua vim.cmd('packadd packer.nvim') require('packer').startup({ function(use) use({ 'wbthomason/packer.nvim' }) use({ 'voldikss/vim-floaterm', cmd = { 'FloatermNew', 'FloatermToggle' }, }) use({ 'hrsh7th/nvim-cmp', config...

Reopen this issue because I find starting from commit `ed2d5c9c17f4df2eeaca4878145fecc9669e0138` the problem arises. Before this commit packer uses `file` as the `complete` option for `nvim_create_user_command()`; after this commit packer uses...

A short video demonstrating the bug: https://user-images.githubusercontent.com/76579810/207523205-bd5db373-0769-4d8a-a33c-4f5016822f58.mp4

Also see the issue under `nvim-cmp`: [https://github.com/hrsh7th/nvim-cmp/issues/1348](https://github.com/hrsh7th/nvim-cmp/issues/1348)

A better idea is not to sync `packer_compiled.lua`. It is an intermediate cache file to boost the startup time, as long as you keep your regular config file I see...

Hi, if your are interested, I've made [a fok of packer](https://github.com/Bekaboo/packer.nvim) that has this feature implemented with several other improvements.

Experiencing the same issue

> This PR does not address the problem of overrides being unaware of light/dark modes. They are applied universally still. This functionality will have to be implemented later, but this...

Yeah I mean I can make another PR for the problem of overrides being unaware of light/dark modes. Haven't gotten time to really look into this though, it will be...

Any updates on this? It's pretty annoying when users switches between dark and light mode and it happens to be everyday.