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

Typo/ambiguity in colorscheme name (fluoromachine) #846

Closed
3 tasks done
Davidoc26 opened this issue Apr 8, 2024 · 2 comments
Closed
3 tasks done

Typo/ambiguity in colorscheme name (fluoromachine) #846

Davidoc26 opened this issue Apr 8, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@Davidoc26
Copy link

Checklist

  • I have searched through the AstroNvim docs
  • I have searched through the existing issues of AstroNvim
  • I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

0.9.5 release

Operating system/version

Linux 6.6

Terminal/GUI

gnome-terminal

Describe the bug

In fact, there is a typo in the colorscheme name in this repo, which, if you are not careful, will lead to the failure to load this colorscheme (even if the name of the colorscheme was written correctly in the config).

Correct name is fluoromachine.nvim (as it is written by the author himself: maxmx03/fluoromachine.nvim).
But now in the repository it's called fluormachine.nvim (#390).

Steps to Reproduce

Add { import = "astrocommunity.colorscheme.fluoromachine-nvim" } to your community plugins (assuming that colorscheme name is correct).

To make it work, you need to specify the wrong name(in terms of the colorscheme name):
{ import = "astrocommunity.colorscheme.fluormachine-nvim" }

Expected behavior

This should work with the correct colorscheme name:
{ import = "astrocommunity.colorscheme.fluoromachine-nvim" }

Screenshots

No response

Additional Context

No response

@Davidoc26 Davidoc26 added the bug Something isn't working label Apr 8, 2024
@Uzaaft
Copy link
Member

Uzaaft commented Apr 8, 2024

You could have just created a PR yourself.

@Uzaaft
Copy link
Member

Uzaaft commented Apr 8, 2024

Fixed in #848

@Uzaaft Uzaaft closed this as completed Apr 8, 2024
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

No branches or pull requests

2 participants