Skip to content
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

Resolution Problem On macOS #41

Closed
Corgile opened this issue Nov 14, 2022 · 5 comments · May be fixed by #46
Closed

Resolution Problem On macOS #41

Corgile opened this issue Nov 14, 2022 · 5 comments · May be fixed by #46

Comments

@Corgile
Copy link

Corgile commented Nov 14, 2022

OS or distro:

image

neoray version: 0.2.5

Describe the bug

1. right after startup

image

2. press any key

image

3. tried to set guifont smaller but still.

everything works fine but the resolution is malfunctioning on macOS 13 Ventura.

please fix this, thank you

@hismailbulut
Copy link
Owner

Thanks for reporting. Is the second image correct? In my understanding the problem only happens at startup and fixed after a key press. And I need to ask your vim configuration (only include Neoray related part)

@Corgile
Copy link
Author

Corgile commented Nov 18, 2022

Is the second image correct?

sorry for confusing, here is full screen capture of the second picture

after pressing some key or mouse clicking, the text size goes very big, and :set guifont=JetBrains\ Mono:h16 takes no effect (font exists), also the viewing area doesn't fill up the window

image

And I click the maximize button to full-screen it

image

and there are no special Neoray configs currently

image

ps: actually I don't know how to write configurations on Neoray in lua LOL

@hismailbulut
Copy link
Owner

What happens when you start Neoray with -u NORC --noplugin options? And for the font write the filename of the font. It may be JetBrainsMono without space.

@annacrombie
Copy link

I have a fix for this issue here: annacrombie@393d29b. I'm not sure if its worth making a PR though.

@hismailbulut
Copy link
Owner

I have a fix for this issue here: annacrombie@393d29b. I'm not sure if its worth making a PR though.

I will be happy to review it if you make a pr

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants