Post by Stefan on Mar 2, 2023 11:43:16 GMT -5
George,
When editing a primary command, the (DataInsert) primitive functions like the (Insert) primitive.
I think for the command line this is perfectly fine, except perhaps that the Status Bar show INS in green instead of reverse video white, a cosmetic issue which many/most won't even notice.
However, while (Delete) and (Backspace) both work perfectly on the command line, (DataDelete) and (DataBackspace) do nothing.
I think it would be better if all these primitives' behaviour were standardised.
Given that (DataInsert) already leads the way (so why change it), I reckon the simplest way forward is to change the other (DataXXX) primitives to do what their "non-Data' counterparts do.
Then, when on the command line...
(DataInsert) actually performs (Insert) - as it already does,
(DataDelete) performs (Delete) and
(DataBackspace) performs (Backspace).
Why does this even matter?
I can only speak for myself here, but the recent changes to the (Data....) primitives has worked wonders for my productivity.
I have (DataDelete) and (DataInsert) as my defaults, each with its "non-Data" counterpart on the same keys but SHIFTed.
With this setup, I cannot easily edit a primary command because of the differnt behaviour of (DataDelete) and, by association (DataBackspace).
