On 12 Okt., 17:47, Tim Chase <[email protected]> wrote: > - Are you running builds with "+diff" enabled? (check the output > of ":version") This is usually the case unless you're running a > minimal build. :ver output includes +diff
> > - are you in "vimdiff" mode? You can find out by issuing > > :set diff? > > in each of the windows-to-diff to see whether Vim considers your > current vim-window a diff-window. This would be different from > editing a patch (*.diff) file. I am in diff mode (starting the files with "vim -d a.txt b.txt") with all the typical vimdiff layout (folds, filler lines, highlighted passages..) > > - when you say the commands "[are] not working at all", what does > that mean? do they simply not jump to the previous/next despite > being able to see that there's a previous/next-change? Do they > perform some other action? Does the screen flash? A have the vertical diff windows with all the highlighted characters on my screen, but the cursor wont move with the [c ]c commands. Instead there is a beep on the [c and the cursor jumps to the first line with the ]c command but never to the next highlighted diff > > - do you see the same behavior with no startup files? > > vimdiff -u NONE file_a.txt file_b.txt > or > vim -u NONE file_a.txt > :vert diffsplit file_b.txt I tried to start the diffmode without any rc files that possibly could remap the jumpto-diff commands and prevent ]c from working properly . But it is just the same behavior: nothing except an error beep. Thanks for your input, franz -- You received this message from the "vim_use" 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
