[llvm-commits] [llvm] r62719 - /llvm/trunk/utils/vim/README
Dan Gohman
gohman at apple.com
Wed Jan 21 13:52:42 PST 2009
Author: djg
Date: Wed Jan 21 15:52:42 2009
New Revision: 62719
URL: http://llvm.org/viewvc/llvm-project?rev=62719&view=rev
Log:
Versions of VIM included with Intrepid and Leopard at least appear
to handle symlinks just fine, so reword the instructions in the
README accordingly.
Modified:
llvm/trunk/utils/vim/README
Modified: llvm/trunk/utils/vim/README
URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/utils/vim/README?rev=62719&r1=62718&r2=62719&view=diff
==============================================================================
--- llvm/trunk/utils/vim/README (original)
+++ llvm/trunk/utils/vim/README Wed Jan 21 15:52:42 2009
@@ -4,7 +4,7 @@
* llvm.vim
- Syntax highlighting mode for LLVM assembly files. To use, COPY `llvm.vim' to
+ Syntax highlighting mode for LLVM assembly files. To use, copy `llvm.vim' to
~/.vim/syntax and add this code to your ~/.vimrc :
augroup filetype
@@ -13,7 +13,7 @@
* tablegen.vim
- Syntax highlighting mode for TableGen description files. To use, COPY
+ Syntax highlighting mode for TableGen description files. To use, copy
`tablegen.vim' to ~/.vim/syntax and add this code to your ~/.vimrc :
augroup filetype
@@ -21,12 +21,13 @@
augroup END
-IMPORTANT: Making symlinks from ~/.vim/syntax/... to the syntax files in your
-LLVM source tree does not work, you DO need to copy the files directly.
+If you prefer, instead of making copies you can make symlinks from
+~/.vim/syntax/... to the syntax files in your LLVM source tree. Apparently
+did not work with older versions of vim however, so if this doesn't work
+you may need to make actual copies of the files.
-However, if you do not already have a ~/.vim/syntax/ directory, simply
-symlinking it to llvm/utils/vim will do the trick nicely, and you can stay
-up-to-date with CVS.
+Another option, if you do not already have a ~/.vim/syntax directory, is
+to symlink ~/.vim/syntax itself to llvm/utils/vim .
Note: If you notice missing or incorrect syntax highlighting, please contact
<llvmbugs [at] cs.uiuc.edu>; if you wish to provide a patch to improve the
More information about the llvm-commits
mailing list