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? -- 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/CAEJNuHwzC90ns5K9Yp-8s0KjmzB5xJrgVBpN2aNbgQK%2BAY4k-A%40mail.gmail.com.