[first time] notation broken?

[paulobrian]

Not sure if this is a bug or my own denseness. Section 5.7 of the manual tells me:

say “[first time]”

or:
say “[only]”

This pair of text substitutions causes whatever is between them to be printed only the first time the text is printed. Example:

“The screen door squeaks loudly as when you open it. [first time]Well, you’ll get used to it eventually. [only]”

This is exactly equivalent to

“The screen door squeaks loudly as when you open it. [one of]Well, you’ll get used to it eventually. [or][stopping]”;

but easier to read.

However, I can’t seem to get that notation to work in my code:

[code]“Dude, Where’s My Description?” by Paul O’Brian

The Parking Garage is a room. “Dim and shadowy, but plenty roomy.”

A vehicle called my car is here. “My car is here, parked conveniently. [first time]Say what you will about the dimensional anomalies, they’ve really helped the parking situation.[only]”
[/code]
Yields this output:

Parking Garage
Dim and shadowy, but plenty roomy.

My car is here, parked conveniently.

The [first time] text is MIA. But if I change the car code to:

A vehicle called my car is here. "My car is here, parked conveniently. [one of]Say what you will about the dimensional anomalies, they've really helped the parking situation.[or][stopping]"

I get the desired result:

Parking Garage
Dim and shadowy, but plenty roomy.

My car is here, parked conveniently. Say what you will about the dimensional anomalies, they’ve really helped the parking situation.

L
Parking Garage
Dim and shadowy, but plenty roomy.

My car is here, parked conveniently.

So am I missing something, or is this a bug?

(Also, apologies if this has been reported before. The forum doesn’t seem to want to let me search on the term “first time”, complaining that the words are too common.)

[Draconis (Daniel Stelzer)]

It’s a known bug, which will hopefully be fixed in the next release.

[paulobrian]

Ah, and now I see that if I google “Inform 7 known bugs” I find my way to the Mantis tracker, which lets me see the bug right away. Thanks, Draconis.