Thank you - point taken about quotes being redundant in my set clipboard=.
I completely forgot about the black hole register! Thank you.
On Friday, 30 May 2014 00:48:51 UTC+1, ZyX wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On May 29, 2014 9:25:05 PM GMT+03:00,
Point taken about quotes being comment indicators in my set clipboard=.
I completely forgot about the black hole register! Isn't vim wonderful just to
have that concept!
Thank you ZyX - and John for making sure I didn't miss the black hole advice.
Praful
--
--
You received this message from
Hi Praful!
On Do, 29 Mai 2014, Praful Kapadia wrote:
I have had an annoying issue with gvim 7.4, with patches 1-307. If I open a
large file (e.g. containing 200,000 lines) and use the global command to
delete lines, the operation takes a very long time on Windows if clipboard
has been set
On Friday, 30 May 2014 12:27:01 UTC+1, Christian Brabandt wrote:
This is a known issue for windows (see :h todo.txt and search for
:g/test/d)
Thanks Christian - and apologies to all for not seeing the todo list
Here is an experimental patch, that resets the clipboard option for :g
Hi Pedro!
On So, 25 Mai 2014, Pedro Ferrari wrote:
I believe that the problem (bug?) is that the * (star) key cannot be
remapped: if I start vim with vim -N -u NONE (Vim 7.4 with patches
1-274) and run the command noremap * :echo starCR and press *,
vim tries to perform a search.
I can't
On Fri, May 30, 2014 at 9:46 AM, Christian Brabandt cbli...@256bit.org
wrote:
Hi Pedro!
On So, 25 Mai 2014, Pedro Ferrari wrote:
I believe that the problem (bug?) is that the * (star) key cannot be
remapped: if I start vim with vim -N -u NONE (Vim 7.4 with patches
1-274) and run the
Hi David!
On Fr, 30 Mai 2014, David Fishburn wrote:
When I press *, I get star written, no search performed.
So no problem for you, since you can remap *. Anybody else has that
problem?
Best,
Christian
--
Die Menschen neigen zur falschen Auffassung, daß, da sich alle unsere
mechanischen
On Friday, May 30, 2014 12:01:09 PM UTC-3, Christian Brabandt wrote:
Hi David!
On Fr, 30 Mai 2014, David Fishburn wrote:
When I press *, I get star written, no search performed.
So no problem for you, since you can remap *. Anybody else has that
problem?
Best,
On Friday, 30 May 2014 13:00:39 UTC+1, Praful wrote:
On Friday, 30 May 2014 12:27:01 UTC+1, Christian Brabandt wrote:
This is a known issue for windows (see :h todo.txt and search for
:g/test/d)
Thanks Christian - and apologies to all for not seeing the todo list
Here is an
On Fr, 30 Mai 2014, Praful wrote:
On Friday, 30 May 2014 13:00:39 UTC+1, Praful wrote:
On Friday, 30 May 2014 12:27:01 UTC+1, Christian Brabandt wrote:
This is a known issue for windows (see :h todo.txt and search for
:g/test/d)
Thanks Christian - and apologies to all for
On Fr, 30 Mai 2014, Pedro Ferrari wrote:
Hi David and Christian! Thank you for looking into this. I'm using:
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled May 2014 21:13:41)
MS-Windows 64-bit console version Included patches: 1-274
which you can get here:
On 2014-05-30, Christian Brabandt wrote:
Hi Praful!
On Do, 29 Mai 2014, Praful Kapadia wrote:
I have had an annoying issue with gvim 7.4, with patches 1-307.
If I open a large file (e.g. containing 200,000 lines) and use
the global command to delete lines, the operation takes a very
This is a preliminary implementation of matchaddpos() that requires a list
of positions. See changes in matchparen.vim as example of using it. It
works fine with the new matchparen. The implementation does not involve
regexps and redraws only part of screen. Probably i missed something or
Christian Brabandt wrote:
Hi Praful!
On Do, 29 Mai 2014, Praful Kapadia wrote:
I have had an annoying issue with gvim 7.4, with patches 1-307. If I
open a large file (e.g. containing 200,000 lines) and use the global
command to delete lines, the operation takes a very long time on
On Friday, 30 May 2014 19:31:06 UTC+1, Bram Moolenaar wrote:
I wonder if this only applies to the :g command. Doesn't :%s have the
same problem? And perhaps joining many lines. Anything that repeatedly
puts text in the register.
I just tried :%s where I substituted something on
Naofumi Honda wrote:
Recently I had experienced a segmentation fault
at the last mch_memmove() call in the function
clip_x11_convert_selection_cb() of ui.c.
This fault happens under the conditions:
*target == utf8_atom
*length == 0
enc_utf8 == false.
In fact, if
On Friday, 30 May 2014 19:31:06 UTC+1, Bram Moolenaar wrote:
I wonder if this only applies to the :g command. Doesn't :%s have the
same problem? And perhaps joining many lines. Anything that repeatedly
puts text in the register.
I should have added that joining many lines (eg
Hello,
Recently I noticed that when I set 'wildignorecase', it does not ignore case
when expanding a filename on a Xubuntu 12.04 system. (This is also reproducible
with Xubuntu 14.04)
What I tried:
1. touch ZoomTile.py archive.py
2. vim -u NONE -N -c set\ wildignorecase
3. :buffer zTAB
On Friday, May 30, 2014 7:57:55 PM UTC-7, Akshay H wrote:
Hello,
Recently I noticed that when I set 'wildignorecase', it does not ignore case
when expanding a filename on a Xubuntu 12.04 system. (This is also
reproducible with Xubuntu 14.04)
What I tried:
1. touch ZoomTile.py
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 226 by muffinpo...@gmail.com: cfg has no setting for commentstring
http://code.google.com/p/vim/issues/detail?id=226
What steps will reproduce the problem?
1. open a file which happens vim happens to pick as [cfg], ~/.hgrc
20 matches
Mail list logo
