Avoid vim eating input after quit - vim

Question

Some irritating issue when doing git commit (for example, there are other non-git scenarios): what I'd like to type (really fast):
git commit -a --amendEnter:wqEntergit push -fEnter
My problem is that after :wqEnter I have to wait until vim exits, and as I have a big vimrc it takes some time. I know, I'm spoiled.
I'm pretty sure there is a flag to git commit that will not open vim at all, but I'd prefer a more generic vim solution that will make vim not eat my input.
My vimrc is here

Answer 1

Git
While the OP wants a vim-centric solution, I offer these git workarounds as
temporary band-aids (and useful information).
At the bottom, I provide resources for discovering the issue in vim.
no-edit flag
Amending with the --no-edit flag causes vim not to launch (which is a good
idea if you do not need to edit the commit message: this is what the flag is
designed for).
Use a "different" editor for commit messages
There are a couple of different configuration options here, and a couple of
different "vims" to try.
See also git(1), section ENVIRONMENT VARIABLES, variable GIT_EDITOR.
One-off configuration
This is good for occasional usage (you can alias it, of course).
Use the -c flag on git:
git -c core.editor='vim variant' commit...
You could also set GIT_EDITOR via your shell (e.g., env, export, or
bash-isms).
Permanent configuration
This is good if you cannot resolve the vim issue and need it permanently.
Edit your configuration file (e.g., git config --edit --global), and add
[core]
editor = vim variant
Vim variants
Vim's command line switches let us control various aspects of its behavior. You
might want to
disable plugins (--noplugin)
disable a vimrc (-u NORC)
disable both (-u NONE)
use a 'clean' vim (--clean)
use a completely different vimrc for git (-u DEFAULTS or -u ~/.mygitvimrc)
The vimrc option allows us to craft an extremely efficient and minimal vimrc for
git work, while keeping our original for full-time stuff.
Experimentation may show that -N (not compatible mode) is necessary with some
of these.
Once you've chosen a setup that works, simply use vim <args>... as your git
editor, in one of the spots above.
Vim
The first things to try on the vim side are binary-split debugging your
vimrc and profiling your
vimrc to
find out what the root cause is.
It helps to be comfortable debugging for these steps. If you need to debug
vimscript, see :help debug-scripts.
Once you've identified the root cause, the next step is to squash it. You may
need to
disable a plugin (possibly to be loaded on demand)
change an autocommand to not be so nasty (look especially for autocommands
that are accidentally triggered more than once such as those not in
augroup)
avoid expensive function calls in your vimrc
help convert a heavy plugin to autoloads
or a myriad of other performance-enhancing techniques.
As always, the key is to know where the problem lies first.
For OP, using pathogen and vundle together seems like a mistake (two different runtimepath/plugin managers?). Also, vundle provides vundle#begin as a possible time-saver over vundle#rc.