Package Details: lunarvim-git 1.2.0.r57.gb661efb3-2

Git Clone URL: https://aur.archlinux.org/lunarvim-git.git (read-only, click to copy)
Package Base: lunarvim-git
Description: An IDE layer for Neovim with sane defaults. Completely free and community driven.
Upstream URL: https://github.com/LunarVim/LunarVim
Keywords: lunarvim neovim
Licenses: GPL3
Submitter: edward-p
Maintainer: cassius23
Last Packager: cassius23
Votes: 2
Popularity: 0.070549
First Submitted: 2021-08-08 18:14 (UTC)
Last Updated: 2022-12-17 19:14 (UTC)

Latest Comments

1 2 3 Next › Last »

REmorin commented on 2023-01-14 12:14 (UTC)

Hi, could you update the package regularly, as in chaotic-aur, please?

I'm using the one from chaotic-aur, but I can only leave comments about e.g. errors only here. And the version here being not up-to-date prevents me from commenting here.

pi314ever commented on 2022-12-21 03:27 (UTC)

I'm getting the same errors as @Tangdi along with the invalid Tree-sitterquerylanguage mentioned by @Xar. The current update doesn't seem to help this issue.

I have neovim previously installed with some configs which I suspect might be the issue, will there be a fix anytime soon?

joshmackwilliams commented on 2022-12-20 15:07 (UTC)

The issue I mentioned below is resolved for me in the latest version (1.2.0.r57.gb661efb3-2). Thanks @cassius23!

Xar commented on 2022-12-18 21:51 (UTC)

You might try this, but definitely test it out:

build() {
  cd "${srcdir}/nvim-treesitter"
  runtime="${srcdir}/nvim-treesitter"

  for lang in ${langs[@]}; do
    if [[ ! -e ${runtime}/parser/${lang}.so ]]; then
      XDG_CONFIG_HOME='/dev/null' \
        XDG_DATA_HOME='/dev/null' \
        XDG_STATE_HOME='/dev/null' \
        nvim --clean --headless \
        --cmd "set runtimepath+=${runtime}" +"TSUpdateSync ${lang}" +qall
    fi
  done
}

There's an unrelated error with the langs entry Tree-sitterquerylanguage, which is invalid.

Xar commented on 2022-12-18 20:57 (UTC) (edited on 2022-12-18 20:58 (UTC) by Xar)

No, it's still broken. There's a conflict between this and any pre-existing installations of nvim.

In PKGBUILD, the build() script runs:

nvim --cmd "set runtimepath+=${runtime}" --headless +"TSUpdateSync ${lang}" +qall

That shouldn't be part of this package. It's not safe, because: - it will use the existing configs and data dirs - nvim-treesitter won't install them in the local location anyway

https://github.com/nvim-treesitter/nvim-treesitter/blob/ee095abeac5842943a94a27c0ca75c61e7c614a2/README.md?plain=1#L428

Bear in mind that any parser installed into a parser folder on the runtime path will still be considered installed. (For example if "~/.local/share/nvim/site/parser/c.so" exists then the "c" parser will be considered installed, even though it is not in parser_install_dir)

Later in PKGBUILD in package, it does:

for parser in "${srcdir}/nvim-treesitter/parser/"*.so; do

This doesn't exist, hence the error.

Can't lunarvim do this on startup rather than in this script?

cassius23 commented on 2022-12-17 19:15 (UTC)

The package is following master branch so the version should be appropriate now.

Tangdi commented on 2022-12-17 07:26 (UTC)

Hi, I try to install this package but always get this error:

==> Starting package()...
install: cannot stat '/home/yang/.cache/paru/clone/lunarvim-git/src/nvim-treesitter/parser/*.so': No such file or directory

I checked the PKGBUILD and the treesitter repo, there are no such .so files in the respective direcotory.

Omisviden commented on 2022-11-15 01:43 (UTC)

I have the exact same problem as @joshmackwilliams using yay 11.3.0. Versions are 0.5.1.r842.g7d570462-1 -> 1.1.4.r1.g47e4e5b8-1.

joshmackwilliams commented on 2022-11-13 21:38 (UTC)

Every time I run yay, I see the following update available: aur/lunarvim-git 0.5.1.r842.g7d570462-1 -> 1.1.4.r1.g47e4e5b8-1

However, when running the update, I see warning: lunarvim-git-0.5.1.r842.g7d570462-1 is up to date -- reinstalling. Afterwards, I'm left with version aur/lunarvim-git 0.5.1.r842.g7d570462-1 still installed. Next time I try to update, I always see the same update, with the same result.

Anyone else having this problem, or know of a fix? It's not making the package unusable or anything, just annoying.