sakhnik / nvim-ui

gtk4 GUI for neovim
MIT License
48 stars 0 forks source link

unable to build "latest" version on linux #53

Open dpriedel opened 1 year ago

dpriedel commented 1 year ago

Hi I downloaded the new stable tar.gz file and attempted to run the build.sh script but it failed.

 ./scripts/build.sh 
created virtual environment CPython3.10.8.final.0-64 in 224ms
  creator CPython3Posix(dest=/tmp/nvim-ui-stable/venv, clear=False, no_vcs_ignore=False, global=False)
  seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle, via=copy, app_data_dir=/home/dpriedel/.local/share/virtualenv)
    added seed packages: pip==22.3, setuptools==65.5.0, wheel==0.37.1
  activators BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator
Cloning into 'gir2cpp'...
remote: Enumerating objects: 532, done.
remote: Counting objects: 100% (38/38), done.
remote: Compressing objects: 100% (31/31), done.
remote: Total 532 (delta 12), reused 24 (delta 7), pack-reused 494
Receiving objects: 100% (532/532), 69.12 KiB | 1.82 MiB/s, done.
Resolving deltas: 100% (358/358), done.
Note: switching to 'ac4a2770cdb03b2c41cb0683a5ace5fc56cdfc4d'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

  git switch -c <new-branch-name>

Or undo this operation with:

  git switch -

Turn off this advice by setting config variable advice.detachedHead to false

Collecting Jinja2
  Using cached Jinja2-3.1.2-py3-none-any.whl (133 kB)
Collecting MarkupSafe>=2.0
  Using cached MarkupSafe-2.1.1-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (25 kB)
Installing collected packages: MarkupSafe, Jinja2
Successfully installed Jinja2-3.1.2 MarkupSafe-2.1.1
Unhandled {http://www.gtk.org/introspection/core/1.0}union
The Meson build system
Version: 0.63.3
Source dir: /tmp/nvim-ui-stable
Build dir: /tmp/nvim-ui-stable/BUILD
Build type: native build
Project name: nvim-ui
Project version: 0.1.0
C compiler for the host machine: cc (gcc 12.2.0 "cc (GCC) 12.2.0")
C linker for the host machine: cc ld.bfd 2.39.0
C++ compiler for the host machine: c++ (gcc 12.2.0 "c++ (GCC) 12.2.0")
C++ linker for the host machine: c++ ld.bfd 2.39.0
Host machine cpu family: x86_64
Host machine cpu: x86_64
Found pkg-config: /usr/bin/pkg-config (1.8.0)
Run-time dependency msgpack found: YES 4.0.0
Run-time dependency libuv found: YES 1.44.2
Run-time dependency spdlog found: YES 1.10.0
Run-time dependency fmt found: YES 9.1.0
Run-time dependency gtk4 found: YES 4.8.2

meson.build:22:0: ERROR: Subproject exists but has no CMakeLists.txt file
sakhnik commented 1 year ago

I remember removing a subproject some time ago. Could you please try cloning the repository and building from scratch?

dpriedel commented 1 year ago

That did the trick.

The archive seems to be missing the msgpack-c sub-project.

A few questions:

Thanks !!

On 11/3/22 10:05 AM, Anatolii Sakhnik wrote:

I remember removing a subproject some time ago. Could you please try cloning the repository and building from scratch?

— Reply to this email directly, view it on GitHub https://github.com/sakhnik/nvim-ui/issues/53#issuecomment-1302165537, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABUOHSQ65SW6VI5UP5JI5HLWGPBCLANCNFSM6AAAAAARWFE4LA. You are receiving this because you authored the thread.Message ID: @.***>

sakhnik commented 1 year ago

the window content is very washed-out looking compared to other applications on my system. Is there some setting which controls that?

Could you please illustrate the "washed-out" appearance? You could also toggle the Gtk inspector (Help -> Inspector) to tinker with the CSS styles. But I suspect that's the colour scheme used in Neovim that matters.

the page-up, page-down, home, end, etc keys do not work. Is there some way to enable them?

Absolutely! Unfortunately, I only have a Chromebook keyboard at the moment. But could you please try adding some cases to the switch statement in the source code here: https://github.com/sakhnik/nvim-ui/blob/4f40c48528afd6609cc8bdca5b8ab825e91e3864/src/GGrid.cpp#L267 ? Please don't hesitate to send a pull request.

There are a lot of logging 'info' messages output. Is there a way to turn that off?

Sure. You could control the log level with an environment variable: SPDLOG_LEVEL=off ./nvim-ui Reference: https://github.com/sakhnik/nvim-ui/blob/4f40c48528afd6609cc8bdca5b8ab825e91e3864/src/main.cpp#L48

dpriedel commented 1 year ago

Attached is a screenshot showing the desktop screen from AstroNVim.

On the left is nvim-qt

On the right is nvim-ui

Both are running from the same neovim configuration.

NOTE: in the nvim-ui window on the right the first line of the desktop menu is offset to the left.

I hope this is useful.

On 11/4/22 6:05 AM, Anatolii Sakhnik wrote:

the window content is very washed-out looking compared to other
applications on my system. Is there some setting which controls that?

Could you please illustrate the "washed-out" appearance? You could also toggle the Gtk inspector (Help -> Inspector) to tinker with the CSS styles. But I suspect that's the colour scheme used in Neovim that matters.

the page-up, page-down, home, end, etc keys do not work. Is there some
way to enable them?

Absolutely! Unfortunately, I only have a Chromebook keyboard at the moment. But could you please try adding some cases to the switch statement in the source code here: https://github.com/sakhnik/nvim-ui/blob/4f40c48528afd6609cc8bdca5b8ab825e91e3864/src/GGrid.cpp#L267 ? Please don't hesitate to send a pull request.

There are a lot of logging 'info' messages output. Is there a way to
turn that off?

Sure. You could control the log level with an environment variable: |SPDLOG_LEVEL=off ./nvim-ui| Reference: https://github.com/sakhnik/nvim-ui/blob/4f40c48528afd6609cc8bdca5b8ab825e91e3864/src/main.cpp#L48

— Reply to this email directly, view it on GitHub https://github.com/sakhnik/nvim-ui/issues/53#issuecomment-1303205292, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABUOHSXPWOA7LHHLUCVFU63WGTNYNANCNFSM6AAAAAARWFE4LA. You are receiving this because you authored the thread.Message ID: @.***>

sakhnik commented 1 year ago

Any chance to take a peek at the screenshot?

dpriedel commented 1 year ago

Screenshot from 2022-11-04 14-35-01

dpriedel commented 1 year ago

the window on the left is nvim-qt, on the right is nvim-ui

both running from the same neovim configuration

NOTE: the first menu line in the nvim-ui window is offset to the left also

sakhnik commented 1 year ago

Thanks! The offset issue was a known one, but I didn't know how to fix it until today. I'll have to investigate the colours more carefully because I haven't noticed it yet.

sakhnik commented 1 year ago

Well, the colours are fine in my system. So I'd suggest checking the global Gtk4 theme. There may be some CSS influencing nvim-ui. But I see the layout is still messed up in a different way this time. astronvim