On Fri, 30 Sep 2011, Lex Trotman wrote:
On 30 September 2011 06:24, Dag Wieers <[email protected]> wrote:
Can we add .asciidoc support to vim's ftdetect (as shipped with AsciiDoc).
Since this is now the default extension for eg. AsciiDoc README files in
Github, we might as well make sure vim does color-highlighting automatically
for Github users.
The lines at the top of ftdetect/asciidoc_filetype.vim needs to be changed
to add *.asciidoc:
----
au BufNewFile,BufRead *.asciidoc,*.txt,README,TODO,CHANGELOG,NOTES
 setfiletype asciidoc
"au BufRead *.asciidoc,*.txt,README,TODO,CHANGELOG,NOTES call s:FTasciidoc()
----
Not sure if adding .adoc is ok, since it's not considered a standard (I
personally hate .asciidoc as it is too long to my taste).
I agree about .asciidoc, but I don't think there is a choice when you
want a unique association between an extension and the asciidoc
filetype. Other obvious options like asc and adoc are already used
for other applications.
txt is too generic to be uniquely associated with asciidoc.
asc is abobe flash actionscript or GPG signing keys.
adoc is an old MS word format file and a signed/encrypted XML document format
asdoc is a documentation tool used with flash
and once you get to that point you might as well go all the way to asciidoc :)
I agree, although we could use s:FTasciidoc() for everything that is not
uniquely AsciiDoc (eg. .adoc and .txt). That said, there's probably a good
reason why that is not activated today.
--
-- dag wieers, [email protected], http://dag.wieers.com/
-- dagit linux solutions, [email protected], http://dagit.net/
[Any errors in spelling, tact or fact are transmission errors]
--
You received this message because you are subscribed to the Google Groups
"asciidoc" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/asciidoc?hl=en.
