After upgrading to Fedora 32 I've noticed when editing files, especially spec files that vim does some crazy jumps/indents that it didn't do before. Right now I'm pressing i to insert a line before a Requires: and when I hit enter it jumps to the next line (fine) but with 4 indents and one space... WTF? Anyone else seeing strange vim behavior?

I also have seen some weirdness of late, but I'm still on F31. I had yaml files indented with sw=4 and my foldmethod=indent. Now I have to open the fold twice, once for the invisible fold that seems to be implied as if sw=2 and one more to get the real thing. If I reformat to use 2-space indents the folding works like I'd expect but something changed. I've also gotten lots of pain with certain key combos that were solid for ages. Ctrl-6 to swap buffers % and # now must be Ctrl-Shift-6 for vim, though the former still works in gvim. I have a mapping for <C-E> :nohlsearch<CR> that I've used for over a decade to un-highlight a search. That no longer works in vim or gvim. Until I'd found that I figured something in konsole had changed. But once gvim revealed weird issues I figured it must be more of a vim thing. Now seeing this message, I'm becoming even more certain. John Florian On 2020-07-25 09:21, Richard Shaw wrote: After upgrading to Fedora 32 I've noticed when editing files, especially spec files that vim does some crazy jumps/indents that it didn't do before. Right now I'm pressing i to insert a line before a Requires: and when I hit enter it jumps to the next line (fine) but with 4 indents and one space... WTF? Anyone else seeing strange vim behavior? Thanks, Richard _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

I also have seen some weirdness of late, but I'm still on F31.  I had yaml files indented with sw=4 and my foldmethod=indent.  Now I have to open the fold twice, once for the invisible fold that seems to be implied as if sw=2 and one more to get the real thing.  If I reformat to use 2-space indents the folding works like I'd expect but something changed.  I've also gotten lots of pain with certain key combos that were solid for ages.  Ctrl-6 to swap buffers % and # now must be Ctrl-Shift-6 for vim, though the former still works in gvim.  I have a mapping for <C-E> :nohlsearch<CR> that I've used for over a decade to un-highlight a search.  That no longer works in vim or gvim.  Until I'd found that I figured something in konsole had changed.  But once gvim revealed weird issues I figured it must be more of a vim thing. Now seeing this message, I'm becoming even more certain.

After upgrading to Fedora 32 I've noticed when editing files, especially spec files that vim does some crazy jumps/indents that it didn't do before. Right now I'm pressing i to insert a line before a Requires: and when I hit enter it jumps to the next line (fine) but with 4 indents and one space... WTF? Anyone else seeing strange vim behavior?

Hi all, first I would like to recommend you to try the steps here: https://vimhelp.org/vim_faq.txt.html#faq-2.5 it should help you find out where the problem can be. If you are able to reproduce the issue with the first step, please file a bug on bugzilla.redhat.com.

I finally ran into another issue and used the vim faq. It was ":set cindent" that was causing the crazy indentation in spec file %changelogs. I still consider this a bug as the file doesn't even end in c, cpp, cxx, c++ etc.

On Tue, Aug 4, 2020 at 10:49 AM Jonathan Wakely <jwakely(a)fedoraproject.org&gt; wrote: > On 03/08/20 13:32 -0500, Richard Shaw wrote: > >I finally ran into another issue and used the vim faq. It was ":set > >cindent" that was causing the crazy indentation in spec file %changelogs. > > > >I still consider this a bug as the file doesn't even end in c, cpp, cxx, > >c++ etc. > > What's turning it on for non-C files? > Got me, I haven't dug in that far, just turned it off for now.