Thanks for the feedback here and we removed the highlighted
selection after running Cmd+Enter as continual support queries
noted the following:
1) After running a highlighted selection, users wanted to
advance to the next section of code quickly and pressing Cmd+Enter
only re-executes the same command leaving the user stuck. Instead,
typically pressing Cmd+Enter without a selection will always
advance to the next line of code.
2) Users often reported that they would run a highlighted
selection, and then immediately start typing after this (by habit
or intuition). This obviously would overrite the current selection
and the user might not notice or would then need to undo what was
just typed. Either way, the potential to lose code was a
undesirable state to leave the user.
We're not necessarily sold on either way, but obviously don't
want to jump back and forth on either method. An option to
configure this is possible and we considered this. For now we're
awaiting feedback such as this to see what the proper action
I strongly encourage you to add an additional shortcut key that
runs the current line (if there is no selection) and the selection
if there is a selection, without moving the cursor (or without
altering the selection if there is a selection). Perhaps something
like Cmd+Alt+Enter would be suitable.
I think both behaviours (i.e., moving the cursor and not moving
the cursor after executing a command) have important roles. I
imagine it would be a very simple feature to add. It would also
make life so much easier for people who want to use the script
editor a little bit like a console.