Hi,
On Tue, Sep 06, 2022 at 10:34:46AM +0200, Emmanuel Thomé wrote:
> On the other hand, enabling youcompleteme via :packadd youcompleteme
> seems to work without error.
Thanks for looking into it! The problem seems indeed to effect
vim-addon-manager only:
Upstream added/split out two new files
The log of docker build, with all package versions, is attached.
@Frank: to remove youcompleteme from your vim-addon-manager config, you
can do "vam remove youcompleteme". It seems that using packadd instead
of vim-addon-manager works better, no idea why.
E.
On Tue, Sep 06, 2022 at 10:34:47AM
Hi,
I'm affected by this bug too.
After some hit and miss, I'm able to reproduce it in a docker container.
mkdir /tmp/bug1019188
cd /tmp/bug10109188
cat > Dockerfile <
Hi,
On Mon, Sep 05, 2022 at 08:02:20PM +0200, David Kalnischkies wrote:
> Hi,
>
> On Mon, Sep 05, 2022 at 09:47:33AM +0200, Frank Scherrer wrote:
> > ...
>
> Mhhh. Which filetype (vim tells you if you type ":set filetype?") has
> this buffer? Can you perhaps attach a file triggering these
Hi,
On Mon, Sep 05, 2022 at 09:47:33AM +0200, Frank Scherrer wrote:
> Version: 0+20220824+git7c3a88f+ds-2
>
>* What led up to the situation?
>An update from version 0+20220402+git3ededae+ds-3, if
>snapshot.debian.org is right, there was a version in between.
(Nitpick: There were two
Package: vim-youcompleteme
Version: 0+20220824+git7c3a88f+ds-2
Severity: normal
Dear Maintainer,
I think I have discovered an Issue with the latest version of
vim-youcompleteme:
* What led up to the situation?
An update from version 0+20220402+git3ededae+ds-3, if
snapshot.debian.org is
6 matches
Mail list logo
