After reading all the new names and renames that Pine Script V5 brought to us, I knew that my old Notepad++ User Defined Language (UDL) would need a big update, so I decided to do a complete remake using the same Dark color scheme theme of the Pine Editor.
Then, I create a Notepad++ Theme and the Auto-Completion file with the Parameter hints for every built-in function to make everything look nicer
█ IMPORTANT
This is not an indicator!!
These are 3 XML files to copy and paste inside the Notepad++ folder.
You can use any Notepad Software to create the XML files.
The main Notepad++ folder is normally on %AppData%\Notepad++\
To avoid mistakes, always make a Backup of your files before anything.
█ INSTALLATION Just follow these steps:
1. open a New Document File;
2. Copy everything between ↓↓↓ and ↑↑↑ symbols to this new document;
3. Remove the "//" of every single line;
4. Save each document with the correct name in the right folder;
5. Restart the Notepad++
█ NOTES:
If you have some problem installing, ask me, and I will try to help you.
this is super and i am waiting for it long, thanks a lot!
RodrigoKazuma
⋅
@blackcat1402, thanks for the coins. I hope you like.
blackcat1402
⋅
@RodrigoKazuma, i love this much, it works excellent like a magic :D
djmad
⋅
Thanks
rat_king
⋅
Could anyone help me to understand exactly what this is? This can be used with Notepad++ to define the syntax of Pine which therefore basically turns Notepad++ into a Pine IDE outside of the TradingView web browser. Is that correct?
rat_king
⋅
@turkey_johnson, Ok for anyone new to this like me: @RodrigoKazuma has linked a github that houses the 3 xml files mentioned here (so that you don't have to manually copy, etc.). These just need to be copied to the Notepad++ folder on your machine.
RodrigoKazuma
⋅
@turkey_johnson, Exactly. We still (yet) have Pine Script as a Syntax Highlight Language on Notepad++ so that you can add Pine Script with the UDL system. And I recreate (with some differences) the Color Scheme of the Pine Editor in a Notepad++ Theme. And, thanks, @turkey_johnson, for explaining in a simple way the existence of these files on GitHub. 🙂👍