On Tuesday, April 24, 2018 at 3:40:39 PM UTC-4, jrodman-tcell wrote: > Defaulting on the terminal mouse via defaults.vim breaks many expected > behaviors, and should not be on by default, even when there is no .vimrc > present. > > In addition, this setting should lose to other settings in /etc if they > express an alternate value that conflicts with the one in defaults.vim > > Vim has a very long history of being conservative and reliable. I have > generally trusted vim. This setting is far too aggressive. Today it has > caused significant lost productivity, and there is no clear path towards > resolving this for the future across the many environments where I will > encounter vim. I cannot readily automate installing sanity on every image, > vm, os, docker image, etc where I might expect vim to execute in the future. > > I will not be surprised if this is a dupe, but I made a good faith effort to > search for past issues, open or closed before creating it, and I feel it is a > real and serious regression in vim behavior. > > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub
Why are we discussing this? There are better things to focus on. 1. No one wants mouse=a as default (think about vim philosophy and user base) 2. It makes more sense to leave as mouse= (this is the default right now, right?) It's just as easy to put mouse= as mouse=a in vimrc, but mouse= as default makes more sense. -- -- 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 received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
