i don't know about that it would be possible to change.
So, it's a little funny answer, but if you write a "3Dcursor" macro and place it to the top of the 3D script as a Global and to the end as a Local 3D Cursor, it may help.
And of course you have to switch off the native 3D Cursor.
After you have used GDL for awhile, I doubt this will be such a big issue for you, particularly if you use some careful structured programming. Then it is always fairly easy to know where you are. After all, the axes are labeled as well as, sorta, colored.
The origin macro is a cute idea.
AC 19 6006 & AC 20
Mac OS 10.11.5
15" Retina MacBook Pro 2.6
27" iMac Retina 5K
As i recall you can also insert breaks in the code for debugging. I've never used it but I think the command is just BREAK. No arguments. There may be some other debug tricks that I'm not remembering. One trick I use sometimes is to throw in a simple