On Oct 13, 10:22 am, Tony Mechelynck <[EMAIL PROTECTED]> wrote: > On 13/10/08 15:43, Bobby Impollonia wrote: > > > :verbose set cino? > > replies with > > cinoptions=(0 > > Last set from ~/.vimrc > > > That seems right, but it is still not having any effect. > > You did this while editing the file where you were expecting it to had > an effect, and with that file current (i.e., not only visible but with > the visible cursor in it, etc.), right?
Yes. I only had one open window with one buffer and that is where the cursor is. I think you were right in your earlier comment about this relating to filetypes. If I start vim with vim somefile where somefile is a new file, my cino setting does seem to be respected. However, if I do vim a.py where a.py is an extant python file, then the setting is not respected and I get the default behavior of indentation by 2 * shiftwidth. This is problematic because the reason I want to get this working is specifically for indenting python code. In both cases, "verbose set cino?" gives the output indicated above (and vim also claims cindent is enabled). I can understand that the python ft settings could set its own values for cinoptions that are clobbering mine, but then shouldn't "verbose set cino?" reflect those settings? --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
