On Thu, Mar 17, 2011 at 3:15 AM, Jean Johner jean.joh...@cea.fr wrote:
[...]
Make a Select line selection on a line (triple click in Windows with
default _vimrc).
Extend the selection to the end of the file (Shift click in Windows)
Delete
A blank line is left at the end of the file (Windows
On Thu, March 17, 2011 9:04 am, Anurag Priyam wrote:
On Thu, Mar 17, 2011 at 3:15 AM, Jean Johner jean.joh...@cea.fr wrote:
[...]
Make a Select line selection on a line (triple click in Windows with
default _vimrc).
Extend the selection to the end of the file (Shift click in Windows)
Delete
On Thu, March 17, 2011 10:14 am, Christian Brabandt wrote:
On Thu, March 17, 2011 9:04 am, Anurag Priyam wrote:
On Thu, Mar 17, 2011 at 3:15 AM, Jean Johner jean.joh...@cea.fr wrote:
[...]
Make a Select line selection on a line (triple click in Windows with
default _vimrc).
Extend the
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
On Thu, March 17, 2011 12:05 pm, Ben Schmidt wrote:
I think it is a bug. That behaviour in other Windows apps is because
they only have the concept of a characterwise selection. When you are in
Ultraedit behaves that way to. And I think this has line wise selection mode.
SELECT LINE mode
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, 10:20 am, Christian Brabandt cbli...@256bit.org wrote:
Hm, after thinking about it, I wouldn't consider this a bug as this
behaves exactly as it works in other Windows applications.
(e.g. take notepad, open a file and select a line until the end of the
file. If you delete the
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
Ben Schmidt wrote:
Make a Select line selection on a line (triple click in Windows
with default _vimrc). Extend the selection to the end of the file
(Shift click in Windows)
Delete
A blank line is left at the end of the file (Windows or unix).
No such problem with the
Gary Johnson wrote:
I've encountered a problem using gvim 7.3.138 on a Windows XP system
because of the way that Vim expands plugin/**/*.vim when it loads
plugins. Specifically, Vim includes RCS file names that end with
.vim,v in that expansion.
From a command prompt I executed
On Mar 16, 4:28 pm, Jean Johner jean.joh...@cea.fr wrote:
Hello,
I made Cream without cream 7.3.138 vim complete installation on XP.
Opening a file with gvim and using the menu File/Split Diff with..., I
get the 2 following error messages:
E810: Cannot read or write temp files
then
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
On 2011-03-17, Bram Moolenaar wrote:
Gary Johnson wrote:
I've encountered a problem using gvim 7.3.138 on a Windows XP system
because of the way that Vim expands plugin/**/*.vim when it loads
plugins. Specifically, Vim includes RCS file names that end with
.vim,v in that expansion.
14 matches
Mail list logo
