option notitle requires setting noicon as well

I'm running the latest code from git. I used to have "notitle" set and that worked but now I have to use "noicon" as well. This behavior wasn't very intuitive and it's not well documented in the help text, so I had to find it by looking in the source. regards, dan ca

sh.vim: Fix detection of bash shSubSh(ells) instead of using shCmdParenRegion, and allow functions in shSubSh

Hi, I've noticed that syntax highlighting inside bash subshells is lacking (comments are not rendered as such, for instance). Turns out that was because the subshells were parsed as `shCmdParenRegion` which is for stuff like `cat (one-line command)`. Instead subshells should be parsed as

Re: Syntax Highlighting Doesn't Work with Recursive `nextgroup` Across Newlines When Contained

skipping, so it is just rejected. I just wouldn't have anticipated that it worked that way. -- Dan -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You

Re: Syntax Highlighting Doesn't Work with Recursive `nextgroup` Across Newlines When Contained

highlighting is tricky. This does not explain why the bs in the second line are still not matched even when the comment rule is removed. Is it that the entire nextgroup is thrown away, because the # is not officially part of the B match, so it is counted as not matching? -- Dan -- -- You received

:25CR does not save cursor position to jump list

These commands perform the same function: 25G 25gg :25CR But the first two save the cursor position to the jump list, whereas the last command does not, which I feel is inconsistent and a bug. For example, with the following buffer: 1 abc 2 def 3 ghi Entering the following commands: :1CR :2CR

Re: Reproducibility of test61

you mark the test as flaky, so that it's run more than once and considered OK if it passes at least once? I'm seeing it failing here; out of 28 runs, it failed once. (This is on a buildbot I set up while writing a buildbot tutorial.) Does vim's test harness have a way of marking tests flaky? - Dan

mkview saves folds with normal commands when it should use normal! commands

Steps: Put the following in your vimrc nnoremap z J autocmd BufWinLeave *.* mkview autocmd BufWinEnter *.* silent loadview In the commandline: vim ~/foo Insert this text: Test1 Test1 Test2 Test2 Fold the Test1 lines in one fold (enter visual mode, select them, then press zf) Save and exit.

mkview saves folds incorrectly

Issue: views saved with mkview use normal instead of normal! commands to recreate folding, causing user-create key mappings to trigger. Steps to Reproduce: Put the following in your vimrc nnoremap z J autocmd BufWinLeave *.* mkview autocmd BufWinEnter *.* silent loadview In the commandline: vim

rpm spec syntax: add trigger* sections

RPM .spec files have optional and less-known sections defining scriptlet to be run when foreign packages are installed or removed. Let's color their headers green. diff -r 5e84f6567623 -r 963d0dedc37f runtime/syntax/spec.vim --- a/runtime/syntax/spec.vim Wed Sep 21 20:09:42 2011 +0200 +++

Re: compiling failed for vim 7.2 with perl 5.10

executable in the MSYS-DTK package, which is version 5.6.1. I assume your perl 5.10 is installed in c:\perl, so you need to make sure c:\perl\bin comes before c:\msys\1.0\bin (or wherever you installed msys) in your %PATH% variable. Dan --~--~-~--~~~---~--~~ You

Re: compiling failed for vim 7.2 with perl 5.10

Cesar Romani wrote: Dan Sharp wrote: Cesar Romani wrote: I'm using the Ming compiler on Win XP Pro. Compiling vim 7.2 with perl 5.8 works, but when I try to compile vim 7.2 with perl 5.10 it fails: Thanks a lot for your answer. I changed the order as you indicated but I'm