On 19/03/12 05:19, skeept wrote:
On Mar 18, 11:15 pm, Tony Mechelynck
wrote:
Hi Tony,
your answer makes a lot of sense, except that I don't run hg pull
directly, I run it in a script that
also tries to get updates for other programs and scripts so I don't
get an opportunity to choose if I wan
On Mar 18, 11:15 pm, Tony Mechelynck
wrote:
Hi Tony,
your answer makes a lot of sense, except that I don't run hg pull
directly, I run it in a script that
also tries to get updates for other programs and scripts so I don't
get an opportunity to choose if I want to
discard the changes.
I added t
On 16/03/12 18:20, skeept wrote:
Hi,
I would like to know if it is possible to include
runtime/doc/tags in .hgignore?
after I build vim this file shows as modified in mercurial and then
when I try to pull again
I get some kind of error message regarding uncommited local changes.
Alternatively
On Mar 18, 2012, at 6:16 PM, "Benjamin R. Haskell" wrote:
> On Sun, 18 Mar 2012, David Fishburn wrote:
>
>> I will also add this to the YankRing plugin (script #1234).
>>
>> I don't se the patch # to put a conditional check in for it.
>
> It hasn't been applied yet, but you shouldn't check
> When I start VIM with gvim or vim -g I get an escape sequence in the
> terminal windows (esc has been replaced with ^] to show the full byte
> sequence):
Do you have a redraw in your .vimrc, or something called from there?
If so, you've struck the problem discussed in
https://groups.google.com/
On Sun, 18 Mar 2012, David Fishburn wrote:
I will also add this to the YankRing plugin (script #1234).
I don't se the patch # to put a conditional check in for it.
It hasn't been applied yet, but you shouldn't check by patch # anyway.
exists() can detect whether an autocommand for a particul
Dominique Pelle wrote:
> Using Vim-7.3.475, I can reproduce a memory leak using
> the ':rv!' command when reading dictionary or list global
> variables i.e. with 'viminfo' containing ! (:help viminfo-!).
>
> Steps to reproduce:
>
> $ cat > leak.vim < set nocp
> set viminfo+=!
>
> let FOO=[]
>
Dominique Pelle wrote:
> The conceal feature is messing up alignment when using tabs.
>
> For example, content of ":help :index" looks misaligned and ugly
> with ":set conceallevel=3" but looks well aligned with ":set conceallevel=0"
> as shows in these 2 screenshots:
>
> http://dominique.pelle
Christian Brabandt wrote:
> On Do, 15 Mär 2012, Gary Johnson wrote:
>
> > That's an odd error message, since there are no search commands in
> > that sequence, as I understood it. Using a different notation,
> > here's what I typed.
> >
> > G$A
>
> Was this ever supposed to work?
>
> An
I will also add this to the YankRing plugin (script #1234).
I don't se the patch # to put a conditional check in for it.
Could someone let me know.
Thanks.
--
David Fishburn
On Mar 16, 2012, at 1:28 AM, Philippe Vaucher
wrote:
>> Do you maybe have a yankring-like plugin that makes use
Hello,
I found a strange behaviour in the message prompt.
Here is how to reproduce it:
(1) :echo join(range(1,100), "\n")
(2) move down and up for example: jk
What happens: the first line is:
1echo join(range(1,100), "\n")
while I think it should be:
1
This becomes more confusing if the list
Hi
2012/3/15 ZyX
> Yes I would also like to see something better implemented in C
I agree with you and lilydjwg. In the long run it would be great if
extending vim with python would be just as easy and fast as using Vim
Script. I don't have any experience with Vim's codebase, so I don't know
h
number relativenumber reset bug?
I use several machines, Linux, Mac, Windows and have a vimrc that
works very for all. The versions of vim range from 6.2 to 7.3.475,
small, normal, and huge.
The only 'problem' is with number and relativenumber.
The default for the small vim is set early in vimrc
13 matches
Mail list logo