Re: capture to file output of :set all?

2012-11-19 Thread Erik
This is quite bizarre. Seems like pretty much any command I enter (including :mkvimrc) does nothing. Instead of getting output or the intended effect on the text, the command just stays visible. I did have a .vimrc file with some settings; removed it for troubleshooting but it made no

Re: capture to file output of :set all?

2012-11-17 Thread Salman Halim
On Saturday, November 17, 2012, Erik wrote: I'm trying to troubleshoot why vim is behaving differently on different systems, and it would be really handy if i could dump all the settings to a text file for comparison. What's the recommended way of doing that? Or, alternatively, how can i see

Re: capture to file output of :set all?

2012-11-17 Thread Erik
Thanks, but: :help :redir E433: No tags file E149: Sorry, no help for :redir # yum install vim-common :help :redir E434: Can't find tag pattern Found help here: http://vim.wikia.com/wiki/Capture_ex_command_output Then got: E475: Invalid argument: @a Tried the alternate route in the

RE: capture to file output of :set all?

2012-11-17 Thread John Beckett
Erik wrote: Thanks, but: :help :redir E433: No tags file E149: Sorry, no help for :redir If your help was working, you could use: :help :helptags to see: To rebuild the help tags in the runtime directory (requires write permission there): :helptags $VIMRUNTIME/doc

Re: capture to file output of :set all?

2012-11-17 Thread Ben Fritz
On Saturday, November 17, 2012 3:22:06 PM UTC-6, Erik wrote: I'm trying to troubleshoot why vim is behaving differently on different systems, and it would be really handy if i could dump all the settings to a text file for comparison. What's the recommended way of doing that? Or,