On 13.03.12,05:46, Tim Chase wrote:
> On 03/13/12 05:07, Jostein Berntsen wrote:
> but it is what it is.
> 
> >2. When I use copen in an already horizontally split window it comes up
> >at the bottom end of the screen as it should. I have set splitright and
> >splitbelow in my .vimrc. But if I edit the original file and then do copen,
> >often it will overtake all the windows. Why is that? This happens also when
> >opening a link in the original file.
> 
> Starting a naked Vim ("vim -u NONE") could you give a sequence of
> settings & commands that reproduce this, and what you expect to be
> different?  I think if it's easily reproducible, you'll get better
> answers.  I'd expect it to look something like
> 
>   vim -u NONE file1.txt
>   :set splitright splitbelow nocp
>   (some action to populate the quickfix window such as :vimgrep)
>   :copen
>   (some other sequence of actions)
>   :copen
>   (description of the unexpected)

copen works as expected with vim -u NONE, so I guess I must check out my
plugins and .vimrc settings.
> 
> 
> >3. Sometimes vim hangs a bit when I try to go to insert mode and it then
> >enters a lot of the same character instead the one I would like to enter.
> 
> This sounds suspiciously like you've prefixed your insertion with a
> count.  If you type
> 
>   10iX<esc>
> 
> it will insert 10 "X" characters.  If you type multiple characters,
> does it repeat those too, such as
> 
>   10iABC<esc>
> 
> inserting "ABCABCABCABCABCABCABCABCABCABC"?
> 
> Alternatively you could have some strange mapping (depending on the
> length of the "hangs a bit", if it happens to be 'timeoutlen'
> milliseconds) that's getting triggered.  Or perhaps it's an
> abbreviation that's expanding.  The output of ":imap" and ":ab" and
> ":iab" would be helpful in this case.

Thanks. I think I found some iab mappings that might be the culprit. Will
remove those and these some more. 


Jostein

-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Reply via email to