Mail Archives: cygwin/2009/04/02/14:19:36
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to Corinna Vinschen on 4/2/2009 9:53 AM:
> I then puzzled out that on the machine where vim is fast, the filetype
> of the strace file was set to "", while on the incredible slow machine,
> vim had set the filetype to "asciidoc".
Did you, per chance, name your strace with a .txt suffix? If not, how did
it match the vim file content detection? Looking at
/usr/share/vim/vimfiles/ftdetect/asciidoc_filetype.vim, I see:
> " COMMENT OUT ONE OF THE TWO FOLLOWING COMMANDS
> " The first sets asciidoc syntax highlighting on all .txt files, the second
> " only existing files *.txt that appear to be AsciiDoc files.
>
> au BufNewFile,BufRead *.txt,README,TODO,CHANGELOG,NOTES setfiletype asciidoc
> "au BufRead *.txt,README,TODO,CHANGELOG,NOTES call s:FTasciidoc()
Does switching the comment help? I don't use vim, so I'm not really in a
position to test this (I just bundle the vim bindings with asciidoc
because they are available upstream, and my only personal use of asciidoc
is indirectly as the git maintainer). But if it helps, then I'll roll a
- -2 with that comment swapped over.
>
> - The longer the strace file, the slower vim gets. Incidentally
> strace files tend to be rather huge.
>
> - There seem to be a bug in one or more of the regular expressions in
> the asciidoc.vim syntax file.
Well, they are expecting to match asciidoc syntax, which strace does not.
But I can forward that concern upstream.
- --
Don't work too hard, make some time for fun as well!
Eric Blake ebb9 AT byu DOT net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAknVD6YACgkQ84KuGfSFAYDlCQCgmEWEZu4cicTt7X/UZrQh0O/T
00EAn3mJxxpC/n45KLtD+D+yVjdFsTmy
=r1Ji
-----END PGP SIGNATURE-----
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -