Quote:
IMHO it is better to guarantee the result "clipboard is not touched" completly or not at all. Than the user has transparency.
That is a good point but would defeat much of the usefulness of the script. I'll leave those lines in for now. Anyone can remove them if they prefer not to use the clipboard.
Quote:
Yout wrote "Andreas Borutta suggested the following script".
But the credits for the script is yours

In this case, I think your original idea is much more valuable than the script

Quote:
A profile will be created automatically: [application data]\autohotkey\
It contains
scripts\global-hotstrings.ahk
autohotkey.ini
I will keep that in mind for a future version. Thanks.
Quote:
Long hotstrings with linebreaks ({Enter}) are difficult to read and to edit.
A hotstring in the following form will be allowed, next to the old form:
::adr::
Andreas Borutta
Hochkirchstr. 8
10829 Berlin
::imho::in my humble opinion
A line continuation mechanism is planned. I will try to ensure that it works with hotstrings too.
Quote:
"Local hotstrings" by a leading "[path to the application]"
All hotstrings after a line like [path to the application]up to the next start of such a "local group", will take effect only in the mentioned specific application. More than one application is allowed and will be separated with comma.
I think someone else suggested this too. It's a good idea and hopefully someday it will get implemented. In the meantime, there are some other posts on the forum about ways to make your hotstrings context sensitive.
Quote:
Syntaxhighlighting for Ultraedit
If Tekl or someone else wouldn't mind revising
Tekl's UltraEdit script to use the master syntax files, that would be a great help.
Quote:
Example for a wiki to share scripts:
http://www.40tude.com/dialog/wiki/index ... pt_Library ... the work of structuring the big number of scripts will be spread to several people.
That's a nice example. Currently, the
script showcase is a less flexible method of doing this sort of thing. A wiki like that one might be a nice alternative someday.
Quote:
::btw::by the way, an example{Enter}with a semicolon `;and - even -{Enter}some text in {{}braces{}}
I changed the script to use "send raw" mode. It should handle special characters better now, though in exchange, `n is now used in place of {Enter}, which might be harder to read.
Quote:
Error at line 33
This line does not contain a recognized action
I added a little more validation to the script at the bottom of the
hotstrings page. If you get a chance, perhaps you could try it again.
Thanks for everything.