tinyfugue-discuss Mailing List for TinyFugue

tinyfugue-discuss — Archives of tinyfugue@tcp.com list. Prefer "Open Discussion" forum for new talk.

You can subscribe to this list here.

2002	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov (39)	Dec (74)
2003	Jan (52)	Feb (51)	Mar (47)	Apr (52)	May (83)	Jun (58)	Jul (75)	Aug (37)	Sep (55)	Oct (51)	Nov (78)	Dec (103)
2004	Jan (72)	Feb (56)	Mar (71)	Apr (31)	May (16)	Jun (26)	Jul (67)	Aug (15)	Sep (43)	Oct (57)	Nov (34)	Dec (12)
2005	Jan (13)	Feb (34)	Mar (32)	Apr (42)	May (16)	Jun (53)	Jul (37)	Aug (43)	Sep (48)	Oct (41)	Nov (29)	Dec (7)
2006	Jan (41)	Feb (21)	Mar (28)	Apr (30)	May (16)	Jun (28)	Jul (12)	Aug (71)	Sep (20)	Oct (21)	Nov (5)	Dec (6)
2007	Jan (16)	Feb (3)	Mar	Apr	May	Jun (3)	Jul (18)	Aug (9)	Sep (6)	Oct (6)	Nov (6)	Dec
2008	Jan	Feb	Mar	Apr	May	Jun (1)	Jul (3)	Aug (1)	Sep (3)	Oct (2)	Nov	Dec
2009	Jan	Feb	Mar	Apr	May	Jun	Jul (15)	Aug (44)	Sep (5)	Oct (18)	Nov (7)	Dec (6)
2010	Jan	Feb (1)	Mar (1)	Apr (7)	May (1)	Jun (13)	Jul (51)	Aug (31)	Sep (22)	Oct (7)	Nov (2)	Dec (18)
2011	Jan (8)	Feb	Mar	Apr	May (2)	Jun (28)	Jul (9)	Aug (1)	Sep (37)	Oct (45)	Nov (8)	Dec (5)
2012	Jan (1)	Feb (7)	Mar (2)	Apr (8)	May (10)	Jun	Jul	Aug	Sep	Oct	Nov	Dec (3)
2013	Jan (11)	Feb	Mar	Apr	May	Jun (3)	Jul	Aug	Sep	Oct	Nov	Dec
2014	Jan	Feb (11)	Mar (13)	Apr (5)	May	Jun (6)	Jul (11)	Aug	Sep	Oct	Nov	Dec (4)
2015	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct (6)	Nov	Dec
2016	Jan	Feb	Mar	Apr (12)	May (7)	Jun (2)	Jul	Aug	Sep (4)	Oct (2)	Nov	Dec

Flat | Threaded

1 2 3 .. 106 > >> (Page 1 of 106)

Re: [tf-dis] Timestamp 'window' in TF

From: Paul <tf-...@ra...> - 2016-10-03 16:53:56

On Thursday, 22 September, 2016 at 16:45:57 BST, Colin Mackay wrote:
>At times it can be annoying when you realize you've been idle and the
>conversation you thought was recent happened half an hour ago...

In such cases, I'd "/recall -t <n>".

[tf-dis] Converting time?

From: Colin M. <zix...@gm...> - 2016-10-03 00:02:18

Not sure how to go about this; anyone know a quick way to convert the time
in idle('worldname') to HH:MM:SS?

For seconds, it returns SS:ms
3.673621

But when it gets up to minutes, it displays HH:MM:SS.ms

0:01:23.793138

Any way to make it only show HH:MM:SS with leading zeros and scrapping the
milliseconds?

00:01:23


Thanks. :)

Re: [tf-dis] Timestamp 'window' in TF

From: Bartek S. <ft...@in...> - 2016-09-22 16:33:20

> On 22 Sep 2016, at 6:30 PM, Colin Mackay <zix...@gm...> wrote:
> 
> That does work to some degree, but with paragraphs, you get line-wrapped and it doesn't look all that clear...  I'm using a fixed width font below, for those of you who are translating it into some kind of variable width...
> 
> 09:21 | Room name
> 09:21 | Description that's very long and
> just keeps going on the next line
> which kinda breaks the 'look'...
> 09:21 | Some Text
> 09:22 | Some Text
> 09:22 | Some Text
> 
> What'd I'm looking for:
> 
> 09:21 | Room name
> 09:21 | Description that's very long and
>       |  just keeps going on the next line
>       |  which doesn't break the 'look'...
> 09:21 | Some Text
> 09:22 | Some Text
> 09:22 | Some Text

/set wrapspace=8

-- 
Bartek ‘ftpd’ Stalewski

Re: [tf-dis] Timestamp 'window' in TF

From: Bartek S. <ft...@in...> - 2016-09-22 16:31:12

> 
> On 22 Sep 2016, at 5:45 PM, Colin Mackay <zix...@gm...> wrote:
> 
> More or less just a passing thought after looking over a recent time-stamped log.
> 
> Is it possible to have perhaps a vertical status area along the left side of the output area with a simple timestamp?
> 
> Example:
> 
> 09:55 | 5 players are awake
> 09:55 | The Room Name
> 09:55 | Before you is a room with a multiline
>           |   description, neat huh?
> 09:56 | You say, "Hello everyone!"
> 09:57 | Everyone smiles in response, "Good day, eh?"
> 
> Not even sure if I'd use it.  At times it can be annoying when you realize you've been idle and the conversation you thought was recent happened half an hour ago...
> 
> Thoughts?

The simplest way is to substitute _every_ line, adding time before it - something like that:
/def -mregexp -Fp1 -t'.*' = /test substitute(strcat(ftime("%H:%M:%S",time()), " | ", {P0}))

But I assume it easily can make your script pack _very_ slow :(

-- 
Bartek ‘ftpd’ Stalewski

Re: [tf-dis] Timestamp 'window' in TF

From: Colin M. <zix...@gm...> - 2016-09-22 16:30:45

That does work to some degree, but with paragraphs, you get line-wrapped
and it doesn't look all that clear...  I'm using a fixed width font below,
for those of you who are translating it into some kind of variable width...

09:21 | Room name
09:21 | Description that's very long and
just keeps going on the next line
which kinda breaks the 'look'...
09:21 | Some Text
09:22 | Some Text
09:22 | Some Text

What'd I'm looking for:

09:21 | Room name
09:21 | Description that's very long and
      |  just keeps going on the next line
      |  which doesn't break the 'look'...
09:21 | Some Text
09:22 | Some Text
09:22 | Some Text


On Thu, Sep 22, 2016 at 12:14 PM, Bartek Stalewski <ft...@in...>
wrote:

> >
> > On 22 Sep 2016, at 5:45 PM, Colin Mackay <zix...@gm...> wrote:
> >
> > More or less just a passing thought after looking over a recent
> time-stamped log.
> >
> > Is it possible to have perhaps a vertical status area along the left
> side of the output area with a simple timestamp?
> >
> > Example:
> >
> > 09:55 | 5 players are awake
> > 09:55 | The Room Name
> > 09:55 | Before you is a room with a multiline
> >           |   description, neat huh?
> > 09:56 | You say, "Hello everyone!"
> > 09:57 | Everyone smiles in response, "Good day, eh?"
> >
> > Not even sure if I'd use it.  At times it can be annoying when you
> realize you've been idle and the conversation you thought was recent
> happened half an hour ago...
> >
> > Thoughts?
>
> The simplest way is to substitute _every_ line, adding time before it -
> something like that:
> /def -mregexp -Fp1 -t'.*' = /test substitute(strcat(ftime("%H:%M:%S",time()),
> " | ", {P0}))
>
> But I assume it easily can make your script pack _very_ slow :(
>
> --
> Bartek ‘ftpd’ Stalewski

[tf-dis] Timestamp 'window' in TF

From: Colin M. <zix...@gm...> - 2016-09-22 15:46:05

More or less just a passing thought after looking over a recent
time-stamped log.

Is it possible to have perhaps a vertical status area along the left side
of the output area with a simple timestamp?

Example:

09:55 | 5 players are awake
09:55 | The Room Name
09:55 | Before you is a room with a multiline
          |   description, neat huh?
09:56 | You say, "Hello everyone!"
09:57 | Everyone smiles in response, "Good day, eh?"

Not even sure if I'd use it.  At times it can be annoying when you realize
you've been idle and the conversation you thought was recent happened half
an hour ago...

Thoughts?

Re: [tf-dis] randline function in textutil.tf

From: Ron <rph...@ho...> - 2016-06-12 22:51:25

Edit testutil.tf and change the line in this method from:


        /test rand(++_lines) | (_selection := {*})%; \


.. to..

        /test rand(++_lines) | (_selection := {_line})%; \

That should do it.

________________________________
From: ha...@vn... <ha...@vn...>
Sent: Sunday, June 12, 2016 8:33 AM
To: TinyFugue Discussions
Subject: [tf-dis] randline function in textutil.tf

Hello all.  I've used other functions from the textutil.tf file with no problems, but when attempting to use the randline function, things aren't working as I expected them to.  The description in the helpfiles says that it should return a random line from the handle or from tfin.  All I can get it to do for me is to return the actual handle (the stream ID from when the file I want searched is open).  So here is the code I have.

First, the data file.  Its just a text file with different text on separate lines, that will eventually be random party names, but just this boring stuff for now.

party_db.txt:
line 1
line 2
line 3
line 4

Here is the test script I wrote:

/require textutil.tf

/def temp = \
        /let temp=$[tfopen("party_db.txt", "r")] %; \
        /randline %{temp} %; \
        /test tfclose(%{temp})

So this _should_ return a random line from the data file, but just gives me the number of the tfio stream it is supposed to be searching.  If anybody has gotten this to work, please let me know what you did!

Thanks

--Tommy



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
TinyFugue-discuss mailing list
Tin...@li...
https://lists.sourceforge.net/lists/listinfo/tinyfugue-discuss

[tf-dis] randline function in textutil.tf

From: <ha...@vn...> - 2016-06-12 13:47:56

Hello all.  I've used other functions from the textutil.tf file with no problems, but when attempting to use the randline function, things aren't working as I expected them to.  The description in the helpfiles says that it should return a random line from the handle or from tfin.  All I can get it to do for me is to return the actual handle (the stream ID from when the file I want searched is open).  So here is the code I have.

First, the data file.  Its just a text file with different text on separate lines, that will eventually be random party names, but just this boring stuff for now.

party_db.txt:
line 1
line 2
line 3
line 4

Here is the test script I wrote:

/require textutil.tf

/def temp = \
	/let temp=$[tfopen("party_db.txt", "r")] %; \
	/randline %{temp} %; \
	/test tfclose(%{temp})

So this _should_ return a random line from the data file, but just gives me the number of the tfio stream it is supposed to be searching.  If anybody has gotten this to work, please let me know what you did!

Thanks

--Tommy

Re: [tf-dis] Capturing a gagged line in a variable

From: Colin M. <zix...@gm...> - 2016-05-08 15:15:31

I'd like to thank everyone for the help in getting this working.  I now
understand a little more about TF after all this time... :p

Here's the final code I worked out:

Grab location from a gagged line:

/def -ag -t'^<loc>[A-Za-z0-9].*<loc>$' loc_name= %; \
    /set loc_full=%{P0} %; \
    /set loc_wn=$[replace("-", "_", ${world_name})] %; \
    /set room_%{loc_wn}=$[replace("<loc>", "", {loc_full})] %; \
    /eval /set room=%%room_%{loc_wn}

Create change world hook, to update the variable used in the status bar:

/def -hWORLD setRoomWorldHook = \
    /set world_name=$[replace("-", "_", {1})]%; \
    /eval /set room=%%room_%world_name


Thanks again!  I have another question that google isn't answering, so I'll
ask it in another thread.

:D

On Thu, May 5, 2016 at 8:18 PM, Jacob Finn <sup...@gm...> wrote:

> You need to create a new evaluation scope so that %{world_name} will be
> substituted with its value in time to act as part of the room_X variable
> name.  Like so, for example:
>
> /eval /set room=%%room_%{world_name}
>
> When the hook fires, a scope is created and substitution is performed on
> the hook body, turning that line into this:
>
> /eval /set room=%room_WORLD1
>
> Then, /eval creates a new scope and substitution is performed again,
> turning it into this:
>
> /set room=My Room
>
> On a side note, macro substitution is generally a strange thing to do in
> an expression, but it works here thanks to some special cases for world
> fields (which I didn't know about before, so thanks!).  A nicer way to do
> it in an expression would be with the world_info function:
>
> /set world_name=$[replace("-", "_", world_info())]%; \
>
> But then, this is a WORLD hook, so the world name is already passed as the
> first argument.  You can use %1 instead (Or {1} since it's in an
> expression).  Here's how I would write your hook (I always use /def, mostly
> so I can name things, but that's entirely up to you):
>
> /def -hWORLD setRoomWorldHook = \
>     /set world_name=$[replace("-", "_", {1})]%; \
>     /eval /set room=%%room_%world_name
>
> I recommend you read the /help on: scope; evaluation; percent compression;
> substitution; expressions.
>
>
> On Thu, May 5, 2016 at 1:46 PM, Colin Mackay <zix...@gm...> wrote:
>
>> So the %; \ fixed it... Starting to understand where it's needed after
>> messing with it this afternoon.  This is what I ended up with:
>>
>> /def -ag -t'^<loc>[A-Za-z0-9].*<loc>$' loc_name= %; \
>>     /set loc_full=%{P0} %; \
>>     /set loc_wn=$[replace("-", "_", ${world_name})] %; \
>>     /set room_%{loc_wn}=$[replace("<loc>", "", %loc_full)]
>>
>> So I end up with the following, when specific text appears:
>>
>> room_WORLD1 = My Room
>> room_WORLD2 = My Other Room
>>
>>
>> Now, I'm trying to use a hook, which works to some degree.  All it needs
>> to do is place the room_WORLDx contents into the 'room' variable.
>>
>> /hook WORLD = \
>>     /set world_name=$[replace("-", "_", ${world_name})] %; \
>>     /set room=%room_%{world_name}
>>
>> All it seems to do is put the world name itself there.  I'm sure this
>> isn't the right way to do this, it's just what I came up with.
>>
>>
>> (*Note*:  I do the replace on the world_name variable as my world names
>> have hyphens (-) and variable names don't like hypens.)
>>
>>
>> On Thu, May 5, 2016 at 7:38 AM, lost addams <fil...@gm...>
>> wrote:
>>
>>> Wow, that was some serious overlooking on my part.
>>>
>>> On Thu, May 5, 2016 at 12:25 AM, Kai <tin...@ne...> wrote:
>>>
>>>> You need a %; between lines in the trigger body:
>>>>
>>>>   /def -ag -t'^<loc>.*<\/loc>$' loc_name = \
>>>>     /set loc=%{P0} %; \
>>>>     /send say %{loc}
>>>>
>>>> --Kai
>>>>
>>>>
>>>> On Wed, May 04, 2016 at 04:05:14PM -0400, Colin Mackay wrote:
>>>> > Hello folks.
>>>> >
>>>> > I've been fiddling with the idea of putting my current location into
>>>> the
>>>> > status bar for a while, just got around to looking into it.  Not sure
>>>> if
>>>> > this is the best way, but as I connect to 'freeform' MUCKs, there
>>>> isn't
>>>> > anything specific that I can use for my location, so I created a small
>>>> > command that will output:
>>>> >
>>>> > <loc>Room Name</loc>
>>>> >
>>>> > My plan was to gag the line, while hopefully figuring out how to
>>>> place that
>>>> > line into a variable.  This is my initial test:
>>>> >
>>>> > /def -ag -t'^<loc>[A-Za-z0-9].*<\/loc>$' loc_name = say %{P0}
>>>> >
>>>> > And hooray!  My character says:
>>>> >
>>>> > Zxarr says, "<loc>Room Name</loc>"
>>>> >
>>>> > So I tried going a little farther, which is where I'm starting to lose
>>>> > control:
>>>> >
>>>> > /def -ag -t'^<loc>.*<\/loc>$' loc_name = \
>>>> > /set loc=%{P0} \
>>>> > /send say %{loc}
>>>> >
>>>> > Shouldn't this do the same thing?
>>>> >
>>>> > I've tried %%{P0} as well and replacing %{loc} with %{P0} in the /send
>>>> > command...
>>>> >
>>>> >
>>>> > Thanks everyone.
>>>>
>>>> >
>>>> ------------------------------------------------------------------------------
>>>> > Find and fix application performance issues faster with Applications
>>>> Manager
>>>> > Applications Manager provides deep performance insights into multiple
>>>> tiers of
>>>> > your business applications. It resolves application problems quickly
>>>> and
>>>> > reduces your MTTR. Get your free trial!
>>>> > https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
>>>>
>>>> > _______________________________________________
>>>> > TinyFugue-discuss mailing list
>>>> > Tin...@li...
>>>> > https://lists.sourceforge.net/lists/listinfo/tinyfugue-discuss
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Find and fix application performance issues faster with Applications
>>>> Manager
>>>> Applications Manager provides deep performance insights into multiple
>>>> tiers of
>>>> your business applications. It resolves application problems quickly and
>>>> reduces your MTTR. Get your free trial!
>>>> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
>>>> _______________________________________________
>>>> TinyFugue-discuss mailing list
>>>> Tin...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/tinyfugue-discuss
>>>>
>>>
>>>
>>>
>>> --
>>> Film the dead; see how they lie.
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Find and fix application performance issues faster with Applications
>>> Manager
>>> Applications Manager provides deep performance insights into multiple
>>> tiers of
>>> your business applications. It resolves application problems quickly and
>>> reduces your MTTR. Get your free trial!
>>> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
>>> _______________________________________________
>>> TinyFugue-discuss mailing list
>>> Tin...@li...
>>> https://lists.sourceforge.net/lists/listinfo/tinyfugue-discuss
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> Find and fix application performance issues faster with Applications
>> Manager
>> Applications Manager provides deep performance insights into multiple
>> tiers of
>> your business applications. It resolves application problems quickly and
>> reduces your MTTR. Get your free trial!
>> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
>> _______________________________________________
>> TinyFugue-discuss mailing list
>> Tin...@li...
>> https://lists.sourceforge.net/lists/listinfo/tinyfugue-discuss
>>
>>
>
>
> ------------------------------------------------------------------------------
> Find and fix application performance issues faster with Applications
> Manager
> Applications Manager provides deep performance insights into multiple
> tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial!
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> _______________________________________________
> TinyFugue-discuss mailing list
> Tin...@li...
> https://lists.sourceforge.net/lists/listinfo/tinyfugue-discuss
>
>

Re: [tf-dis] Capturing a gagged line in a variable

From: Jacob F. <sup...@gm...> - 2016-05-06 00:18:32

You need to create a new evaluation scope so that %{world_name} will be
substituted with its value in time to act as part of the room_X variable
name.  Like so, for example:

/eval /set room=%%room_%{world_name}

When the hook fires, a scope is created and substitution is performed on
the hook body, turning that line into this:

/eval /set room=%room_WORLD1

Then, /eval creates a new scope and substitution is performed again,
turning it into this:

/set room=My Room

On a side note, macro substitution is generally a strange thing to do in an
expression, but it works here thanks to some special cases for world fields
(which I didn't know about before, so thanks!).  A nicer way to do it in an
expression would be with the world_info function:

/set world_name=$[replace("-", "_", world_info())]%; \

But then, this is a WORLD hook, so the world name is already passed as the
first argument.  You can use %1 instead (Or {1} since it's in an
expression).  Here's how I would write your hook (I always use /def, mostly
so I can name things, but that's entirely up to you):

/def -hWORLD setRoomWorldHook = \
    /set world_name=$[replace("-", "_", {1})]%; \
    /eval /set room=%%room_%world_name

I recommend you read the /help on: scope; evaluation; percent compression;
substitution; expressions.


On Thu, May 5, 2016 at 1:46 PM, Colin Mackay <zix...@gm...> wrote:

> So the %; \ fixed it... Starting to understand where it's needed after
> messing with it this afternoon.  This is what I ended up with:
>
> /def -ag -t'^<loc>[A-Za-z0-9].*<loc>$' loc_name= %; \
>     /set loc_full=%{P0} %; \
>     /set loc_wn=$[replace("-", "_", ${world_name})] %; \
>     /set room_%{loc_wn}=$[replace("<loc>", "", %loc_full)]
>
> So I end up with the following, when specific text appears:
>
> room_WORLD1 = My Room
> room_WORLD2 = My Other Room
>
>
> Now, I'm trying to use a hook, which works to some degree.  All it needs
> to do is place the room_WORLDx contents into the 'room' variable.
>
> /hook WORLD = \
>     /set world_name=$[replace("-", "_", ${world_name})] %; \
>     /set room=%room_%{world_name}
>
> All it seems to do is put the world name itself there.  I'm sure this
> isn't the right way to do this, it's just what I came up with.
>
>
> (*Note*:  I do the replace on the world_name variable as my world names
> have hyphens (-) and variable names don't like hypens.)
>
>
> On Thu, May 5, 2016 at 7:38 AM, lost addams <fil...@gm...>
> wrote:
>
>> Wow, that was some serious overlooking on my part.
>>
>> On Thu, May 5, 2016 at 12:25 AM, Kai <tin...@ne...> wrote:
>>
>>> You need a %; between lines in the trigger body:
>>>
>>>   /def -ag -t'^<loc>.*<\/loc>$' loc_name = \
>>>     /set loc=%{P0} %; \
>>>     /send say %{loc}
>>>
>>> --Kai
>>>
>>>
>>> On Wed, May 04, 2016 at 04:05:14PM -0400, Colin Mackay wrote:
>>> > Hello folks.
>>> >
>>> > I've been fiddling with the idea of putting my current location into
>>> the
>>> > status bar for a while, just got around to looking into it.  Not sure
>>> if
>>> > this is the best way, but as I connect to 'freeform' MUCKs, there isn't
>>> > anything specific that I can use for my location, so I created a small
>>> > command that will output:
>>> >
>>> > <loc>Room Name</loc>
>>> >
>>> > My plan was to gag the line, while hopefully figuring out how to place
>>> that
>>> > line into a variable.  This is my initial test:
>>> >
>>> > /def -ag -t'^<loc>[A-Za-z0-9].*<\/loc>$' loc_name = say %{P0}
>>> >
>>> > And hooray!  My character says:
>>> >
>>> > Zxarr says, "<loc>Room Name</loc>"
>>> >
>>> > So I tried going a little farther, which is where I'm starting to lose
>>> > control:
>>> >
>>> > /def -ag -t'^<loc>.*<\/loc>$' loc_name = \
>>> > /set loc=%{P0} \
>>> > /send say %{loc}
>>> >
>>> > Shouldn't this do the same thing?
>>> >
>>> > I've tried %%{P0} as well and replacing %{loc} with %{P0} in the /send
>>> > command...
>>> >
>>> >
>>> > Thanks everyone.
>>>
>>> >
>>> ------------------------------------------------------------------------------
>>> > Find and fix application performance issues faster with Applications
>>> Manager
>>> > Applications Manager provides deep performance insights into multiple
>>> tiers of
>>> > your business applications. It resolves application problems quickly
>>> and
>>> > reduces your MTTR. Get your free trial!
>>> > https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
>>>
>>> > _______________________________________________
>>> > TinyFugue-discuss mailing list
>>> > Tin...@li...
>>> > https://lists.sourceforge.net/lists/listinfo/tinyfugue-discuss
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Find and fix application performance issues faster with Applications
>>> Manager
>>> Applications Manager provides deep performance insights into multiple
>>> tiers of
>>> your business applications. It resolves application problems quickly and
>>> reduces your MTTR. Get your free trial!
>>> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
>>> _______________________________________________
>>> TinyFugue-discuss mailing list
>>> Tin...@li...
>>> https://lists.sourceforge.net/lists/listinfo/tinyfugue-discuss
>>>
>>
>>
>>
>> --
>> Film the dead; see how they lie.
>>
>>
>> ------------------------------------------------------------------------------
>> Find and fix application performance issues faster with Applications
>> Manager
>> Applications Manager provides deep performance insights into multiple
>> tiers of
>> your business applications. It resolves application problems quickly and
>> reduces your MTTR. Get your free trial!
>> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
>> _______________________________________________
>> TinyFugue-discuss mailing list
>> Tin...@li...
>> https://lists.sourceforge.net/lists/listinfo/tinyfugue-discuss
>>
>>
>
>
> ------------------------------------------------------------------------------
> Find and fix application performance issues faster with Applications
> Manager
> Applications Manager provides deep performance insights into multiple
> tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial!
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> _______________________________________________
> TinyFugue-discuss mailing list
> Tin...@li...
> https://lists.sourceforge.net/lists/listinfo/tinyfugue-discuss
>
>

Re: [tf-dis] Capturing a gagged line in a variable

From: Colin M. <zix...@gm...> - 2016-05-05 20:46:46

So the %; \ fixed it... Starting to understand where it's needed after
messing with it this afternoon.  This is what I ended up with:

/def -ag -t'^<loc>[A-Za-z0-9].*<loc>$' loc_name= %; \
    /set loc_full=%{P0} %; \
    /set loc_wn=$[replace("-", "_", ${world_name})] %; \
    /set room_%{loc_wn}=$[replace("<loc>", "", %loc_full)]

So I end up with the following, when specific text appears:

room_WORLD1 = My Room
room_WORLD2 = My Other Room


Now, I'm trying to use a hook, which works to some degree.  All it needs to
do is place the room_WORLDx contents into the 'room' variable.

/hook WORLD = \
    /set world_name=$[replace("-", "_", ${world_name})] %; \
    /set room=%room_%{world_name}

All it seems to do is put the world name itself there.  I'm sure this isn't
the right way to do this, it's just what I came up with.


(*Note*:  I do the replace on the world_name variable as my world names
have hyphens (-) and variable names don't like hypens.)


On Thu, May 5, 2016 at 7:38 AM, lost addams <fil...@gm...> wrote:

> Wow, that was some serious overlooking on my part.
>
> On Thu, May 5, 2016 at 12:25 AM, Kai <tin...@ne...> wrote:
>
>> You need a %; between lines in the trigger body:
>>
>>   /def -ag -t'^<loc>.*<\/loc>$' loc_name = \
>>     /set loc=%{P0} %; \
>>     /send say %{loc}
>>
>> --Kai
>>
>>
>> On Wed, May 04, 2016 at 04:05:14PM -0400, Colin Mackay wrote:
>> > Hello folks.
>> >
>> > I've been fiddling with the idea of putting my current location into the
>> > status bar for a while, just got around to looking into it.  Not sure if
>> > this is the best way, but as I connect to 'freeform' MUCKs, there isn't
>> > anything specific that I can use for my location, so I created a small
>> > command that will output:
>> >
>> > <loc>Room Name</loc>
>> >
>> > My plan was to gag the line, while hopefully figuring out how to place
>> that
>> > line into a variable.  This is my initial test:
>> >
>> > /def -ag -t'^<loc>[A-Za-z0-9].*<\/loc>$' loc_name = say %{P0}
>> >
>> > And hooray!  My character says:
>> >
>> > Zxarr says, "<loc>Room Name</loc>"
>> >
>> > So I tried going a little farther, which is where I'm starting to lose
>> > control:
>> >
>> > /def -ag -t'^<loc>.*<\/loc>$' loc_name = \
>> > /set loc=%{P0} \
>> > /send say %{loc}
>> >
>> > Shouldn't this do the same thing?
>> >
>> > I've tried %%{P0} as well and replacing %{loc} with %{P0} in the /send
>> > command...
>> >
>> >
>> > Thanks everyone.
>>
>> >
>> ------------------------------------------------------------------------------
>> > Find and fix application performance issues faster with Applications
>> Manager
>> > Applications Manager provides deep performance insights into multiple
>> tiers of
>> > your business applications. It resolves application problems quickly and
>> > reduces your MTTR. Get your free trial!
>> > https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
>>
>> > _______________________________________________
>> > TinyFugue-discuss mailing list
>> > Tin...@li...
>> > https://lists.sourceforge.net/lists/listinfo/tinyfugue-discuss
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Find and fix application performance issues faster with Applications
>> Manager
>> Applications Manager provides deep performance insights into multiple
>> tiers of
>> your business applications. It resolves application problems quickly and
>> reduces your MTTR. Get your free trial!
>> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
>> _______________________________________________
>> TinyFugue-discuss mailing list
>> Tin...@li...
>> https://lists.sourceforge.net/lists/listinfo/tinyfugue-discuss
>>
>
>
>
> --
> Film the dead; see how they lie.
>
>
> ------------------------------------------------------------------------------
> Find and fix application performance issues faster with Applications
> Manager
> Applications Manager provides deep performance insights into multiple
> tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial!
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> _______________________________________________
> TinyFugue-discuss mailing list
> Tin...@li...
> https://lists.sourceforge.net/lists/listinfo/tinyfugue-discuss
>
>

Re: [tf-dis] Capturing a gagged line in a variable

From: lost a. <fil...@gm...> - 2016-05-05 11:38:15

Wow, that was some serious overlooking on my part.

On Thu, May 5, 2016 at 12:25 AM, Kai <tin...@ne...> wrote:

> You need a %; between lines in the trigger body:
>
>   /def -ag -t'^<loc>.*<\/loc>$' loc_name = \
>     /set loc=%{P0} %; \
>     /send say %{loc}
>
> --Kai
>
>
> On Wed, May 04, 2016 at 04:05:14PM -0400, Colin Mackay wrote:
> > Hello folks.
> >
> > I've been fiddling with the idea of putting my current location into the
> > status bar for a while, just got around to looking into it.  Not sure if
> > this is the best way, but as I connect to 'freeform' MUCKs, there isn't
> > anything specific that I can use for my location, so I created a small
> > command that will output:
> >
> > <loc>Room Name</loc>
> >
> > My plan was to gag the line, while hopefully figuring out how to place
> that
> > line into a variable.  This is my initial test:
> >
> > /def -ag -t'^<loc>[A-Za-z0-9].*<\/loc>$' loc_name = say %{P0}
> >
> > And hooray!  My character says:
> >
> > Zxarr says, "<loc>Room Name</loc>"
> >
> > So I tried going a little farther, which is where I'm starting to lose
> > control:
> >
> > /def -ag -t'^<loc>.*<\/loc>$' loc_name = \
> > /set loc=%{P0} \
> > /send say %{loc}
> >
> > Shouldn't this do the same thing?
> >
> > I've tried %%{P0} as well and replacing %{loc} with %{P0} in the /send
> > command...
> >
> >
> > Thanks everyone.
>
> >
> ------------------------------------------------------------------------------
> > Find and fix application performance issues faster with Applications
> Manager
> > Applications Manager provides deep performance insights into multiple
> tiers of
> > your business applications. It resolves application problems quickly and
> > reduces your MTTR. Get your free trial!
> > https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
>
> > _______________________________________________
> > TinyFugue-discuss mailing list
> > Tin...@li...
> > https://lists.sourceforge.net/lists/listinfo/tinyfugue-discuss
>
>
>
> ------------------------------------------------------------------------------
> Find and fix application performance issues faster with Applications
> Manager
> Applications Manager provides deep performance insights into multiple
> tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial!
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> _______________________________________________
> TinyFugue-discuss mailing list
> Tin...@li...
> https://lists.sourceforge.net/lists/listinfo/tinyfugue-discuss
>



-- 
Film the dead; see how they lie.

Re: [tf-dis] Capturing a gagged line in a variable

From: Kai <tin...@ne...> - 2016-05-05 04:41:45

You need a %; between lines in the trigger body:

  /def -ag -t'^<loc>.*<\/loc>$' loc_name = \
    /set loc=%{P0} %; \
    /send say %{loc}

--Kai


On Wed, May 04, 2016 at 04:05:14PM -0400, Colin Mackay wrote:
> Hello folks.
> 
> I've been fiddling with the idea of putting my current location into the
> status bar for a while, just got around to looking into it.  Not sure if
> this is the best way, but as I connect to 'freeform' MUCKs, there isn't
> anything specific that I can use for my location, so I created a small
> command that will output:
> 
> <loc>Room Name</loc>
> 
> My plan was to gag the line, while hopefully figuring out how to place that
> line into a variable.  This is my initial test:
> 
> /def -ag -t'^<loc>[A-Za-z0-9].*<\/loc>$' loc_name = say %{P0}
> 
> And hooray!  My character says:
> 
> Zxarr says, "<loc>Room Name</loc>"
> 
> So I tried going a little farther, which is where I'm starting to lose
> control:
> 
> /def -ag -t'^<loc>.*<\/loc>$' loc_name = \
> /set loc=%{P0} \
> /send say %{loc}
> 
> Shouldn't this do the same thing?
> 
> I've tried %%{P0} as well and replacing %{loc} with %{P0} in the /send
> command...
> 
> 
> Thanks everyone.

> ------------------------------------------------------------------------------
> Find and fix application performance issues faster with Applications Manager
> Applications Manager provides deep performance insights into multiple tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial!
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z

> _______________________________________________
> TinyFugue-discuss mailing list
> Tin...@li...
> https://lists.sourceforge.net/lists/listinfo/tinyfugue-discuss

Re: [tf-dis] Capturing a gagged line in a variable

From: lost a. <fil...@gm...> - 2016-05-05 03:26:46

Pretty sure you'd need to do /eval /send say %{loc} because I think you
need the /eval to expand %{loc} or %{P0}. I'm not 100% sure but it's one of
the first things I try when I experience similar issues.

On Wed, May 4, 2016 at 4:05 PM, Colin Mackay <zix...@gm...> wrote:

> Hello folks.
>
> I've been fiddling with the idea of putting my current location into the
> status bar for a while, just got around to looking into it.  Not sure if
> this is the best way, but as I connect to 'freeform' MUCKs, there isn't
> anything specific that I can use for my location, so I created a small
> command that will output:
>
> <loc>Room Name</loc>
>
> My plan was to gag the line, while hopefully figuring out how to place
> that line into a variable.  This is my initial test:
>
> /def -ag -t'^<loc>[A-Za-z0-9].*<\/loc>$' loc_name = say %{P0}
>
> And hooray!  My character says:
>
> Zxarr says, "<loc>Room Name</loc>"
>
> So I tried going a little farther, which is where I'm starting to lose
> control:
>
> /def -ag -t'^<loc>.*<\/loc>$' loc_name = \
> /set loc=%{P0} \
> /send say %{loc}
>
> Shouldn't this do the same thing?
>
> I've tried %%{P0} as well and replacing %{loc} with %{P0} in the /send
> command...
>
>
> Thanks everyone.
>
>
> ------------------------------------------------------------------------------
> Find and fix application performance issues faster with Applications
> Manager
> Applications Manager provides deep performance insights into multiple
> tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial!
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> _______________________________________________
> TinyFugue-discuss mailing list
> Tin...@li...
> https://lists.sourceforge.net/lists/listinfo/tinyfugue-discuss
>
>


-- 
Film the dead; see how they lie.

[tf-dis] Capturing a gagged line in a variable

From: Colin M. <zix...@gm...> - 2016-05-04 20:05:21

Hello folks.

I've been fiddling with the idea of putting my current location into the
status bar for a while, just got around to looking into it.  Not sure if
this is the best way, but as I connect to 'freeform' MUCKs, there isn't
anything specific that I can use for my location, so I created a small
command that will output:

<loc>Room Name</loc>

My plan was to gag the line, while hopefully figuring out how to place that
line into a variable.  This is my initial test:

/def -ag -t'^<loc>[A-Za-z0-9].*<\/loc>$' loc_name = say %{P0}

And hooray!  My character says:

Zxarr says, "<loc>Room Name</loc>"

So I tried going a little farther, which is where I'm starting to lose
control:

/def -ag -t'^<loc>.*<\/loc>$' loc_name = \
/set loc=%{P0} \
/send say %{loc}

Shouldn't this do the same thing?

I've tried %%{P0} as well and replacing %{loc} with %{P0} in the /send
command...


Thanks everyone.