On 2008-10-05 17:44:23 -0700, Gary Johnson wrote:
> On 2008-10-05, Jorge Luis <[EMAIL PROTECTED]> wrote:
> > On 2008-10-05 17:41:36 +0200, Tony Mechelynck wrote:
> > > On 05/10/08 17:30, Jorge Luis wrote:
> > > > I use the program remind as a scheduler. At the bottom of my main
> > > > remind rc file I have:
> > > >
> > > > # vim: ft=remind:
> > > >
> > > > Entering "set" shows that the filetype is recognized as "remind" and the
> > > > syntax is colored accordingly.
> > > >
> > > > In this file I have a number of include statements that call other
> > > > files. Each of the included files has the same line at the bottom, but
> > > > none of them are colored appropriately. They, too, are
> > > > "filetype=remind" according to set.
> > > >
> > > > What am I doing wrong?
> > >
> > > Something else, I think. Maybe there is something missing at the top of
> > > the include files for the remind syntax script to recognize how to
> > > highlight them?
> >
> > It appears to have something to do with the name of the file. The name
> > of the rc file isn't enforced by remind, and include files are a very
> > common method of organizing one's memoranda, but it seems that a file
> > named .reminders picks up the syntax, while files given another name do
> > not. This even though the program has a built-in function that scans
> > for remind files named *.rem.
> >
> > There's nothing evident at the top of my include files that would fail
> > to distinguish them as remind files.
> >
> > I have looked at the syntax script for remind and didn't see anything
> > that would be overriding the usual # vim: ft=remind: tagline, but I'm
> > just starting with vim and may be missing something. If any experienced
> > vimer is willing to take a look at the syntax file for the filetype, I'd
> > appreciate it.
>
> I also use remind. I have a main ~/.reminders file that remind and
> vim recognize automatically and a ~/.remind directory containing a
> set of files such as birthdays and holidays. Those files are
> included by the ~/.reminders file. At the bottom of each one is the
> line
>
> # vim: ft=remind
>
> to tell vim the filetype. All the remind files are highlighted
> properly.
>
> I don't know what's wrong with your setup, but at least I have a
> working one that maybe we can use to get yours working.
>
> The one thing you said that really bothers me is that the 'ft' is
> "remind" in all cases. I can't fathom how filetype detection can be
> working in all cases, yet syntax highlighting works in only one
> case.
I have my files set up exactly as you do, except I named the include
files with an .rem extension. And I just discovered that the same setup
works perfectly on FreeBSD 6.2-RELEASE-p1. The trouble I'm having is on
a different machine, running Ubuntu Heron LTS. The FreeBSD box has Vim
7.0.94; the Ubuntu machine has Vim 7.1.138. However, they share the
same remind.vim syntax script.
It's very odd, and must be a quirk of the Ubuntu package, but it seems
that someone on Debian would have noticed this before and reported it.
I've found no bug listings to indicate that.
Finding the source of little quirks like this is like tracking down
electrical problems with a Lucas ignition system: it goes on forever. I
suppose it's one of those things I'll have to live with.
I'll file a bug with Ubuntu.
Thanks for your help,
JL
--
JL <[EMAIL PROTECTED]>
This message optimized for teletypes.
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
