Community

Having though a bit about the issues raised in this thread, I'd like to propose the following specific enhancements: *) Implement $Stdin and $Stdout "pseudo parameter macros" for user tools ("pseudo" because, like $Clip, they do not supply command-line arguments). Simple. I only suggest that this ...

Rather than exposing some library API or COM interface the simplest thing would be to add a STDIN/STDOUT filter that could be applied to any selected text. This would allow powerful extension yet require almost no learning on the part of the user. For example, I could use TextPad's Tool feature to ...

I think what TextPad really needs is source code folding.
This could possibly serve double-duty as an "outline" feature.
I've always loved Outline View in Microsoft Word (although, I
never liked how it actually formatted the Normal View).

I have successfully used rsync and ssh to setup one-click synchronization with a remote server. The best way to do this is to install Cygwin and include the rsync and ssh packages. You will need to create a key pair and put the public key in your remote server's authorized_keys file. ... If all this ...

UPX also compresses the textpad.exe by 44%
(From 1941504 to 853504 bytes).

(UPX is the Ultimate Packer for eXecutables by
Markus F.X.J. Oberhumer & Laszlo Molnar)

I vote for this. I'd really like to see a feature to have TextPad store options in a file in the same directory it was run. It seems like TextPad does not install much else in the way of DLLs or controls, so (except for the registry) it should be able to run from any directory -- including a USB ...

Add the Python syntax file to the default install! It's a pain in the arse to always have to download the Python and Oracle SQL syntax files after I install TextPad on a new machine. These files are pretty small. It would be nice to see at least the Python syntax file in the default install. ... I'd ...