Recorded script fails but works if pasted to command line

Well, since CT is a custom function, and since the script fails while interacting with CT, I was going to create a similar script from native commands as a more accessible demonstration of the problem and post that as file rather than as code. But here's the interesting part -- if I use an internal command like ERASE, the script doesn't fail! While trying to troubleshoot this, I had already tried to do noun/verb operation of CT by running SELECT, then using CT with a "p" for previous sset, but the SELECT runs and CT doesn't complete entity selection after the 'p'.

So....apparently this runs differently (specifically the (ssget)) when CT is called manually or "CT" is pasted into the command line vs. when called from a script. Why? Here's what's in CT:

(defun c:CT (/ count ent newval sset sub1)
    (graphscr)
    (setq sset (ssget) count 0)
    (while (< count (sslength sset))
        (setq ent (entget(ssname sset count)))
        (if (equal "TEXT" (cdr (assoc 0 ent)))
            (progn
                (setq newval (getstring T (strcat "\nNew value <" (cdr (assoc 1 ent)) ">: ")))
                (if (/= newval "")
                    (gced ent 1 newval)
                );end if
            );end progn
        ); end if
        (setq count (1+ count))
    );end while
    (princ)
);end defun

You mean that's an issue for CT in general or when called from script? If invoked manually, and the operator doesn't pick a text entity, so what? It just returns to the command line and he's more careful the next time. If you're talking about the current issue with script execution, there should always be text at that location, and I don't think that relates to the script failure because it's still in the (ssget) when it fails. I've not seen any failures due to an otherwise valid selection set that doesn't contain any text.

Wow -- in a strange way you called it! By inserting debugging statements into CT, I found that in fact entity selection was completing (command prompt showed with 1 entity as expected -- assumed but later found not to be the correct entity), then completing CT with no changes because the selected entity was NOT a text entity. I verified the coordinates in the script (and remember it works fine if you paste it), and they're correct.

So now I have a script that does nothing but draw a line between those same two points -- doesn't draw a thing. But enter the exact same command manually to the command prompt and it work perfectly. Here's a cap of the command line with the unsuccessful script calling an internal function, followed by it working right manually, with the same keystrokes. This is actually a verbatim cut and paste from my command window.

'_script

l
" LINE "

LINE
Start of line or [Follow] :28.97,0.77
Set end point or [Angle/Length/Undo]:32.95,0.87
Set end point or [Angle/Length/Follow/Undo]:

l

" LINE "

LINE
Start of line or [Follow] :
Start of line or [Follow] :28.97,0.77
Set end point or [Angle/Length/Undo]:32.95,0.87
Set end point or [Angle/Length/Follow/Undo]: