-
Notifications
You must be signed in to change notification settings - Fork 200
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
gem rouge warning Lexers::SHELL #240
Comments
Not really a solution, but downgrading to 1.9.0 seems to help on my end. |
I have the same issue on linux with ruby 2.1.5. It shows up with rouge 1.9.0, but not with rouge 1.8.0. I could not find any relevant changes in the upstream changelog. So do you think this is an upstream bug or is it in hologram? |
I'll have to test this on windows and see. On linux and osx I'm not getting this warnings with Rouge 1.9.1 |
Having the issue here on OS X. /Library/Ruby/Gems/2.0.0/gems/rouge-1.9.1/lib/rouge/lexers/shell.rb:20: warning: already initialized constant Rouge::Lexers::Shell::KEYWORDS
/Library/Ruby/Gems/2.0.0/gems/rouge-1.9.1/lib/rouge/lexers/shell.rb:20: warning: previous definition of KEYWORDS was here
/Library/Ruby/Gems/2.0.0/gems/rouge-1.9.1/lib/rouge/lexers/shell.rb:25: warning: already initialized constant Rouge::Lexers::Shell::BUILTINS
/Library/Ruby/Gems/2.0.0/gems/rouge-1.9.1/lib/rouge/lexers/shell.rb:25: warning: previous definition of BUILTINS was here |
@tonifisler These are the exact same warnings that I have also |
I still get the warnings with Rouge 1.9.1 on linux. I would be happy to supply additional information if you tell me what you need. |
Can confirm that downgrading to 1.9.0 fixes the issue. |
Upstream issue is tracked in rouge-ruby/rouge#296 |
I can also confirm that downgrading to rouge 1.9.0 fixes the issue |
We are on Windows 8.1
Ruby 2.1 x64.
We followed the installation procedure but whenever we run hologram we get these gem warnings, what are those can we ignore them?
The text was updated successfully, but these errors were encountered: