Community

It works in a non-interactive mode. You cannot even set up a tool in interactive mode. It doesn't matter if you "just" execute python.exe with parameters (speak: parsing a script) or without - in sum it is always python.exe which outputs to STDOUT (or STDERR) or wants to wait for input on STDIN ...

I have set python as a tool in Textpad. It works in a non-interactive mode. However it fails when I run a script which requires user input, all I get is a spinning circle. Here is my present configuration Command: my path to \Python\Python313\python.exe Parameters: $File Initial folder: $FileDir N ...

I use a batch file that I've configured as a tool, which opens the matching .h file when you have a .c file open and vice versa: openrelated.bat @echo off if %~x1==.c goto :c start %~dpn1.c goto :end :c start %~dpn1.h :end The settings for the tool are: Command: openrelated.bat Parameters: $File ...

With knowledge on how the Registry works everyone could have set this up himself with every version and platform (x86 or x64) since Windows 95 (and up to whatever the current Windows version is) - unrelated if the program knows how to do this or not: Run the registry editor ( regedit.exe ). Browse ...

I'm using TextPad version 9.5.2 (64-bit) Using the search and replace strings and other parameters at the top of my text file, I can NOT reproduce my problem either. I will continue using REPLACE ALLto see if my problem recurs. I will let you know, either way. BTW: I always thought TEXTPAD was ...

FINDSTR is at least 25 years old and has its bugs and weird behavior . Most of all it won't support anything with a NUL byte, which means UTF-16, UTF-32 and others, while TextPad can handle them. The regex engine can't be trusted either. It may be faster, but much more unreliable - it's your choice ...

Is TextPad already installed? If so, uninstall it before running msiexec.exe. You can create a log of msiexec's actions as follows: msiexec /quiet /i "TextPad 8.19.msi" /lewiv "log.txt" I couldn't get it to work with the TARGETDIR parameter in PowerShell, but it did work with Command Prompt. This ...

If you run it without the "/quiet" parameter, it should explain why it's not working.

In the absence of an option to specify a macro on the command line, a way to achieve the same ends with the minimum number of keystrokes is: Create the macro and append the "FileSave" command to it. Assign a shortcut to the macro using Configure » Preferences » Keyboard » Macros. Then, each time you ...

Thank you for suggesting wildcards in search queries on the forum, and for including "parameter*" as a search term in this case. I can't believe I didn't try that. Duh! As I am sure is true for many longtime TextPad users, I use/abuse the program in ways that were probably never considered when it ...

I can't see any sense in starting TextPad with a file and auto-executing a macro on without saving the file and closing TextPad again - for me it would imply to also need to more parameters to save all open files, and close TextPad entirely. However, this results in not needing the GUI at all, so ...

In the future (or on other boards) you may want to make more than one attempt, since commandline and parameter* do find posts (the asterisk finds not only "parameter" but also words starting with that, like "parameter s " - likewise searching for command* does find posts, too, but you can use the ...

Not directly applicable, but in case you're not aware, the Edit/Copy Other/All File Names command will place the fully qualified names of all the files currently open on the clipboard. Also, if you paste and save them in a file, say wspfiles.txt, then use the Quick Open command (Ctrl+Shift+O) to ...

I am following these instructions and everything appeared to go as planned except the actual install with the .msi. If I use the command line msiexec.exe /quiet /i "TextPad 9.5.msi" TRANSFORMS=LicenseKey.mst it fails to install. If I take off the /quiet parameter and interactively install it goes ...

@MrSpock: to allow for spaces in file pathnames, put the %1 in the registry in quotes. Assuming that was not an issue, if TextPad is started with the name of a file in its parameters, it will either open it, or ask if you want to create it. Try it for yourself by running these commands in a command ...