I don't get the requirement for using a text editor for programming. Use a proper IDE for programming, and a text editor for the log files, it's the only sensible way. Why would you want to read or change code in something that can't then be used to compile and test that code without a lot of extraneous setup and inadequate debugging? The stuff I do end up doing on the command-line on a remote, headless station is so minor that literally pico/nano will suffice. Anything more complex and I want my IDE back even if it means re-uploading the code (and with decent source-control, that's literally a command or two on either end).
Personally, metapad has been my notepad replacement for years. I don't care about syntax highlighting in 2G log files (God, I hate to think what it would do to some of the files I open in terms of opening time), but metapad can at least open them in a reasonable time and not choke on them. But when I program, it has to be Eclipse or some equivalent. All the syntax highlighting is there. No end of clever regexp tricks to do the text manipulation required. And, I'm sorry, but Eclipse isn't going to take that much longer to start on a decent machine than a Java-based text editor would. And at least by sticking to one tool, I don't have to keep loading it up and switching/closing it anyway.
The code-folding? Obviously don't get that large programs grow to the point where you don't need to see every line all the time. It's there for a reason.
And using a text-editor you have to register and pay for? Sorry, are we back in the 90's shareware era again?
If you're editing code, use an IDE - because you're unlikely to load up a huge code project, make changes, and then NOT want to just compile it again, and there one-button in a GUI with a debugger is worth its weight in gold (I'm an advocate of both GUI and CLI - sometimes at the same time - for whatever is more appropriate to the job at hand. It's about a 70-30 split in my daily work life and about a 50-50 in anything technical, programming, or personal that I do.).
If you're only viewing/searching text, use a simple text editor that's capable of showing you things like the final bug and is so damn small and fast that you don't WANT it to do anything more complex.
And if you're writing documentation, use a word-processor.
Use the tools designed for the job that you need to do. And certainly don't pay for a one-size-fits-nobody tool that is worse than any particular tool you should be using.
Biting the hand that feeds IT
