snipMate not working - vim_use

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion snipMate not working
Received-SPF: neutral (google.com: 209.85.215.54 is neither permitted nor denied by best guess record for domain of ke...@teamprema.co.nz) client-ip=209.85.215.54;
MIME-Version: 1.0
In-Reply-To: <20121008150336.GA4374@phoenix>
References: <4daad6e7-11f5-4363-8f66-d14f11ba25e9@googlegroups.com>
 <20121003154906.GA23694@phoenix> <c1e6fa90-0c50-4788-a6a6-1c48e37961eb@googlegroups.com>
 <20121008063411.GC3697@phoenix> <c97968b0-361c-4d45-a3c1-af8cb368c8e7@googlegroups.com>
 <20121008150336.GA4374@phoenix>
From: Matt Keir <ke...@teamprema.co.nz>
Date: Tue, 16 Oct 2012 01:01:26 +1300
Message-ID: <CANYKVeMpcX4Qz=0CQ4fL0n+8o+4=xGaUu3Ze0EaAM88jQfG...@mail.gmail.com>
Subject: Re: snipMate not working
To: vim_use@googlegroups.com
Content-Type: multipart/alternative; boundary=f46d040714a742ccaf04cc17cdb9

--f46d040714a742ccaf04cc17cdb9
Content-Type: text/plain; charset=ISO-8859-1

Hi Gary

Took your advice and RTFM'D ;-)

Had a look in usr/share/vim/vimrc

'set compatible' was uncommented in there. Not a default setting it seems.
Must have come over from my colleagues PC when we copied Vim over

So when I put 'nocompatible' in .vimrc it over rode this and snipmate worked

funny thing is it didn't work a few days later when I tried to use it again.

So removed nocompatible from .vimrc and commented out set compatible
in usr/share/vim/vimrc and now snipmate works again :)

Thanks for your help


On Tue, Oct 9, 2012 at 4:03 AM, Gary Johnson <garyj...@spocom.com> wrote:

> On 2012-10-08, Mashan wrote:
> > Thanks Gary / Marc / Charles
> >
> > Turns out putting "set nocompatible" into the .vimrc file did the
> > trick (Thanks Marc)
>
> I'm glad that problem has been fixed, but I would be wary of that
> solution for two reasons.  First, it shouldn't be necessary.  As
> ":help 'compatible' explains,
>
>         When a |vimrc| or |gvimrc| file is found while Vim is
>         starting up, this option is switched off, and all options
>         that have not been modified will be set to the Vim defaults.
>
> So, 'nocompatible' should already have been set by the time your
> ~/.vimrc was read.
>
> Secondly, again from ":help 'compatible',
>
>         This is a special kind of option, because when it's set or
>         reset, other options are also changed as a side effect.
>         CAREFUL: Setting or resetting this option can have a lot of
>         unexpected effects: Mappings are interpreted in another way,
>         undo behaves differently, etc.  If you set this option in
>         your vimrc file, you should probably put it at the very
>         start.
>
> By putting "set nocompatible" into your ~/.vimrc where you did,
> you've thrown a monkey wrench into your initialization process.
> While it did have the effect of fixing this problem, it may well
> have caused other problems that you haven't discovered yet.
>
> Since: a) this fixes this problem; b) hasn't had any bad
> side-effects yet; and c) I don't know what the real solution is; I'd
> leave your ~/.vimrc as-is.  Just be aware that this is a flaky
> solution, may cause other problems, and removing it should be one of
> the first things you do if you have problems in the future.
>
> > This worked on it's own without any of the "filetype" settings,
> > though as you'll see below I put them in anyway as I had heard
> > they were important (possible for other reasons ?)
>
> The ":filetype ident plugin on" and ":syntax on" commands were
> already executed in your /usr/share/vim/vimrc file.  That's why you
> didn't need to set them in your ~/.vimrc file.  That can be seen in
> the output of :scriptnames that you posted earlier.
>
> > Thanks again for everyone's help
> >
> > Much appreciated
> >
> > contents of .vimrc file :
> >
> > set ts=4
> > set ai
> > set shiftwidth=4
> > syn on
> > set mouse=a
> > au BufRead,BufNewFile jquery.*.js set ft=javascript syntax=jquery
> > color evening
> > filetype on
> > set tabpagemax=25
> > set smartindent
> > set showmatch
> > set vb t_vb=
> > set ruler
> > set incsearch
> > set nocompatible
> > au BufRead,BufNewFile *.php set ft=php.html
> > filetype plugin on
> > filetype indent plugin on | syn on
>
> Regards,
> Gary
>
> --
> 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
>

--f46d040714a742ccaf04cc17cdb9
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Gary<div><br></div><div>Took your advice and RTFM&#39;D ;-)</div><div><b=
r></div><div>Had a look in usr/share/vim/vimrc</div><div><br></div><div>&#3=
9;set compatible&#39; was uncommented in there. Not a default setting it se=
ems. Must have come over from my colleagues PC when we copied Vim over</div=
>

<div><br></div><div>So when I put &#39;nocompatible&#39; in .vimrc it over =
rode this and snipmate worked</div><div><br></div><div>funny thing is it di=
dn&#39;t work a few days later when I tried to use it again.</div><div>

<br></div><div>So removed nocompatible from .vimrc and commented out set co=
mpatible in=A0usr/share/vim/vimrc and now snipmate works again :)</div><div=
><br></div><div>Thanks for your help</div><div><br><br><div class=3D"gmail_=
quote">

On Tue, Oct 9, 2012 at 4:03 AM, Gary Johnson <span dir=3D"ltr">&lt;<a href=
=3D"mailto:garyj...@spocom.com" target=3D"_blank">garyj...@spocom.com</a>&g=
t;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<div class=3D"im">On 2012-10-08, Mashan wrote:<br>
&gt; Thanks Gary / Marc / Charles<br>
&gt;<br>
&gt; Turns out putting &quot;set nocompatible&quot; into the .vimrc file di=
d the<br>
&gt; trick (Thanks Marc)<br>
<br>
</div>I&#39;m glad that problem has been fixed, but I would be wary of that=
<br>
solution for two reasons. =A0First, it shouldn&#39;t be necessary. =A0As<br=
>
&quot;:help &#39;compatible&#39; explains,<br>
<br>
=A0 =A0 =A0 =A0 When a |vimrc| or |gvimrc| file is found while Vim is<br>
=A0 =A0 =A0 =A0 starting up, this option is switched off, and all options<b=
r>
=A0 =A0 =A0 =A0 that have not been modified will be set to the Vim defaults=
.<br>
<br>
So, &#39;nocompatible&#39; should already have been set by the time your<br=
>
~/.vimrc was read.<br>
<br>
Secondly, again from &quot;:help &#39;compatible&#39;,<br>
<br>
=A0 =A0 =A0 =A0 This is a special kind of option, because when it&#39;s set=
 or<br>
=A0 =A0 =A0 =A0 reset, other options are also changed as a side effect.<br>
=A0 =A0 =A0 =A0 CAREFUL: Setting or resetting this option can have a lot of=
<br>
=A0 =A0 =A0 =A0 unexpected effects: Mappings are interpreted in another way=
,<br>
=A0 =A0 =A0 =A0 undo behaves differently, etc. =A0If you set this option in=
<br>
=A0 =A0 =A0 =A0 your vimrc file, you should probably put it at the very<br>
=A0 =A0 =A0 =A0 start.<br>
<br>
By putting &quot;set nocompatible&quot; into your ~/.vimrc where you did,<b=
r>
you&#39;ve thrown a monkey wrench into your initialization process.<br>
While it did have the effect of fixing this problem, it may well<br>
have caused other problems that you haven&#39;t discovered yet.<br>
<br>
Since: a) this fixes this problem; b) hasn&#39;t had any bad<br>
side-effects yet; and c) I don&#39;t know what the real solution is; I&#39;=
d<br>
leave your ~/.vimrc as-is. =A0Just be aware that this is a flaky<br>
solution, may cause other problems, and removing it should be one of<br>
the first things you do if you have problems in the future.<br>
<div class=3D"im"><br>
&gt; This worked on it&#39;s own without any of the &quot;filetype&quot; se=
ttings,<br>
&gt; though as you&#39;ll see below I put them in anyway as I had heard<br>
&gt; they were important (possible for other reasons ?)<br>
<br>
</div>The &quot;:filetype ident plugin on&quot; and &quot;:syntax on&quot; =
commands were<br>
already executed in your /usr/share/vim/vimrc file. =A0That&#39;s why you<b=
r>
didn&#39;t need to set them in your ~/.vimrc file. =A0That can be seen in<b=
r>
the output of :scriptnames that you posted earlier.<br>
<div class=3D"im HOEnZb"><br>
&gt; Thanks again for everyone&#39;s help<br>
&gt;<br>
&gt; Much appreciated<br>
&gt;<br>
&gt; contents of .vimrc file :<br>
&gt;<br>
&gt; set ts=3D4<br>
&gt; set ai<br>
&gt; set shiftwidth=3D4<br>
&gt; syn on<br>
&gt; set mouse=3Da<br>
&gt; au BufRead,BufNewFile jquery.*.js set ft=3Djavascript syntax=3Djquery<=
br>
&gt; color evening<br>
&gt; filetype on<br>
&gt; set tabpagemax=3D25<br>
&gt; set smartindent<br>
&gt; set showmatch<br>
&gt; set vb t_vb=3D<br>
&gt; set ruler<br>
&gt; set incsearch<br>
&gt; set nocompatible<br>
&gt; au BufRead,BufNewFile *.php set ft=3Dphp.html<br>
&gt; filetype plugin on<br>
&gt; filetype indent plugin on | syn on<br>
<br>
</div><div class=3D"HOEnZb"><div class=3D"h5">Regards,<br>
Gary<br>
<br>
--<br>
You received this message from the &quot;vim_use&quot; maillist.<br>
Do not top-post! Type your reply below the text you are replying to.<br>
For more information, visit <a href=3D"http://www.vim.org/maillist.php" tar=
get=3D"_blank">http://www.vim.org/maillist.php</a><br>
</div></div></blockquote></div><br></div>

--f46d040714a742ccaf04cc17cdb9--
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
