On 4/15/2016 11:52 AM, Roger Harman wrote:
I also voted for that one when I first saw it.
But, the "oneSpace" is a great workaround.
Where do you find these things?
I have an unhealthy tendency to use the command line instead of a mouse
or a dialogue box. After embarrassing myself with regex, I went back
into the documentation to see what else I was getting wrong.
Escape to get to the command line.
F1 to summon the help / references.
Click on 'Issuing editor commands'.
There are 3 separate concepts which are related to each other but are
different enough to warrant separate references:
Editor commands
Editor actions
Editor parameters
The distinction between commands and actions is that a command accepts
parameters; actions don't. Which makes an action quite suitable to
attach to a keyboard shortcut or mouse click :-) So 'findText', having
parameters, is a command but 'join' is an action suitable to assign to
say, Alt-j.
Editor Parameters are sort of like environment variables for the editor.
Many editor parameters set global behaviour, but others are more
transient, and act in concert with Editor Actions. Editor parameters
are retrieved with the 'query' command: 'query lines' retrieves the
number of lines in the source. Setting the parameters is done with the
'set' command. Here's an interesting thing to experiment with:
Open a source member.
Position to line 1, column 1.
Escape to go to the command line.
action right
Escape to go to the editor.
The cursor should be on line 1, column 2.
Escape to go to the command line
set actionArgument 25
action right
Escape to go back to the editor.
The cursor moved right 25 times.
All of this stuff is in there to help developers write plug-ins. But
they can all be used from the command line too, which weirdly enough, is
one way to prototype a script I want to run.
As an Amazon Associate we earn from qualifying purchases.