-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unable to build "latest" version on linux #53
Comments
I remember removing a subproject some time ago. Could you please try cloning the repository and building from scratch? |
That did the trick.
The archive seems to be missing the msgpack-c sub-project.
A few questions:
- the window content is very washed-out looking compared to other
applications on my system. Is there some setting which controls that?
- the page-up, page-down, home, end, etc keys do not work. Is there some
way to enable them?
- There are a lot of logging 'info' messages output. Is there a way to
turn that off?
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
<#53 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABUOHSQ65SW6VI5UP5JI5HLWGPBCLANCNFSM6AAAAAARWFE4LA>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
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.
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: Line 267 in 4f40c48
Sure. You could control the log level with an environment variable: Line 48 in 4f40c48
|
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
<#53 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABUOHSXPWOA7LHHLUCVFU63WGTNYNANCNFSM6AAAAAARWFE4LA>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Any chance to take a peek at the screenshot? |
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 |
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. |
Hi
I downloaded the new stable tar.gz file and attempted to run the build.sh script but it failed.
The text was updated successfully, but these errors were encountered: