On Apr 2, 2:15 pm, Charles Campbell <Charles.E.Campb...@nasa.gov>
wrote:
> Tony Mechelynck wrote:
>> Vim's system files should be in c:/Program Files (x86)/Vim/vim73/ aka
>> $VIMRUNTIME -- c:/Program Files (x86)/Vim/vimfiles/ is $VIM/vimfiles/
>> which is where system-wide Vim "full-fledged script" customizations are
>> kept.
>
> Thank you, Tony -- I was going to check on that later when I have access
> to a Windows box.
Tony, Charles, you seem to be the gray beards here!
Thanks for the clarification. I did indeed try unpacking netrw v.147
to both locations and confirmed that they were in each. I also
confirmed that all files & directories were read/execute/accessible to
all and that they were not user-specific virtual instantiations (a
Windows 7 feature). In both cases, I got the same behaviour i.e. when
I edited a directory, I got what appeared to be an empty file.
On a separate matter, even if I got netrw 147 working on the computer
for which I have admin privileges, it would not be a solution for the
copying of marked files by the Windows-based gvim on the locked down
computer (which is where I will be spending most of my time). There
are barriers to getting anything installed there. Is there another
avenue I can pursue for that scenario?
--
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Tuesday, April 2, 2013
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment