Re: Changing the defaults with Vim 8

2016-08-21 Thread h_east
Hi Michael, 2016-8-21(Sun) 21:58:54 UTC+9 Michael Henry: > On 08/20/2016 01:22 PM, Bram Moolenaar wrote: > > Hirohito Higashi wrote: > >> `set ttimeoutlen=0` will solve the above. > >> > >> I have invested in above setting more than a year, but the > >> trouble does not happen even once. > > > >

Re: Changing the defaults with Vim 8

2016-08-21 Thread Michael Henry
On 08/20/2016 01:22 PM, Bram Moolenaar wrote: > Hirohito Higashi wrote: >> `set ttimeoutlen=0` will solve the above. >> >> I have invested in above setting more than a year, but the >> trouble does not happen even once. > > Zero only works when you are directly using a terminal. When > using a

Re: Changing the defaults with Vim 8

2016-08-20 Thread Marcin Szamotulski
Hi Tim and Bram > > > As a backwards incompatible change, my biggest want would be that the > > > outer-quotation text objects (a" and a') would no longer eat leading > > > whitespace. I've never wanted the out-of-box behavior, always > > > wanting to change just the string-cum-quotes. > > > >

Re: Changing the defaults with Vim 8

2016-08-20 Thread Bram Moolenaar
Hirohito Higashi wrote: > Sorry for late reply :-) > > I want to add the following setting: > > " If Vim cause malfunctioning cursor keys on slow terminals or very busy > systems, adjust the value or comment out this. > set ttimeoutlen=0 > > 'ttimeoutlen' default value is -1. > This

Re: Changing the defaults with Vim 8

2016-07-26 Thread Brennen Bearnes
A note in support of the idea that 8.0 seems like a reasonable time for this kind of change. Vim's maximum utility and friendliness really only come after some configuration work, and I don't expect that to change any time soon, but nudging it towards more modern out-of-the-box behavior for new

Re: Changing the defaults with Vim 8

2016-07-26 Thread Erik Falor
On Sun, Jul 24, 2016 at 07:50:51PM -0700, h_east wrote: > Please refer to the last two lines of `:help iquote`. > DOC> i" v_iquote iquote > DOC> i' v_i' i' > DOC> i`

Re: Changing the defaults with Vim 8

2016-07-26 Thread Greg Vilardi
On Tue, Jul 26, 2016 at 01:21:56PM +0200, Bram Moolenaar wrote: > > Tony Mechelynck wrote: > > > On Mon, Jul 25, 2016 at 10:10 PM, Christian Brabandt > > wrote: > > > Hi Bram! > > > > > > On So, 24 Jul 2016, Bram Moolenaar wrote: > > > > > >> > please no hlsearch. That is

Re: Changing the defaults with Vim 8

2016-07-26 Thread Bram Moolenaar
Tony Mechelynck wrote: > On Mon, Jul 25, 2016 at 10:10 PM, Christian Brabandt > wrote: > > Hi Bram! > > > > On So, 24 Jul 2016, Bram Moolenaar wrote: > > > >> > please no hlsearch. That is most often annoying. > >> > >> Well, I find it useful. But I suppose that's more a

Re: Changing the defaults with Vim 8

2016-07-26 Thread Tim Chase
On 2016-07-25 18:25, Gary Johnson wrote: > If you want to have Ctrl-L also execute :nohls, I do... > create a mapping. I do. Though I also agree that it's the sort of thing that people will change if they want different behavior. So I don't see changing it just for the sake of changing

Re: Changing the defaults with Vim 8

2016-07-25 Thread Tony Mechelynck
On Mon, Jul 25, 2016 at 10:00 PM, Bram Moolenaar wrote: > > Hirohito Higashi wrote: > >> I think it is better to change the default value of Vim body for some >> of the options. >> >> i.e. >> set wildmenu >> set ruler >> set showcmd >> set tags=./tags;,tags; >> etc... >> >>

Re: Changing the defaults with Vim 8

2016-07-25 Thread Gary Johnson
On 2016-07-26, Tony Mechelynck wrote: > On Tue, Jul 26, 2016 at 12:10 AM, Tumbler Terrall > wrote: > > On Monday, July 25, 2016 at 3:11:11 PM UTC-5, Christian Brabandt wrote: > >> Hi Bram! > >> > >> On So, 24 Jul 2016, Bram Moolenaar wrote: > >> > >> > > please no

Re: Changing the defaults with Vim 8

2016-07-25 Thread Tony Mechelynck
On Tue, Jul 26, 2016 at 12:10 AM, Tumbler Terrall wrote: > On Monday, July 25, 2016 at 3:11:11 PM UTC-5, Christian Brabandt wrote: >> Hi Bram! >> >> On So, 24 Jul 2016, Bram Moolenaar wrote: >> >> > > please no hlsearch. That is most often annoying. >> > >> > Well, I

Re: Changing the defaults with Vim 8

2016-07-25 Thread Tony Mechelynck
On Mon, Jul 25, 2016 at 10:10 PM, Christian Brabandt wrote: > Hi Bram! > > On So, 24 Jul 2016, Bram Moolenaar wrote: > >> > please no hlsearch. That is most often annoying. >> >> Well, I find it useful. But I suppose that's more a personal >> preference. > > perhaps, if we

Re: Changing the defaults with Vim 8

2016-07-25 Thread Tumbler Terrall
On Monday, July 25, 2016 at 3:11:11 PM UTC-5, Christian Brabandt wrote: > Hi Bram! > > On So, 24 Jul 2016, Bram Moolenaar wrote: > > > > please no hlsearch. That is most often annoying. > > > > Well, I find it useful. But I suppose that's more a personal > > preference. > > perhaps, if we

Re: Changing the defaults with Vim 8

2016-07-25 Thread Christian Brabandt
Hi Bram! On So, 24 Jul 2016, Bram Moolenaar wrote: > > please no hlsearch. That is most often annoying. > > Well, I find it useful. But I suppose that's more a personal > preference. perhaps, if we made ctrl-l clear the search highlighting by default? > > some more I would set, the mentioned

Re: Changing the defaults with Vim 8

2016-07-25 Thread Bram Moolenaar
Hirohito Higashi wrote: > I think it is better to change the default value of Vim body for some > of the options. > > i.e. > set wildmenu > set ruler > set showcmd > set tags=./tags;,tags; > etc... > > Obviously useful things should be changed. A few people have mentioned setting 'wildmenu'.

Re: Changing the defaults with Vim 8

2016-07-25 Thread Tony Mechelynck
On Mon, Jul 25, 2016 at 4:39 PM, Ben Fritz wrote: > On Sunday, July 24, 2016 at 8:03:06 AM UTC-5, Bram Moolenaar wrote: >> >> if has("autocmd") >> " Enable file type detection. >> filetype plugin indent on >> > > Don't common plugin managers require you to turn

Re: Changing the defaults with Vim 8

2016-07-25 Thread h_east
Hi Bram and All, I think it is better to change the default value of Vim body for some of the options. i.e. set wildmenu set ruler set showcmd set tags=./tags;,tags; etc... Obviously useful things should be changed. Thanks. -- Best regards, Hirohito Higashi (a.k.a. h_east) -- -- You

Re: Changing the defaults with Vim 8

2016-07-25 Thread Ben Fritz
On Monday, July 25, 2016 at 8:02:21 AM UTC-5, Tony Mechelynck wrote: > On Mon, Jul 25, 2016 at 11:00 AM, wrote: > > Ideally, starting the program as 'vim' would automatically give the user > > the improvements promised in the name. And 'vi' would hide all those > >

Re: Changing the defaults with Vim 8

2016-07-25 Thread Ben Fritz
On Sunday, July 24, 2016 at 8:03:06 AM UTC-5, Bram Moolenaar wrote: > > if has("autocmd") > " Enable file type detection. > filetype plugin indent on > Don't common plugin managers require you to turn on filetype stuff at a very specific location, e.g. *after* loading the plugin

Re: Changing the defaults with Vim 8

2016-07-25 Thread Tony Mechelynck
On Mon, Jul 25, 2016 at 11:00 AM, wrote: > Ideally, starting the program as 'vim' would automatically give the user the > improvements promised in the name. And 'vi' would hide all those improvements. > > Here is my list of options to set when run as 'vim': [...] >

Re: Changing the defaults with Vim 8

2016-07-25 Thread Erik Christiansen
On 24.07.16 15:02, Bram Moolenaar wrote: > If someone wants to start with 'nocompatible', but not all of the new > option values, a .vimrc would be needed to change the settings. This is > the most common and also most tricky part. Assuming that the user will > want most of the new option

Re: Changing the defaults with Vim 8

2016-07-25 Thread romainlafourcade
Ideally, starting the program as 'vim' would automatically give the user the improvements promised in the name. And 'vi' would hide all those improvements. Here is my list of options to set when run as 'vim': set nocompatible Just because. set autoindent It's smart enough to cover

Re: Changing the defaults with Vim 8

2016-07-24 Thread Gary Johnson
On 2016-07-24, Bram Moolenaar wrote: > Vim has always been conservative about the default option values. > Without any .vimrc the default is 'compatible'. That's nice for people > who rely on the old Vi. But how many of these still exist? I expect > nearly all Vim users to want 'nocompatible',

Re: Changing the defaults with Vim 8

2016-07-24 Thread Tony Mechelynck
Hi Bram, For about as long as I've been using Vim, I've had a .vimrc with a "runtime vimrc_example.vim" line in it and a few (and then more than only a few) lines added to it to tweak it to my liking. For instance a number of additional mappings. To revert part of the "filetype plugin indent on"

Re: Changing the defaults with Vim 8

2016-07-24 Thread h_east
Hi Tim and Bram, I react only to the last sentence. 2016-7-25(Mon) 4:43:30 UTC+9 Bram Moolenaar: > Tim Chase wrote: > > > On 2016-07-24 15:02, Bram Moolenaar wrote: > > > What has stopped me from changing this is the unexpected change. > > > Many users will notice that Vim suddenly behaves

Re: Changing the defaults with Vim 8

2016-07-24 Thread Bram Moolenaar
Christian Brabandt wrote: > > set backspace=indent,eol,start > > +1 > > > set history=50" keep 50 lines of command line history > > Why only 50? Good point, the Vim default already is 50. That changed a while back. How about 200? > And while we are it, increase the undolevels

Re: Changing the defaults with Vim 8

2016-07-24 Thread Tim Chase
On 2016-07-24 15:02, Bram Moolenaar wrote: > What has stopped me from changing this is the unexpected change. > Many users will notice that Vim suddenly behaves differently. Some > may be upset. The release of Vim 8.0 might be the best point in > time to do this. If we do this. Agreed that 8.0

Re: Changing the defaults with Vim 8

2016-07-24 Thread Christian Brabandt
> set backspace=indent,eol,start +1 > set history=50 " keep 50 lines of command line history Why only 50? And while we are it, increase the undolevels setting > set ruler " show the cursor position all the time > set showcmd " display incomplete commands >

Changing the defaults with Vim 8

2016-07-24 Thread Bram Moolenaar
Vim has always been conservative about the default option values. Without any .vimrc the default is 'compatible'. That's nice for people who rely on the old Vi. But how many of these still exist? I expect nearly all Vim users to want 'nocompatible', thus create a .vimrc ASAP. What has stopped