Jens Claes

Even when the buffer is wiped-out, it's still connected to the LSP client at the moment. And with the above fix in place, the buffer is still attached again when...

Are you still planning on doing this @wokalski ?

I posted an answer yesterday but it apparently didn't get through 😢 Let's try again ```vim call plug#begin('~/.vim/bundle') Plug 'prabirshrestha/async.vim' Plug 'prabirshrestha/asyncomplete.vim' Plug 'yami-beta/asyncomplete-omni.vim' Plug 'autozimu/LanguageClient-neovim', { 'do': ':UpdateRemotePlugins' }...

What kind of flags would you like `dotenv-cli` to have? How should it behave?

@raxityo that's already possible by using the right order of -e flags, have you tried switching the order? See also https://github.com/entropitor/dotenv-cli#cascading-env-variables for an alternative to this This issue is about...

@aterreno Or you can use the `-c development` flag and have a `.env` useful for all environments and `.env.development` for local development and then in CI you don't use `-c...

I welcome a PR that actually works without reversing the order of the paths in which we load things. Otherwise, I suggest a fork is used indeed 👍

The problem is that `--override` doesn't really work well together with multiple env files. I think it makes more sense to add a flag to ignore a specific env variable...

@IdanDavidi This PR is broken as you can see here https://github.com/entropitor/dotenv-cli/pull/63#discussion_r788541172. I think something like https://github.com/entropitor/dotenv-cli/pull/63#issuecomment-1100945178 could work but nobody seems to be willing to put the work in so...

I think those are very fair points! I'm open to other alternatives as well, where e.g. in the documentation we add "common alternatives" so if you hover / if you...