indeed … we try hard to track down issues till they are angry and go away 
3 Likes
sudo nano '/usr/share/nano-syntax-highlighting/nanorc.nanorc'
I changed icolor brightnormal " brightnormal" to icolor normal " normal" and saved it.
Then added include /usr/share/nano-syntax-highlighting/*.nanorc back into both filesnano ~/.nanorc and sudo nano /root/.nanorc and then checked again to see if the red error message on the bottom showed up and it does indeed go away 
1 Like
Ensure that your “include” statements are including from your local config folder as opposed to /usr/share… Further, to simplify as you set up and gain control of the situation, I suggest include only one syntax file in your main nanorc and then add others in once you understand the situation.
(Interestingly, I very much like nano, but I have recently switched to micro. It uses syntax names such that change color e.g. for comments, symbols, etc. in one file only, and then it’s updated for all languages. E.g. if you want to change color for comments, you change it one place and then comments in all languages use that color. In nano, must change in every syntax file. I also use IDEs for other work, so that route is always available, but terminal editors are great for some things and can even be used for all work, along with a good shell.)
@Greg_M, this thread is 3 years old. Necrobumbing is discouraged.
2 Likes
Hi, I am sorry. I didn’t even know. I think it showed as “unread” or as notification etc, or perhaps I got there from external search. Will be more careful. (Perhaps old threads can be locked.)
1 Like
I have been using Micro for a long time, I think it’s great. I added some notes about getting started with the advanced features on another forum a while back if you are interested:
No worries @Greg_M, no harm done. Maybe a good idea to close this old thread though.