On Fri, 1 May 2020 at 12:33, Tony Mechelynck <antoine.mechely...@gmail.com> wrote: > > On Fri, May 1, 2020 at 12:02 PM Christian Brabandt <cbli...@256bit.org> wrote: > > > > > > On Fr, 01 Mai 2020, 'Ottavio Caruso' via vim_use wrote: > > > > > On Fri, 1 May 2020 at 09:18, Christian Brabandt <cbli...@256bit.org> > > > wrote: > > > > > > > > > > > > On Do, 30 Apr 2020, 'Ottavio Caruso' via vim_use wrote: > > > > > > > > > On Thu, 30 Apr 2020 at 21:21, Christian Brabandt <cbli...@256bit.org> > > > > > wrote: > > > > > > > > > > > > > > > > > > Hi Ottavio, > > > > > > can you please test with the latest version? I believe there were > > > > > > some > > > > > > patches that fixes such a problem. > > > > > > > > > > I've just compiled from the latest Github sources (8.2.0671), and > > > > > unfortunately I have the same problem. > > > > > > > > Hm, not sure. Looks like to be caused by a vi-compatible setting > > > > (possible shortmess). BTW: what is the size of your terminal? (echo > > > > $LINES $COLUMNS to find out). How long is the complete path? Does it > > > > matter, if the complete path is shorter (e.g. try with a bigger terminal > > > > window). > > > > > > That was it! > > > > > > $ echo $LINES $COLUMNS > > > 24 80 > > > > > > Stretching the terminal to 100 columns solves the issue. And using a > > > shorter path, too. > > > > > > So, we know what it is that triggers the message. Is it still a bug? > > > > not sure. > > > > Best, > > Christian > > I'm not sure either. Ottavio, what is 'cmdheight' set to? Ask it with > :verbose set ch?
cmdheight=1 > The default setting is 1, which IMHO is often too small a value. Does > the problem still happen (with long pathfilenames and/or narrow > terminal sizes) if you do > :set ch+=1 ch? > once or twice? If it doesn't, you can make that setting permanent by > writing it (not with += but with = and the actual value) into your > vimrc. Yes, changing cmdheight to solves the problem, but I have "-u NONE" intentionally, in order to emulate legacy vi, therefore I can't put anything in my .vimrc. (Incidentally, you might ask why I'm not using nvi, and the reason is that it's buggy). I can live with that. If it's not a bug and it's intended behaviour, so be it. -- Ottavio Caruso -- -- 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 --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAEJNuHxeawT8rgHRdCL7wwqjhTE-21VH_QGog2R3Jj%3DrB27j0w%40mail.gmail.com.
