fritzophrenic wrote: > > > On Oct 13, 5:39 pm, Ian Young <[EMAIL PROTECTED]> wrote: >> Hi all, >> I'm running into a small but annoying problem that has me baffled. >> When I am editing a .php file and type '/*' and hit Return, the next >> line comes up as ' * ' (notice the space on each side), which is the >> behavior I expect and want. >> >> However, I also want .inc and .html files to behave as PHP >> files. .inc files seem to get that behavior automatically, and I have >> 'au BufRead,BufNewFile *.html set filetype=php' in my .vimrc file to >> force .html files to conform. When I am editing a .inc or .html file >> and type '/*' and hit Return, the next line comes up with an extra tab >> and no '*', which is not what I want. >> >> :set filetype confirms that filetype=php in all of these cases. >> >> I can't figure out what setting might be different in cases where I am >> editing one of the latter files, especially concerning .inc files >> where the filetype is assigned without my interference. Anyone have a >> guess? >> >> Thanks, >> Ian > > The "comments" option usually controls this I think. What is the > output of ":set comments?" in each of these files?
In a .inc file: comments=s1:/*,mb:*,ex:*/,://,b:#,:%,:XCOMM,n:>,fb:- In a .php file: comments=s1:/*,mb:*,ex:*/,://,:# I've tried running 'set comments=s1:/*,mb:*,ex:*/,://,:#' in the .inc file, and it didn't change the behavior I described. Ian -- --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
