On Mar 16, 10:52 pm, Patrick A Inskeep [patrick.insk...@abbott.com]
wrote:
if a does not yank and not a does not yank, isn't that what you would expect?
a means no yank, not a means yank.
The user can choose which they want.
Or is this against what the help says?
Patrick
Dear Patrick,
Your
Dear Patrick,
Your comment is not clear to me.
Help says:
a options results in a word selected using Visual is automatically
yanked to the selection register (*).
It works.
With a suppressed, a Visual selected word is no longer yanked to
the selection buffer (*).
It works.
Now, I see no reason
On Mar 17, 12:25 pm, Christian Brabandt cbli...@256bit.org wrote:
You are on windows, aren't you? Windows has no concept of selection
and clipboard buffers. Therefore, the + register is the same as the *
register on Windows.
regards,
Christian
No, the problem is for unix of course (as
On Thu, March 17, 2011 2:35 pm, Jean Johner wrote:
On Mar 17, 12:25 pm, Christian Brabandt cbli...@256bit.org wrote:
You are on windows, aren't you? Windows has no concept of selection
and clipboard buffers. Therefore, the + register is the same as the *
register on Windows.
No, the problem
On Wed, Mar 16, 2011 at 02:52:19PM -0700, Jean Johner wrote:
Hello,
Zero comment on the below thread in vim_use.
I think it is a bug.
Best regards
Jean Johner
Hello,
Using gvim in unix, a is by default in guioptions.
Yanking a word to the Unix clipboard (with +yw) does not yank the
Hello,
Zero comment on the below thread in vim_use.
I think it is a bug.
Best regards
Jean Johner
Hello,
Using gvim in unix, a is by default in guioptions.
Yanking a word to the Unix clipboard (with +yw) does not yank the
word to the Selection buffer (*).
When suppressing the a option (with
