Community

Well, okay, but none of the other programs that print have any problems. Why would that be?

It's a work computer; I don't have that ability. Also, it's shared on the network.

This has been a problem since 4.7.3. Nine times out of ten, when I try to print from TextPad, it aborts. The environment is Windows 2000 SP4. I get the message, "DBGHELP.DLL too old to create dump file" before TextPad terminates. I think the "tenth" time it doesn't abort is when there is only one ...

That's a good idea, thanks.

It doesn't even get to the "ask for a printer" window, it just aborts.

I'm running TextPad 4.7.3 on Windows 2000 SP4 (sorry, can't help it, it's work) and 9 times out of ten, when I try to print, TextPad aborts and I get that "had to shutdown the program" message. It's gotten so that I use Notepad to print (blech). Given that the last release was in 2004 I have a ...

I understand guys, I really do, and I appreciate the help. I tried the one-batch-file solution and it doesn't work for me. I'd have to pass in a different working directory for each file I work on which means changing all the scripts. These scripts are designed to work stand-alone and I was trying ...

Thanks for your suggestion. It's certainly a good one, and one I tried, but too many of the scripts rely on the current directory being correct. And if I put all these batch files in the correct directory, how have I changed anything? I'm more interested in how, from a technical point of view ...

I have several Perl scripts that I use as tools in TP. They work fine like this: Command: c:\perl\bin\perl.exe Parameters: c:\path\to\script.pl -switch1 -switch2 $File My problem is that "\path\to\script" changes a lot, so I'm in Configure -> Preferences changing things all the time. I'm also trying ...

csalsa wrote:Consider also voting in the poll:

Add support for Perl5/JavaScript regular expressions

I did, thanks.

Did he miss this? http://www.textpad.com/forum/viewtopic.php?p=13013 I did, but not because I didn't look. I guess I misinterpretted this: Perl syntax highlighting is now handled by its own lexical scanner, to make it more robust in detecting when # starts a comment. This requires use of the new ...

Okay, that subject line is not easy to understand. Here's the problem: #!/usr/bin/perl -w $_= qq/"text with actual quotes"/; # Strip quotes s/^"//; s/"$//; See those double quotes in lines six and seven? The syntax highlighter thinks everything from the middle of line six to the middle of line seven ...