-
Notifications
You must be signed in to change notification settings - Fork 554
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
C/C++ syntax highlighting doesn't work #12
Comments
Somehow not including nanorc.nanorc seems to fix the issue, so the problem must be in there. |
And it seems that assembly highlighting doesn't work unless c highlighting is not included. Boy this is a big mess. |
Actually, it seems that a lot of files cause conflicts with each other at random. I'm finding lots of issues through trial and error. And somehow nano stays silent about all of it, not reporting any errors. |
Hi @OrdinaryMagician, are you including these files in you In many ways, it makes sense that you would see something when you include the In any event, I think that this is a configuration issue on your end. I hope this helps. |
I simply have all the files included on my nanorc in alphabetical order. Maybe it's something about the order, I don't know. edit: nevermind, I just seemed to have some few duplicate lines for some reason. By the way, Fish and Markdown files seem to have errors in lines 4 and 12 respectively. |
Glad that you figured this out! Is it OK to close? Also, pull requests very welcome if you have fixes for the broken lines. |
I could only figure out the Markdown one, and I don't know how to do pull requests so I'll just say there should be a ) and a " at the end of line 12. |
Great, thanks! I have fixed it. |
enh(install): Use defined constant as path
Any C or C++ source file appears with no highlighting at all.
The text was updated successfully, but these errors were encountered: