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

[UI] Don't hard-code 'zzz' in active Lazy menu bar (next to lazy.nvim title) #161

Closed
3 tasks done
bluz71 opened this issue Dec 25, 2022 · 0 comments · Fixed by #163
Closed
3 tasks done

[UI] Don't hard-code 'zzz' in active Lazy menu bar (next to lazy.nvim title) #161

bluz71 opened this issue Dec 25, 2022 · 0 comments · Fixed by #163
Labels
bug Something isn't working

Comments

@bluz71
Copy link

bluz71 commented Dec 25, 2022

Did you check docs and existing issues?

  • I have read all the lazy docs
  • I have searched the existing issues of lazy
  • I have searched the exsiting issues of the plugin I have a problem with

Neovim version (nvim -v)

NVIM v0.8.1

Operating system/version

Linux Mint 20.0

Describe the bug

The active title bar in the README looks like this:

Lazy_Orig

Notice the sleepy zzz next to lazy.nvim.

However, this is what I see on my machine:

Lazy

Looks like some type of Japanese Kanji. I assume this is happening for me since I deliberately don't use a NERD Font (by choice).

That character is hard-coded here.

Steps To Reproduce

  1. Run Neovim on a machine without the character.

Expected Behavior

I don't mind the current behaviour as default. But it would be desirable to configure that character in the Lazy configuration ui section for folks such as myself.

I think hard-coding zzz is not desirable for folks who run minimal terminal and font setups.

Best regards.

Repro

No response

@bluz71 bluz71 added the bug Something isn't working label Dec 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant