Package Details: neovide-git 0.8.0.r0.g86aa275-1

Git Clone URL: (read-only, click to copy)
Package Base: neovide-git
Description: No Nonsense Neovim Client in Rust
Upstream URL:
Licenses: MIT
Conflicts: neovide
Provides: neovide
Submitter: peeweep
Maintainer: peeweep (ptolemy753, j4qfrost)
Last Packager: peeweep
Votes: 20
Popularity: 0.93
First Submitted: 2020-01-27 08:47 (UTC)
Last Updated: 2022-04-13 22:21 (UTC)

Latest Comments

peeweep commented on 2022-03-24 01:31 (UTC)

@Johnystar Try to build this package in devtools.

Johnystar commented on 2022-03-23 19:54 (UTC)

Doesn't compile on my system. Any clues?

   Compiling rmpv v1.0.0
error[E0599]: no variant or associated item named `Unsupported` found for enum `ErrorKind` in the current scope
  --> /home/ocean/.cache/yay/neovide-git/src/neovide-git/CARGO/registry/src/
41 |             Error::DepthLimitExceeded => ErrorKind::Unsupported,
   |                                                     ^^^^^^^^^^^ variant or associated item not found in `ErrorKind`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0599`.
error: could not compile `rmpv`

To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error: build failed
==> ERROR: A failure occurred in build().
 -> error making: neovide-git

mehrad commented on 2022-02-21 09:59 (UTC)

The URL of the project has changed from '' to ''. It would be nice to have that fixed in the PKGBUILD

lunaryorn commented on 2022-02-18 21:02 (UTC) (edited on 2022-02-18 21:03 (UTC) by lunaryorn)

I'd like to report that this PKGBUILD fails to build in a clean chroot, due to what looks like a missing makedepends on python:

Compiling tar v0.4.38
error: failed to run custom build command for `xcb v0.8.2`

Caused by:
  process didn't exit successfully: `/build/neovide-git/src/neovide-git/target/release/build/xcb-09733d86a842c41f/build-script-build` (exit status: 101)
  --- stderr
  thread 'main' panicked at 'Unable to find build dependency python3: Os { code: 2, kind: NotFound, message: "No such file or directory" }', /build/neovide-git/src/neovide-git/CARGO/registry/src/
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
error: build failed

I can make it build if I add a makedepends on python to the PKGBUILD. Would you mind to update the AUR package accordingly?

peeweep commented on 2021-06-30 06:10 (UTC)

In Debian or Fedora, the debug symbol package will be compiled for the binary package, but in Archlinux the binary is stripped and there is no debug symbol package. Please remind me if I am wrong

peeweep commented on 2021-06-30 02:19 (UTC)

@Hubro Most users should not need a software package that contains debuginfo. I personally prefer developers to modify PKGBUILD locally and add debug information. Thank you for your point!

Hubro commented on 2021-06-29 23:14 (UTC)

@peeweep @j4qfrost Would it make sense to remove "--release" from the build command? I've had to compile neovide myself several times the last week in order to get full stack traces.

It seems to me like installing a bleeding edge *-git package implies that the application may crash and the user is probably interested in proper stack traces to be able to report bugs. I'm not sure what the general convention for *-git packages is though.

zayatura commented on 2021-06-22 19:12 (UTC)

@peeweep: building neovide-git worked in a clean chroot, using the instructions from the wiki page. Thank you!

zayatura commented on 2021-06-22 06:58 (UTC)

@jeanlucthumm thanks for trying to help. I ran the command but it didn't have any effect in building neovide-git, it still fails with the same error.

I suspect that I was already on the stable branch, because it gave me this message (notice "unchanged" in there):

❯ rustup default stable
info: using existing install for 'stable-x86_64-unknown-linux-gnu'
info: default toolchain set to 'stable-x86_64-unknown-linux-gnu'

  stable-x86_64-unknown-linux-gnu unchanged - rustc 1.49.0 (e1884a8e3 2020-12-29)

@peeweep: thanks, I will look into it and see if it's something that I can use to fix the issue.

peeweep commented on 2021-06-22 05:59 (UTC) (edited on 2021-06-22 06:00 (UTC) by peeweep)

@jeanlucthumm I highly recommend that use devtools to compile the package to avoid this problem.

jeanlucthumm commented on 2021-06-21 22:24 (UTC)

@peeweep I got a similar error as @zsolt-donca. The error happens when you are using the nightly toolchain for Rust instead of the stable one. A workaround is to switch back temporarily for install:

rustup default stable

peeweep commented on 2021-06-15 01:59 (UTC)

@zsolt-donca Not reproduced, it looks like this problem has been fixed

zayatura commented on 2021-06-14 10:47 (UTC)

Build fails for me with the following:

==> Updated version: neovide-git 0.7.0.r29.g8168023-1
==> Starting build()...
error: failed to parse manifest at `/home/zdonca/work/aur/neovide-git/src/neovide-git/Cargo.toml`

Caused by:
  feature `resolver` is required

  this Cargo does not support nightly features, but if you
  switch to nightly channel you can add
  `cargo-features = ["resolver"]` to enable this feature
==> ERROR: A failure occurred in build().

nghialm commented on 2021-06-08 02:34 (UTC)

it works fine after I explicitly set guifont in init.vim

nghialm commented on 2021-06-08 02:29 (UTC)

@peeweep: without noto-fonts, I got error: thread 'main' panicked at 'index out of bounds: the len is 0 but the index is 0' , /home/nghialm/.cache/paru/clone/neovide-git/src/neovide-git/CARGO/git/checkout s/skribo-3c422fce25a33836/a35c876/src/

It's the same issue as

peeweep commented on 2021-03-27 07:54 (UTC)

@lmartinez-mirror I also think that noto-fonts should not become a dependency. @j4qfrost What do you think?

lmartinez-mirror commented on 2021-03-26 18:16 (UTC)

Is there a reason why the neovide packages depend on noto-fonts?

j4qfrost commented on 2020-06-15 20:26 (UTC) (edited on 2020-06-15 20:29 (UTC) by j4qfrost)

@peeweep I can take over package management.

ptolemy753 commented on 2020-06-08 18:50 (UTC) (edited on 2020-06-09 03:49 (UTC) by ptolemy753)

There is an issue with the static linking when building. I was able to get it to build by adding sed -i 's/, features = \[\"bundled", "static-link"\] / /g' Cargo.toml to prepare() in the PKGBUILD. I am also interested in maintaining this package.

peeweep commented on 2020-05-23 06:53 (UTC)

I am no longer using neovide, so if anyone is interesting in this package, mailme or comment to say that, i will add you to co-matainer.

obreitwi commented on 2020-04-03 16:18 (UTC)

Currently building fails with:

error[E0277]: `*mut (dyn std::ops::Fn() + 'static)` cannot be shared between threads safely
   --> src/bridge/
199 |         runtime.spawn(async move {
    |                 ^^^^^ `*mut (dyn std::ops::Fn() + 'static)` cannot be shared between threads safely

acheronfail commented on 2020-03-16 22:15 (UTC)

Hey @peeweep, I've just merged a PR on neovide adding a desktop package:

Any chance you can update the PKGBUILD to add in the desktop file? Thanks. :)