[Vimoutliner] My VO does not work anymore

[Steve Litt]

On Monday 10 December 2007 11:33, Steve Litt wrote:
> On Monday 10 December 2007 06:59, on_ wrote:
> > Hi there,
> >
> > I'm new here. I use GVim and VimOutline for my work. I only use basic
> > features of them. I'm runing it under Ubuntu 7.10. And 'till now
> > everything was fine.
> >
> > Last time I use VO, I worked on a big outline a month ago... Today, I
> > tried to open this .otl file, GVim opened it but without VO. I tried to
> > open other .otl files, from within GVim, by double-clicking them
> > directly in Nautilus and at the commandline. Nothing worked. I
> > unsinstalled and reinstalled VO. ... ... Worst, I figured out that my
> > GVim does not include VO anymore, as ":he vimoutliner" returned an E149
> > errorcode.
> >
> > Could you help me bringing VO back to live on my system?
> >
> > Thanks in advance,
> >
> > on_
>
> Hi On_,
>
> First, be assured that your content is still completely intact. Next, be
> assured that this is easy to fix.
>
> It's been fixed many times, but unfortunately I keep forgetting the fix.
> However, let me try to remember the steps...
>
> First, with the file open in vim/gvim, issue this colon command:
> :set filetype=vo_base
>
> One of three things will happen:
>
> 1) It will act just like a VO outline
> 2) It will act partially like a VO outline
> 3) It won't act like a VO outline
>
> In order to see which of the three applies, evaluate the following:
> 1) Do different levels have different colors?
> 2) Do trees expand and collapse?
> 3) Do ,,1 and ,,9 work collapse to level 0 and expand to level 8?
> 4) Does body text work?
> 5) Does interoutline linking work?
>
> Note that with #5, when you come back to the original outline it may no
> longer perform like VO, in which case you'll need to do :set
> filetype=vo_base again.
>
> If it acts completely like VO, the problem is probably that either you
> don't have the filetype listed in the ~/.vim/ftdetect directory. If it is
> listed there, for some reason that directory isn't searched, and I defer to
> Noel as to what diagnostic steps you'd perform from there.
>
> Noel -- we need to write a predefined diagnostic and put it on the website.
> I'll help write it, but I'll need some help on what does what.
>
> The first part of the predefined diagnostic should be Vim's startup
> procedures -- what files does it parse in what order. The second part
> should be a diagnostic tree. This stuff is so obscure that every time it
> comes up I have to relearn it.
>
> Thanks
>
> SteveT

Hi On_,

As an ultra-quick diagnostic test, please put the following file, called 
my_vo_extensions.vim, in your ~/.vim/ftdetect directory:

augroup filetypedetect
  au! BufRead,BufNewFile *.emdl         setfiletype vo_base
  au! BufRead,BufNewFile *.ebdl         setfiletype vo_base
  au! BufRead,BufNewFile *.pho          setfiletype vo_base
  au! BufRead,BufNewFile *.rl           setfiletype vo_base
augroup END

Then edit a file called junk.emdl, see whether it acts like an outline, and 
report back to us.

Thanks

SteveT