| Computers Forum Index » Computer - Editors » How can I diagnose Vim startup errors?... |
|
Page 1 of 1 |
|
| Author |
Message |
| markscottwright... |
 Posted: Mon Oct 05, 2009 4:02 pm |
|
|
|
Guest
|
I've transferred my vimrc from my PC to my Linux box recently, and
there's some sort of error that occurs on startup now. Sadly, the
only indication that something is wrong is that gvim prompts me to
"Press ENTER or type command to continue" on startup (console vim
seems fine).
Is there a way to get more verbose info when starting vim? Is there a
way to get better error info? |
|
|
| Back to top |
|
|
|
| Florian Rehnisch... |
| Posted: Mon Oct 05, 2009 5:33 pm |
|
|
|
Guest
|
o markscottwright <markscottwright at (no spam) gmail.com>:
Quote: I've transferred my vimrc from my PC to my Linux box recently, and
Whut duz PC mean? Can be anything from Amiga across Windows to
main frame.
dos vs unix?
--
flori
Vim-Hilfe auf Deutsch http://www.florianrehnisch.de/vimhelp/ |
|
|
| Back to top |
|
|
|
| Gary Johnson... |
| Posted: Mon Oct 05, 2009 8:41 pm |
|
|
|
Guest
|
markscottwright <markscottwright at (no spam) gmail.com> wrote:
Quote: I've transferred my vimrc from my PC to my Linux box recently, and
there's some sort of error that occurs on startup now. Sadly, the
only indication that something is wrong is that gvim prompts me to
"Press ENTER or type command to continue" on startup (console vim
seems fine).
Is there a way to get more verbose info when starting vim? Is there a
way to get better error info?
If there were any error messages, you can see them again by executing
:messages
You can start vim and gvim in a 'verbose' mode with various levels of
verbosity and optionally capture the output to a file. See
:help verbose
--
Gary Johnson |
|
|
| Back to top |
|
|
|
|
