Fwd: exclusive vs. inclusive actions and selection

Forwarding to vim_dev from vim_use, seems to be a bug introduced since
7.2.284

John Little cannot duplicate the behavior on 7.2.284, but I see it on
7.2.320 on Windows gvim launched with -N -u NONE.

If it isn't clear, I had to :set selection=exclusive to see the
puzzling behavior. I assume he did this.

---------- Forwarded message ----------
From: Ben Fritz <fritzophre...@gmail.com>
Date: Jan 7, 12:14 pm
Subject: exclusive vs. inclusive actions and selection
To: vim_use

I'm a little puzzled over "exclusive" vs. "inclusive" actions and how
they interact with the 'selection' option.

Specifically, the 'e' and 'g_' commands seem inconsistent to me.

:help e says the cursor will be placed on the end of a word
(inclusive).

:help g_ says the cursor will be placed on the last nonblank character
in a line (also inclusive).

So, suppose I have a line with one word, like this:

anitdisestablishmentarianism

With 'selection' set to "inclusive", ^ve and ^vg_ do the same thing,
with a visual selection that looks like:

|anitdisestablishmentarianism|

With 'selection' set to "exclusive", ^ve gives:

|anitdisestablishmentarianism|

But ^vg_ gives:

|anitdisestablishmentarianis|m

This happens even with trailing whitespace on the line.

Why do two motions, both inclusive, that put the cursor in the same
place, create a different visual selection?