nano-win
nano-win copied to clipboard
Syntax Highlighting
I've seen that Nano supports syntax highlighting by default, but when I try opening a simple .py
file with nano, no syntax highlighting is applied.
Add a line include "C:/my/nano/rcs/*.nanorc"
to your .nanorc
file and then extract all the syntax highlight .nanorc
files included in the .zip to the include dir mentioned above.
I think I understand what you're saying, but before I make these changes, was I supposed to install nano-win into a certain directory?
No. But wherever you do, make sure your '.nanorc' contains an absolute path to default syntax files.
I have the same problem. I can't get any color when running nano in powershell (pwsh.exe
), no matter what I do. It runs fine, but no color.
Can someone please provide:
- a functioning
.nanorc
and the location of that? - the correct
$env:path
and location? - Do we also need to set our own
$HOME
? - Do we need to manually enable
ENABLE_VIRTUAL_TERMINAL_PROCESSING
?
(New windows should handle this automatically, but may be need to enable manually for legacy code?) - Is there a specific file encoding required on either the OS terminal or of the files?
(UTF-8 for files or OS?)
You also said in your latest commit that you enabled UTF-8
, yet it was compiled with it disabled. (See #35 ).
I used the default .nanorc
file included in the package, commented out the line following the ## To include most of the existing syntax definitions, you can do:
and adjusted the path to c:/installfolder/whatever/*.nanorc
.
You can load the .nanorc file with the option --rcfile=c:/installfolder/.nanorc
.
You can pack this into a one-liner batch file like @"c:\Program Files\Nano\pkg_x86_64-w64-mingw32\bin\nano.exe" --rcfile="c:/Program Files/Nano/.nanorc" %*
to avoid typing the option everytime.
I just installed nano (both same & latest versions) on a new Window 10 Pro. I copied all the nano config, environment and all the various terminal and character coding settings I could think of to the new machine, but no matter what I do, I am not able to get colors showing in pwsh (core), even if they're working perfectly for all other programs I use via terminal. I have no idea what is causing this not to work ion this machine.
UPDATE
Indeed this seem related to the created pwsh windows shortcut.
When one is created without Admin rights, the coloring works.
When it has administrator rights enabled, it doesn't... BUT
This is not the whole story. On the other machine, it has administrator rights and still works. Something funny about the windows link/shortcut difference...
Enhancements
+ .nanorc is loaded from "%USERPROFILE%\.nanorc" with normal privilege
and from "%ALLUSERSPROFILE%\.nanorc" with elevated privilege.
+ Systemwide nanorc is loaded from "%ALLUSERSPROFILE%\nanorc".
Read the above carefully and yes, I know it can be very confusing at first glance, but I ain't judging.
C:\> 7z e nano-win_9986_v6.2-16-g58bbad01a.7z -o"C:\ProgramData\" ".nanorc"
C:\> ren C:\ProgramData\.nanorc nanorc
C:\> echo include "C:/my/nano/syntax/hilite/resources/*.nanorc" >> C:\ProgramData\nanorc
By the way, for a nicer set of syntax highlighting definitions see:
https://github.com/scopatz/nanorc