Community

Currently (TP 5.4.2)
The option "In all documents" on the Find dialog has room for improvement: if i search for a word with "in all documents" checked, then all documents in the current workspace are scanned as expected .. but each time i click "Next", every single open document is repositioned to ...

You might also like to execute your SQL scripts/queries from within textpad .. if so, then see my post here

You would just need to modify it to run isql.exe .. or is it osql.exe(?) Can't remember the SQL Server commandline interface off-hand.

I have created a tool to do precisely this .. and it's available as a TextPad Add-on :D Direct download
Official Textpad "Add-ons" page ... Search the page for "SQLite3" Although this add-on (mysl3.zip) runs your text selection as a SQLite3 script/query, it can easily be modfied to execute your ...

Another way of doing this with $CLIP (with or without AutoIt) is to use the Unxutils port of to Windows of some brilliant unix file utilities ..
http://unxutils.sourceforge.net/

Just copy pclip.exe from the above collection to your System32 folder (or someplace that's already on your $path). Here ...

Or you can use the commandline utility, sed from http://gnuwin32.sourceforge.net/packages/sed.htm as follows .. Save the following script as mysed.sed:

s/String01/String_A/g
s/String02/String_B/g
s/String03/String_C/g
s/String04/String_D/g
s/String05/String_E/g

Then run the following command at ...

Yep, I agree that a new "all open files" checkbox would be very useful on the "find in files" dialog.

Perhaps it might also be possible to provide a list of all open files by way of an environment variable, which custom tools can access? Helios? Maybe a tab-delimited list of fully qualified ...

There is a very cool solution for this, which i use countless times each day. Check it out ..
http://forums.textpad.com/viewtopic.php?p=11264#11264

It uses grep, a free commandline utility .. download link is in that post. Best of all, no need for a macro

Thanks for the reply, woho

After further investigation, it looks like the registry is not where the problem/solution lies after all. According to the helpfile, keyboard shortcuts are stored in the CUSTOM.BND file .. mine is 2665 bytes, but i can't decipher it.

But wait, how's this for bizarre ...

Is there some limit to the number of keyboard shortcuts that can be user-assigned?

I keep bumping my head on this problem with different versions of TP .. I'm still on version 5.2.0, but I've noticed it since about 4.7.3.

What happens is I can create a custom tool no problem, and it appears ...

There are some workarounds you could try though ..

The quickest one is to use this regular expression in the Find dialog to highlight words of more than 30 chars in length:
\<[^ \t=]{31,}\>
.. This will take you to each exception individually within the context of the document.

Taking this a ...

Can you explain why it worked. 8)

I'm guessing that TP sees "-" as a delimiter unless and until you specify that it can be part of a word.

So until you put the "-" into the Other characters in words parameter, the best TP can do is get to the "I" in "I-J-K", and look that up in your syntax file ...

Also - check your "files in document class" settings .. if it really does say ".txt" then try "*.txt" ... because i'm not experiencing the problem you described and mine says "*.txt"

You need to somehow gain access to the clipboard from your script, and then decide whether it's being called from TextPad or EditPad.

I use $Clip to pass multiline selections to scripts written in AutoIt 3 , where I save the clipboard to a file and send the results back in a variety of ways ...

Try removing "-" from the OperatorChars for the document class.

And try with and without a "-" in the Other characters in words parameter of the Syntax tab of the document class.

grindy wrote: Are the quotation marks actually used?
thx

Yes .. otherwise any spaces in the path-or-filename will cause problems