Hey, thanks for getting back to me. Answers inline.
On Apr 23, 5:18 pm, Charles Campbell <[email protected]> wrote: > Kablooie!! wrote: > > Hey all, > > > This is probably a newbie question, but I've done some searching > > around and documentation reading and I just can't seem to get it > > working. > > > The problem is that I've got a fresh install of cygwin, which includes > > vim 7.2. I'm "pretty" sure that includes the appropriate version of > > netrw module. But when I try: > > > vim scp://machine_name//path/to/file > > > Vim comes up with "~/scp:/machine_name:/path/to_file" [New DIRECTORY]" > > in the bottom of the window. > > > It looks to me like the netrw module isn't being called in this case. > > > Thinking I may have messed something up in my .inputrc, .vimrc, > > or .vim directry, I moved them all aside to "test.inputrc", etc. > > Hello! > > Please bring up vim and try > > :scriptnames > > Does netrw show on that list? Alternatively, type Yep, it does: ... 12: /usr/share/vim/vim72/plugin/netrwPlugin.vim > > :echo g:loaded_netrwPlugin > :echo g:loaded_netrw > > If the first one gives an error message about an undefined variable, > then netrw's plugin/ script hasn't been loaded. If the second one gives > an error message, then netrw's autoload/ script hasn't been loaded yet. > The latter one isn't loaded until its asked for, though (via a command > that invokes it, such as :e .). The first one showed "v136" in the bottom. The second one gave me this: E121: Undefined variable: g:loaded_netrw E15: Invalid expression: g:loaded_netrw And as you suggested above, I ran ":e ." and then re-ran the ":echo g:loaded_netrw" command and got: v136 at the bottom Hmm, does that mean now that it's loaded, I can use it? Testing... Yes! I can read a file into the current buffer via: :r scp://machine//path/to/file Now, how can I make it autoload the netrw module so that I can do it from a cygwin command-line like this: $ vi scp://machine//path/to/file am I missing some environment variable? Is there a chance that vim isn't reading my .vimrc before it tries to open the file specified on the command-line? Thanks for any help. Grant > > Do you have > > filetype plugin on > > in your .vimrc? This command enables plugins (and if you also want > indent scripts, then you might prefer filetype plugin indent on). Yes, I have this at the beginning of my .vimrc: " Trying to get netrw working set nocp filetype plugin on > > Regards, > Chip Campbell > > -- > 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, visithttp://www.vim.org/maillist.php > > Subscription settings:http://groups.google.com/group/vim_use/subscribe?hl=en -- 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
