Package Details: gnvim 0.3.1-1

Git Clone URL: https://aur.archlinux.org/gnvim.git (read-only, click to copy)
Package Base: gnvim
Description: GUI for neovim, without any web bloat
Upstream URL: https://github.com/vhakulinen/gnvim
Licenses: MIT
Submitter: svenstaro
Maintainer: alerque
Last Packager: alerque
Votes: 8
Popularity: 0.82
First Submitted: 2019-05-17 11:31 (UTC)
Last Updated: 2024-03-28 13:53 (UTC)

Latest Comments

Terseus commented on 2024-06-02 11:22 (UTC)

Build fails with the same error, the test smoke_test_ui_attach fails.

---- smoke_test_ui_attach stdout ----
thread 'smoke_test_ui_attach' panicked at lib/nvim-rs/src/types/gen.rs:765:18:
failed to decode message (Some("chdir"), Some([Array([String(Utf8String { s: Ok("/home/terseus/.cache/yay/gnvim/src/gnvim-0.3.1/lib/nvim-rs") })])]))
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

cosmo commented on 2024-05-29 09:08 (UTC)

Build fails for me as well with the same error

rosenberg commented on 2024-05-23 10:35 (UTC)

For me it fails to compile:

warning: variable does not need to be mutable
   --> ui/src/components/./grid-buffer/row.rs:100:21
    |
100 |                 let mut cell = iter.next().expect("too long grid line event");
    |                     ----^^^^
    |                     |
    |                     help: remove this `mut`
    |
    = note: `#[warn(unused_mut)]` on by default

warning: `gnvim` (bin "gnvim" test) generated 1 warning (run `cargo fix --bin "gnvim" --tests` to apply 1 suggestion)
    Finished test [unoptimized + debuginfo] target(s) in 38.51s
     Running unittests src/lib.rs (target/debug/deps/gio_compat-91e47809b1f6e047)

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

     Running unittests src/main.rs (target/debug/deps/gnvim-172a0dd45cf5fa44)

running 2 tests
test input::tests::test_modifier_to_nvim ... ok
test child_iter::tests::test_child_iter ... ok

test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.01s

     Running unittests src/lib.rs (target/debug/deps/nvim_rs-aba2eed84f313d06)

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

     Running unittests src/bin/apigen/main.rs (target/debug/deps/apigen-fd231aa501d90a6d)

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

     Running tests/client.rs (target/debug/deps/client-3f3dab2bf9f09641)

running 1 test
test void_response_decodes_correctly ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

     Running tests/nvim.rs (target/debug/deps/nvim-6a9a37b3b28c6fab)

running 2 tests
test smoke_test ... ok
test smoke_test_ui_attach ... FAILED

failures:

---- smoke_test_ui_attach stdout ----
thread 'smoke_test_ui_attach' panicked at lib/nvim-rs/src/types/gen.rs:765:18:
failed to decode message (Some("chdir"), Some([Array([String(Utf8String { s: Ok("/home/raffaele/.cache/paru/clone/gnvim/src/gnvim-0.3.1/lib/nvim-rs") })])]))
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace


failures:
    smoke_test_ui_attach

test result: FAILED. 1 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.14s

error: test failed, to rerun pass `-p nvim-rs --test nvim`
==> ERROR: A failure occurred in check().
    Aborting...
error: failed to build 'gnvim-0.3.1-1': 
error: packages failed to build: gnvim-0.3.1-1
[ble: exit 1][ble: elapsed 92.420s (CPU 360.6%)] paru -Syu gnvim

agusdallalba commented on 2022-05-18 22:44 (UTC)

Please add options=( !lto ) to the PKGBUILD, onig does not link with LTO enabled.

halcek commented on 2022-03-03 14:11 (UTC)

@Svenstaro Can you add 'aarch64' also to the list of supported architectures for this PKGBUILD?

Thanks,

caelia commented on 2020-11-13 22:33 (UTC)

@Ataraxy :

Yes, that error indicates that you need to set a default Rust toolchain. I guess you must have rustup installed, so you need to run the command:

rustup default stable

You could also set your default to nightly (or various other less-common values), but gnvim is supposed to compile against stable Rust, so unless you're a Rust developer there is no reason to use anything else.

Also, rustup is a developer tool for managing multiple and/or customized toolchains. It's not hard to use, but one consequence of using it is that you have to manually update your Rust toolchain. If you only ever need stable Rust, you might want to install the rust package instead. That will give you the stable toolchain, which will be updated with Pacman, and you don't have to administer anything.

Ataraxy commented on 2020-10-27 10:01 (UTC) 

   Compiling xml-rs v0.8.3
error[E0658]: `cfg(doctest)` is experimental and subject to change
 --> /home/ravi/.cargo/registry/src/github.com-1ecc6299db9ec823/xml-rs-0.8.3/src/lib.rs:9:7
  |
9 | #[cfg(doctest)]
  |       ^^^^^^^
  |
  = note: for more information, see https://github.com/rust-lang/rust/issues/62210

error[E0658]: `cfg(doctest)` is experimental and subject to change
  --> /home/ravi/.cargo/registry/src/github.com-1ecc6299db9ec823/xml-rs-0.8.3/src/lib.rs:13:7
   |
13 | #[cfg(doctest)]
   |       ^^^^^^^
   |
   = note: for more information, see https://github.com/rust-lang/rust/issues/62210

   Compiling base64 v0.12.3
   Compiling pangocairo v0.9.0
   Compiling percent-encoding v1.0.1
error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0658`.
error: could not compile `xml-rs`.
warning: build failed, waiting for other jobs to finish...
error: build failed
==> ERROR: A failure occurred in build().
    Aborting...
error making: gnvim

Then:

% rustc --explain E0658
error: no override and no default toolchain set

Is there some default toolchain that is required for build?