I too am pleased to see some TF users. I've switched between TF and Zmud over the past few years. I finally dropped Zmud and stuck with TF about 8 months ago. I liked all of the Zmud documentation and features, but it always seemed to crash for random reasons, parts of my system would get corrupted or something odd.
The real nice thing about TF is that I can keep all of my config files on my debian server and connect to it from work, my fiancee's apartment, or just about anywhere. It's also nice to know that you can write scripts in any language your terminal supports and TF will run them.
If anyone else is interested in giving TF a shot I posted the installation files (source code and windows binary) for 5.0 beta 6, as well as the documentation and vim syntax highlighting file on my website. http://www.bwbettin.com
The real nice thing about TF is that I can keep all of my config files on my debian server and connect to it from work, my fiancee's apartment, or just about anywhere. It's also nice to know that you can write scripts in any language your terminal supports and TF will run them.
If anyone else is interested in giving TF a shot I posted the installation files (source code and windows binary) for 5.0 beta 6, as well as the documentation and vim syntax highlighting file on my website. http://www.bwbettin.com
well looks like alyssandra got you covered...
but ill throw in a couple just incase
triggering would basically be
/def -t'' =
so say you want to trigger paralysis message and color it red, it would be something like :
/def -aCred -p0 -mglob -t'a prickly stinging has something something(cant remember the message at the moment)' ackcantmove = /set paralysis=1
breaking it down a little
-
color is how TF returns the message to your shell. -ag would be to gag, -aCred (or yellow magenta blue black white etc etc) is how to color the text, -ah is for bold, -au I think(brain hurts dont make me remember) is underline. Background coloring is -aCbgred... you can combine the whole lot as well going something like -ahuCred which is bold underline red. Personally i just gag everthing and echo it back because on my version coloring text is a bit buggy.
-
priority is well the priority of the triggers like for example you have
/def -p0 -mregexp -t'^Here stands (.*)\\.$' exampleyo = lick %P1
that would trigger Here stands (anything). and you would end up licking (anything) in the said line. But for example you want a different return for a more specific line.. say
/def -p0 -mregexp -t'^Here stands HotBabe\\.$' justanexampleyo = fondle
that would trigger you to fondle everytime you see here stands HotBabe. but its going to conflict with your exampleyo trigger and so youll end up sometimes licking hotbabe and sometimes fondling yourself... so in order to make sure you fondle yourself all the time you set it up as.
/def -p0 -mregexp -t'^Here stands (.*)\\.$' exampleyo = lick %P1
/def -p1 -mregexp -t'^Here stands HotBabe\\.$' justanexampleyo = fondle
(sorry if im over simplifying im sure you get most of what im saying already but meh
)
-
matchingtype is basically how you want tf to handle the line glob and regexp are what i normally use but both also have a different way of umm... writing the line
for example you want to trigger the line You have slain (whoever). and gag it and come up with a more personalized echo
if you use glob you would go something like
/def -ag -p0 -mglob -t'You have slain *' uslainthefoo = /echo -ahCwhite JOO OWNZ %{4}
/if you use regexp it would go something like
/def -ag -p0 -mregexp -t'^You have slain (.*)/.$' uslainthefoo = /echo -ahCwhite I ownage da %P1.
generally regexp is more flexible but i find uses for glob as well just depends on what you want to trigger.
-
-t well thats to say its a trigger there are other things like hooks etc.
-
hehe yeah that line
-
macro name you can do without but i find it good to put one on all your triggers anyway because it can be hell to find/edit/delete a trigger you dont have a name for plus you can call the macro as well like going
/
so /justanexampleyo would end up umm fondling (this is such a bad example but im lazy to rewrite now)
-
function well what ever you want it to do.
...
the regular experssion and glob difference well just ask here about a line and ill answer how i would trigger each in both... well ill try anyway
...
about the binding you didnt have trouble binding your function keys and keypad yeah? well you probably looked at your character map anyway... heh
...
ralshan we need to catch up? o.O
but ill throw in a couple just incase
triggering would basically be
/def
so say you want to trigger paralysis message and color it red, it would be something like :
/def -aCred -p0 -mglob -t'a prickly stinging has something something(cant remember the message at the moment)' ackcantmove = /set paralysis=1
breaking it down a little
-
color is how TF returns the message to your shell. -ag would be to gag, -aCred (or yellow magenta blue black white etc etc) is how to color the text, -ah is for bold, -au I think(brain hurts dont make me remember) is underline. Background coloring is -aCbgred... you can combine the whole lot as well going something like -ahuCred which is bold underline red. Personally i just gag everthing and echo it back because on my version coloring text is a bit buggy.
-
priority is well the priority of the triggers like for example you have
/def -p0 -mregexp -t'^Here stands (.*)\\.$' exampleyo = lick %P1
that would trigger Here stands (anything). and you would end up licking (anything) in the said line. But for example you want a different return for a more specific line.. say
/def -p0 -mregexp -t'^Here stands HotBabe\\.$' justanexampleyo = fondle
that would trigger you to fondle everytime you see here stands HotBabe. but its going to conflict with your exampleyo trigger and so youll end up sometimes licking hotbabe and sometimes fondling yourself... so in order to make sure you fondle yourself all the time you set it up as.
/def -p0 -mregexp -t'^Here stands (.*)\\.$' exampleyo = lick %P1
/def -p1 -mregexp -t'^Here stands HotBabe\\.$' justanexampleyo = fondle
(sorry if im over simplifying im sure you get most of what im saying already but meh
)-
matchingtype is basically how you want tf to handle the line glob and regexp are what i normally use but both also have a different way of umm... writing the line
for example you want to trigger the line You have slain (whoever). and gag it and come up with a more personalized echo
if you use glob you would go something like
/def -ag -p0 -mglob -t'You have slain *' uslainthefoo = /echo -ahCwhite JOO OWNZ %{4}
/if you use regexp it would go something like
/def -ag -p0 -mregexp -t'^You have slain (.*)/.$' uslainthefoo = /echo -ahCwhite I ownage da %P1.
generally regexp is more flexible but i find uses for glob as well just depends on what you want to trigger.
-
-t well thats to say its a trigger there are other things like hooks etc.
-
hehe yeah that line
-
macro name you can do without but i find it good to put one on all your triggers anyway because it can be hell to find/edit/delete a trigger you dont have a name for plus you can call the macro as well like going
/
so /justanexampleyo would end up umm fondling (this is such a bad example but im lazy to rewrite now)
-
function well what ever you want it to do.
...
the regular experssion and glob difference well just ask here about a line and ill answer how i would trigger each in both... well ill try anyway
...
about the binding you didnt have trouble binding your function keys and keypad yeah? well you probably looked at your character map anyway... heh
...
ralshan we need to catch up? o.O
On another note, I updated my website with a few script files. They might help you out a bit. The one you'll probably find the most interesting is the status_prompt.tf script which handles the prompt triggering and obtaining updated information whenever you type 'score'.
www.bwbettin.com -> click on "TF Scripting"
www.bwbettin.com -> click on "TF Scripting"
