Re: Rotate shell words widget

[Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>]

On Sat, May 14, 2016 at 2:30 PM, Sebastian Gniazdowski
<sgniazdowski@xxxxxxxxx> wrote:
> On 13 May 2016 at 11:23, Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> wrote:
>> Also it looks like this always rotates all the words in the buffer, so
>> e.g. the last word moves to command position no matter what word the
>> cursor is on.  If the reason is to be able to edit a different word,
>> wouldn't it make more sense to move the word at the end to the cursor
>> (or the word at the cursor to the end)?
>
> I'm not fully following this, maybe an example? Seems sophisticated, though.

Suppose I have:

% echo one two three four

and the cursor is on the "w".  With your widget as-is, rotating "forward" gives

% four echo one two three

with the cursor on the space between "one" and "two".  I don't
understand why someone would ever want to do that.  It doesn't make
sense for "four" to become the command word, and the final cursor
placement isn't helpful.  (Also the choice of calling this "forward"
rotation is a bit arbitrary, because the most obvious change is that
"four" moved *backward*, it's the rest of the line that went forward;
but you can define it either way.)  If instead rotate forward produced

% echo one four two three

with the cursor either still on the "w" or somewhere in the word
"four", that might have some utility.  (This is what I meant by "acts
on $RBUFFER").  Similarly I'd expect rotate backward to do one of

% echo one three four two

OR ("acts on $LBUFFER")

% two echo one three four

though again I don't know why you'd shift a different word into
command position.  Maybe "rotate-arguments" would be a better widget,
something that would produce

% echo four one two three

i.e. without moving the "echo".

And in that case ESC 2 ESC r would produce

% echo three four one two

Cursor placement still needs some thought.