On Wed, Oct 28, 2015 at 2:40 AM, Brenton Horne <[email protected]> wrote:
> Hi,
>
> I have installed the vim-mediawiki-editor plugin and added:
>
> <pre>
> g:mediawiki_editor_url 'en.wikipedia.org'
> g:mediawiki_editor_path '/w/'
> </pre>
>
> to the end of ~/.vimrc. I also tried adding this line right after:
>
> <pre>
> Plugin 'aquach/vim-mediawiki-editor'
> </pre>
>
> and before:
>
> <pre>
> call vundle#end() " required
> filetype plugin indent on " required
> </pre>
>
> but I got the error:
>
> <pre>
> Pattern not found: mediawiki_editor_url 'en.wikipedia.org'
> Pattern not found: mediawiki_editor_path '/w/'
> </pre>
>
> Thanks for your time,
> Brenton
Each "line" of the vimrc (including any continuation lines, which
start by zero or more whitespace characters then a backslash, and are
regarded as joined to the previous line) constitutes an ex-command,
similar to the command you could type on the command-line after
hitting : (colon) in Normal mode.
I don't know the vim_mediawiki_editor plugin but I suspect that your
first example between <pre> and </pre> is supposed to set
configuration variables for this plugin. BTW the vimrc is not in HTML
and it should not contain <pre> </pre> itself.
To set variables in the vimrc, you would use the :let command (see
":help :let" without the quotes), for instance
let g:mediawiki_editor_url = 'http://en.wikipedia.org/'
let g:mediawiki_editor_path = '/w/'
see also :help eval.txt
If the plugin is a global plugin, it should be dropped in the
./plugin/ subdirectory of one of the directories mentioned in the
'runtimepath' option, for instance in ~/.vim/plugin (Unix/Linux) or in
~/vimfiles/plugin (Windows, as seen by Vim) or in
%HOME%\vimfiles\plugin (Windows, as seen by command.exe or by the
window manager). It should also have a filename ending in .vim
filetype plugin indent on
is correct; or you may want to replace it (near the start of your vimrc) by
runtime vimrc_example.vim
which sets a lot of useful settings — unless your vimrc is a frozen
copy of what the vimrc_example.vim used to be the first time you
installed Vim, which some people recommend but I definitely don't. If
anything set by the vimrc_example.vim displeases you you can always
change it afterwards. For instance, I don't like filetype-dependent
autoindenting so my vimrc includes
runtime vimrc_example.vim
filetype indent off
The advantage of sourcing it (with :runtime, q.v.) rather than copying
it is that this way I always enjoy the latest version.
I don't know when you want the function vundle#end() to be called. If
you place that call in your vimrc as you did, it will be called at the
very beginning of Vim startup, even before the plugins have been
sourced. If that's what you want, then it's OK. If you want to call it
at a different time, then it must be invoked some other way, but since
I don't know what it is supposed to do, I cannot guess.
Best regards,
Tony.
--
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
