On Thu, 2006-09-07 at 10:19 -0400, Charles E Campbell Jr wrote:
> scott wrote:
> >ok, so help me out here
> >
> >i've looked at filetype vim, and i see nothing that associates
> >_.txt modules with ft=txt
> >
> >whether i enter my 'ai' modules with the script or by navigating
> >to where they are and, with my bloody fingers typing 'gvim
> >ai_200609.txt', still, inside the module, filetype is undefined
> >
> >are we only supposed to use vim for exotic languages?
> >
> >is 'text' deprecated?
> >
> >i thought it used to suffice to have an extension of .txt
> >
> >now the ground is shifting under my feet...
>
> ---------------------------------------------------------------------
>
> scott wrote again:
> >excuse me
> >
> >this transcends ridiculous
> >
> >i am editing text, and i have gone around the bend to tell vim
> >that i am doing so
> >
> >to have to create an entire "text" syntax, where NOTHING HAPPENS,
> >seems against every premise that vim was built on
> >
> >why do i have to be surprised by 'cindent' when i am editing text?
> >it is, after all, text, and i went out of my way to define these
> >modules with the .txt extension, even here in linux -- specifically
> >so he'd know
> >
> >why would cindent kick in if i'm not editing c?
> >
> >now you say *.txt is associated with nothing -- that goes far to
> >explain why my search in filetype.vim for 'txt' was so fruitless,
> >thank you
> >
> >i don't remember having this problem before -- before what exactly
> >i'm not sure -- but i've been surprised with indenting behavior enough
> >to go out of my way to turn every indenting feature off i can find,
> >but still i get surprises
> >
> >now cindent is off, maybe i can still work...tab is easy to hit...
> >
> >forgive me, i have no bottom line -- no idea what i'm saying --
> >i'll shutup now
>
> Yep, nothing associates *.txt modules with ft=txt. That's because there
> is no syntax/txt.vim highlighting, at least as distributed. What
> highlighting should be done for a non-specific, arbitrary language?
> Keywords? Regions? Or did you intend to mean that you used a .txt
> suffix to avoid syntax highlighting, filetype plugins, etc?
>
> To answer your question about cindent -- are you sure you're not setting
> it yourself in your .vimrc? To find out where it was last set:
>
> :verbose set cin?
>
> There's also autoindent (short form: ai). If that's on, to find out
> where it was last set:
>
> :verbose set ai?
>
> Perhaps you can either remove these settings from your .vimrc if that's
> where they're set or remove any plugins that are setting them.
>
> What do you mean by "entering your ai modules with the script"?
>
> Chip Campbell
>
it is irrelevant to my rant, but i'm glad to share -- it's a simple
one line bash executable on my bin path that gets me into the current
'ai' module (think "action items"):
#!/bin/bash
gvim -S ~/bin/ai.vim
and then ai.vim sets up the name:
let s:name = '~/documents/txt/ai_' . strftime("%Y%m") . '.txt'
execute "e +" s:name
since i was editing ai_200609.txt having used this process, i felt
obliged, in the interest of full disclosure, to mention it in the
context of why filetype might not be set
my 'ai' modules and vim's autoindent feature are related only in
that they share a name
for homework i am assigning myself the research of as many flavors
of indenting as i can find -- my first objective will be to
find out exactly how many options are being set with the command
:set filtype plugin indent
