Press ENTER or type command to continue problem at every vim startup

[Jean-Marcel Belmont]

Hello I am using vim 7.4 beta with patches (1-39). I am using Mac OS X 10.7
Everytime I open vim now I get the prompt:
Press ENTER or type command to continue
In my vimrc I have the following:
set equalalways
set history=200
set autoread
set tw=75
set so=7
set wrapmargin
set nocompatible
" powerline status bar
set laststatus=2
set encoding=utf-8
set wildmenu
set ruler
set tabstop=2
set shiftwidth=2
set expandtab
set softtabstop=2
set cmdheight=1
set hid
set backspace=eol,start,indent
set shiftround
set ignorecase
set nobackup
set autoindent smartindent
set nowb
set magic
set showmatch
set noswapfile
set viminfo='20,\"50
set number
set wildmode=longest:full,full
set wildmenu
set noerrorbells
set incsearch
set hlsearch
I also have additional options set in vimrc but they are for map leader bindings and plugin options as well. I have tried the suggestions in the vim wiki about set shortmess=a, I tried shortmess=at, set cmdheight=2, but these are
refer to the Press ENTER or type command to continue when you issue an external command such as !ls in vim command window. My problem is that I get
Press ENTER to type command to continue in each and every vim startup option.
Does anyone know how to solve this issue. Any suggestions would be greatly appreciated.

Sincerely,

Jean-Marcel Belmont

[Ben Fritz]

On Monday, July 29, 2013 1:52:22 PM UTC-5, Jean-Marcel Belmont wrote:
> I have tried the suggestions in the vim wiki about set shortmess=a, I tried shortmess=at, set cmdheight=2, but these are
> refer to the Press ENTER or type command to continue when you issue an external command such as !ls in vim command window.

I assume you mean:

http://vim.wikia.com/wiki/Avoiding_the_%22Hit_ENTER_to_continue%22_prompts

Actually the only suggestion on that page regarding external commands is that you can use :silent before the command. The rest is about situations where there is something printed to the screen inside Vim which the user must read.

> My problem is that I get
> Press ENTER to type command to continue in each and every vim startup option.
> Does anyone know how to solve this issue.

Are there other messages that show up before the "press enter" prompt? You can search your plugins for these messages to figure out how to disable them. Or set you cmdheight option big enough to show them all at startup.

[Jean-Marcel Belmont]

Hello Ben:

I tried to set cmdheight=15 just to see if any messages, but none came. Also I tried vim -u NONE -U NONE and the message "Press ENTER or type command" didn't not show. You suggested to search plugins, how should I go about this, should I use grep for the phrase "Press ENTER or type command" on my plugins, or should I read all help files for all my plugins for this problem.

--
--
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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Gary Johnson]

On 2013-07-29, Jean-Marcel Belmont wrote:

> On Mon, Jul 29, 2013 at 5:20 PM, Ben Fritz wrote:
>
> On Monday, July 29, 2013 1:52:22 PM UTC-5, Jean-Marcel Belmont wrote:
> > I have tried the suggestions in the vim wiki about set shortmess=a, I
> > tried shortmess=at, set cmdheight=2, but these are
> > refer to the Press ENTER or type command to continue when you issue an
> > external command such as !ls in vim command window.
>
> I assume you mean:
>
> http://vim.wikia.com/wiki/Avoiding_the_%22Hit_ENTER_to_continue%22_prompts
>
> Actually the only suggestion on that page regarding external commands is
> that you can use :silent before the command. The rest is about situations
> where there is something printed to the screen inside Vim which the user
> must read.
>
> > My problem is that I get
> > Press ENTER to type command to continue in each and every vim startup
> > option.
> > Does anyone know how to solve this issue.
>
> Are there other messages that show up before the "press enter" prompt? You
> can search your plugins for these messages to figure out how to disable
> them. Or set you cmdheight option big enough to show them all at startup.

> Hello Ben:
>
> I tried to set cmdheight=15 just to see if any messages, but none came. Also I
> tried vim -u NONE -U NONE and the message "Press ENTER or type command" didn't
> not show. You suggested to search plugins, how should I go about this, should I
> use grep for the phrase "Press ENTER or type command" on my plugins, or should
> I read all help files for all my plugins for this problem.

The message, "Press ENTER or type command to continue" is generated
by Vim itself. It is not generated by plugins and the string is
unlikely to be found in any plugin.

Discussion of this issue is also not likely to be found in the help
file for any plugin. If the message is part of the normal behavior
of a plugin, then that normal behavior would be adequately described
in ":help press-enter". If the message is due to a bug in the
plugin, then the author is probably not aware of it.

Lacking any message preceding the "Press ENTER" message, about the
only way to isolate this to a particular plugin is to do a binary
search of your plugins. If you're not sure how to do that, the
following algorithm should work.

1. Create two directories, ~/unknown and ~/good.
2. Move half the files in ~/.vim/plugin to ~/unknown.
3. Run your test, which in this case is to execute vim and
watch for the "Press ENTER" message. If the message is
there, the result is "bad"; otherwise, the result is "good".
4. If "good":
a) Move all the files in plugin to ~/good.
b) Move half the files in ~/unknown to plugin.
If "bad":
a) Move all the files in ~/unknown to ~/good.
b) Move half the files in plugin to ~/unknown.
5. Repeat from step 3 until one bad file remains in plugin.

The convention in this group is to not top-post. I have reformatted
your reply accordingly.

Regards,
Gary

[Jean-Marcel Belmont]

Okay great thanks for your help. I will try this binary search as you have suggested.