| View previous topic :: View next topic |
| Author |
Message |
Tyler
Joined: 11 Jan 2008 Posts: 47
|
Posted: Sun Jun 08, 2008 3:32 pm Post subject: Tell Logging |
|
|
Here's what i'm confused about, with the #line command i'm perfectly able to log whatever line i want to, so for things such as this:
| Code: |
#ACTION {%0 tells you %1}
{
#line log {tells.txt} {%0 said: %1}
}
|
what gets me is the fact that I have to open the document every time I want to see whatever new tells I got sent, now my question is this: is there another way for me to be able to view a constantly updated string of tells in a seperate window for easier reading. My only idea so far was this
(create a new session with tt++, on a different mud, preferabbly without spam, and most nonsense gagged)
| Code: |
#ACTION {%0 tells you %1}
{
#tell;
#Var {%0 told you: %1}
{%0 told you :%1};
}
|
whenever I want to read said tells i just hit #Var, but I'm sure there is a much smarter way of going about things, anybody have ideas? |
|
| Back to top |
|
 |
Scandum Site Admin
Joined: 03 Dec 2004 Posts: 3281
|
Posted: Sun Jun 08, 2008 3:49 pm Post subject: |
|
|
You have a few options.
You can open a new terminal and use the linux tail command (tail -f tells.txt) to use a different window, on some systems you can launch a new terminal and have it tail a log file with the #system command.
You can also use: #run var tail -f tells.txt, and use #var to switch to the var sessions which should be running the tail command.
If you don't want to bother with a tells.txt file you could use:
#ACTION {~%0 tells you %1} {#gts #showme {%0 told you %1}}
The 'gts' session is the name of the startup session. |
|
| Back to top |
|
 |
Tyler
Joined: 11 Jan 2008 Posts: 47
|
Posted: Sun Jun 08, 2008 4:38 pm Post subject: |
|
|
these are good suggestions, but here's my problem
i'm having difficulties with #run and #system at the moment, thats probabbly more of a failure on my part, but the #gts, #showme was a great idea.... the only reason i wouldn't like to do that is because i can't see a list of #showme, i can only see it at the specific time of the tell. My objective here is to gag the tells i'm getting from players, and display it in this seperate window.... i'm still looking at #run and #system but do you know of any other way? |
|
| Back to top |
|
 |
Scandum Site Admin
Joined: 03 Dec 2004 Posts: 3281
|
Posted: Sun Jun 08, 2008 5:18 pm Post subject: |
|
|
#run and #system don't work with wintin++, so I guess that's the problem if you're on windows.
You can install cygwin http://tintin.sourceforge.net/install.php#Windows to gain more functionality but it's a 100 to 200 MB install. |
|
| Back to top |
|
 |
Tyler
Joined: 11 Jan 2008 Posts: 47
|
Posted: Mon Jun 09, 2008 5:39 pm Post subject: |
|
|
| I must be a knucklehead but i can't open the .bat file for cygwin using windows, it freaks... dunno why |
|
| Back to top |
|
 |
Tyler
Joined: 11 Jan 2008 Posts: 47
|
Posted: Mon Jun 09, 2008 6:06 pm Post subject: |
|
|
| while we're on a completely unrelated subject, is there a way to play a different sound other than the one from #bell using wt++? |
|
| Back to top |
|
 |
Scandum Site Admin
Joined: 03 Dec 2004 Posts: 3281
|
Posted: Tue Jun 10, 2008 8:43 am Post subject: |
|
|
Try to open the file with wordpad.exe
With cygwin installed you can play .wav files using: #system cat file.wav > /dev/dsp&} |
|
| Back to top |
|
 |
|