NASA-AMMOS
Phoenix does very weird, bad formatting when searching text
Checked for duplicates
No - I haven't checked
Is this a regression?
No - This is a new bug
Version
v3.0.1
Describe the bug
A user reported (and I reproduced, using the same sequence) that, when searching text in a sequence, the editor made what looked like a formatting action (?) to turn hex values into integers (which it already probably shouldn't do), but it also messed up the command in the process. I'm unclear on what Phoenix is attempting to do, and even less clear on why it would be triggered by this specific navigation of the text search tool.
Reproduction
I'll work on a repro with an example that doesn't use Clipper commands, but I have a screen recording of the behavior that I can share with JPLers.
Logs
System Info
Phoenix for Clipper
Severity
Moderate
Sit rep: we're struggling to repro on Aerie 3.5.2 and Aerie 3.7.1, but it's not clear what changed between those versions that would affect this. @parkerabercrombie and @duranb are in the loop to do some more testing and see if they can isolate the problem (e.g., is this a Clipper adaptation thing?). @cohansen looked at it a while back and wasn't able to repro with Banananation commands but it's unclear whether that's an adaptation issue or if the dictionary doesn't contain whatever is triggering this.