Odd dgdebug behavior

When I’m using dgddebug and I execute a query (rather than a game action), I get some odd output:

Saguaro; wiffs of evaporating gasoline linger in the chill air. On the dash you
can see a piece of jade.

> (tree)
#middle-of-nowhere (dark)
    #tower #in
    #sagebrush #in
    #desert-sand #in
    #tire-tracks #in
    #pickup-truck #in
        #knock #in (lit)
            #cigarettes #heldby (handled)
            #lighter #heldby (handled)
            #wallet #heldby (handled)
                #license #in
                #receipt #in
            #jacket #wornby
            #emotional-baggage #heldby (handled)
        #jade #in
        #headlights #partof
    #wiffs-of-gasoline #in
    #saguaro #in
Query succeeded: (tree)
> l
Query succeeded: (get input [l])
Middle of Nowhere (in the pickup truck)
The tire tracks from the south stop abruptly here, but where the hell are you? The desert sand and clumps of pale sagebrush are all your dimming headlights pick out before barely reaching the concrete building to the north.

Notice the extra Query succeeded: (get input [l])?

At first I thought this had something to do with the script I use to invoke dgdebug, but I also see it when I run dgdebug directly in terminal.

This is on OS X.

Will investigate. Thanks!

I remember the saguaro, the tower, middle of nowhere and the tire tracks … :grinning:

It‘d the sample story of that old Inform 7 book, isn‘t it?

Jens

1 Like

Yep. I’m building up a hopefully complete equivalent in Dialog.

It’s good for accelerating the search for edge cases and such.