smhc

LanguageClient-neovim will start cquery for you. It doesn't need to be started manually. Does cquery exist at '~/cquery/build/cquery' for the current user? It could be an issue with the ~...

I believe this may be related to the fact Telescope is causing the re-firing of the BufReadPost event when loaded. This is particularly evident when using lazy loading of telescope...

I've reworked this in the follow up commit above and it seems to work ok, I've been using it for some time. "PackerInstall" will honour the commits from the snapshot...

@wbthomason - can you confirm whether something similar to this enhancement will be possible in the v2 refactoring? I think a common use case for snapshots is the ability to...

I believe the existing PR should work ok without change, you just need to specify the full path for the 'snapshot' config. e.g ```lua local snappath = vim.fn.stdpath('config')..'/lua/conf' local snapfile...

Perhaps providing a Dockerfile or others to easily build via docker could be an option? I use the below for oracle linux 7.6. ``` FROM (oracle linux) USER root RUN...

I am simply extracting the executables out of the image/container after it has finished building. I doubt bear would work very well in a docker container on external processes due...

Yes I think it's quite easy. I created a github docker workflow (just used the default): https://github.com/smhc/Bear/blob/master/.github/workflows/docker-image.yml And a basic Dockerfile to build: https://github.com/smhc/Bear/blob/master/Dockerfile I'm not sure where the artefacts...

The existing CI job is already building bear on ubuntu and could publish a release - it doesn't really need docker for that, does it? Docker does make it easier...

Fyi I added package creation and extraction, as well as storing the artefacts. It still needs work to build multiple platforms (different Dockerfiles) and the tie it into the release.