Keven Lyda wrote:
> On Sunday, July 24, 2016 at 2:03:06 PM UTC+1, 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?
For me nothing changed. My vimrc used to source the vimrc_example.vim,
it still does, but now vimrc_example.vim just sources the
defaults.vim, which contains what used to be in the vimrc_example.vim.
No sweat.
About system vimrc files, I hate them: in my experience they contain
the misguided and u
On Fr, 10 Nov 2017, Kevin Lyda wrote:
> On Sunday, July 24, 2016 at 2:03:06 PM UTC+1, 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 o
On Sunday, July 24, 2016 at 2:03:06 PM UTC+1, 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
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.
> >
> > Z
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 rem
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 means
Hi Bram and list,
2016-7-24(Sun) 22:03:06 UTC+9 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 use
"map Q gq" has long been part of the vimrc_example.vim. Now it is
moved to defaults.vim which vimrc_example.vim sources. So if you have
a vimrc you won't be affected, even if your own vimrc sources the
vimrc_example.vim, because in that case you already had it and will
keep it. If, like me, you don
On Thursday, July 28, 2016 at 4:32:31 PM UTC+2, ZyX wrote:
> You can’t. “At the same time” may mean both “ pressed slightly
> after pressed slightly before press after is in par with `Q`: `g` and `q` use different fingers and they need to
> be pressed in specific sequence as well. `Q` may actua
I wrote:
[...]
> Another solution: When there is a .vimrc, then don't load startup.vim.
> Rely on the user already have his preferences in the .vimrc.
> Thus only apply these better defaults when the user doesn't have his own
> settings. Ah, I see Ben also had this idea.
>
> The more I think a
2016-07-28 16:58 GMT+03:00 Bram Moolenaar :
>
> Martin Lundberg wrote:
>
>> On Tuesday, July 26, 2016 at 11:18:01 PM UTC+2, Bram Moolenaar wrote:
>> > " Don't use Ex mode, use Q for formatting
>> > map Q gq
>>
>> What's the reason for doing this change when the new mapping has just
>> as much key p
Martin Lundberg wrote:
> On Tuesday, July 26, 2016 at 11:18:01 PM UTC+2, Bram Moolenaar wrote:
> > " Don't use Ex mode, use Q for formatting
> > map Q gq
>
> What's the reason for doing this change when the new mapping has just
> as much key presses? For me it actually feels like it's slower tha
On Tuesday, July 26, 2016 at 11:18:01 PM UTC+2, Bram Moolenaar wrote:
> " Don't use Ex mode, use Q for formatting
> map Q gq
What's the reason for doing this change when the new mapping has just as much
key presses? For me it actually feels like it's slower than gq since I need to
involve and mo
On Wed, Jul 27, 2016 at 9:09 PM, Bram Moolenaar wrote:
>
> Gary Johnson wrote:
>
>> [...]
>>
>> Not all of those would be my preference, but they seem reasonable,
>> and as long as all of that is in a file and the compile-time
>> defaults aren't changed, I'm fine with it.
>>
>> I was surprised by
On Wed, Jul 27, 2016 at 1:31 PM, Kazunobu Kuriyama <
kazunobu.kuriy...@gmail.com> wrote:
>
> It may be true that setting go+=M will reduce memory usage and make
> startup faster. But I would say the benefit gained by doing that is quite
> marginal.
>
It makes a noticeable difference to me. That
Gary Johnson wrote:
> [...]
>
> Not all of those would be my preference, but they seem reasonable,
> and as long as all of that is in a file and the compile-time
> defaults aren't changed, I'm fine with it.
>
> I was surprised by this:
>
> > " For Win32 GUI: remove 't' flag from 'guioptions':
Manuel Ortega wrote:
> On Wed, Jul 27, 2016 at 2:51 AM, Manuel Ortega
> wrote:
>
> > On Tue, Jul 26, 2016 at 5:17 PM, Bram Moolenaar
> > wrote:
> >
> >>
> >>
> >> " Switch syntax highlighting on when the terminal has colors or when
> >> using the
> >> " GUI (which always has colors).
> >> if &
Perhaps another way to fix this would be if the user could have a
~/.vim/menu.vim that is treated like ~/.vim/filetype.vim is treated. I.e.,
that Vim will load the ~/.vim/menu.vim before it loads
$VIMRUNTIME/menu.vim. That way, a user could in his own ~/.vim/menu.vim
set some variables that will
On Wed, Jul 27, 2016 at 1:47 PM, Gary Johnson wrote:
> On 2016-07-27, Manuel Ortega wrote:
> > On Wed, Jul 27, 2016 at 12:26 PM, Gary Johnson wrote:
> >
> > On 2016-07-27, Manuel Ortega wrote:
> >
> > > What if "syntax on" and "filetype plugin indent on" were moved
> into the
> > auto
On Wed, Jul 27, 2016 at 7:47 PM, Gary Johnson wrote:
> On 2016-07-27, Manuel Ortega wrote:
>> On Wed, Jul 27, 2016 at 12:26 PM, Gary Johnson wrote:
>>
>> On 2016-07-27, Manuel Ortega wrote:
>>
>> > What if "syntax on" and "filetype plugin indent on" were moved into the
>> autocmd
>>
On Wed, Jul 27, 2016 at 8:00 PM, Gary Johnson wrote:
> On 2016-07-27, Tony Mechelynck wrote:
>> On Wed, Jul 27, 2016 at 4:43 PM, Gary Johnson wrote:
>> > On 2016-07-27, Manuel Ortega wrote:
>> >
>> >> If "syntax on" is in the system vimrc as proposed, then I can't seem to
>> >> find
>> >> any way
On 2016-07-27, Tony Mechelynck wrote:
> On Wed, Jul 27, 2016 at 4:43 PM, Gary Johnson wrote:
> > On 2016-07-27, Manuel Ortega wrote:
> >
> >> If "syntax on" is in the system vimrc as proposed, then I can't seem to
> >> find
> >> any way *at all* to disable the loading of the system menu.vim (short
On 2016-07-27, Manuel Ortega wrote:
> On Wed, Jul 27, 2016 at 12:26 PM, Gary Johnson wrote:
>
> On 2016-07-27, Manuel Ortega wrote:
>
> > What if "syntax on" and "filetype plugin indent on" were moved into the
> autocmd
> > group "vimStartup" that the proposed system vimrc defines
On Wed, Jul 27, 2016 at 4:43 PM, Gary Johnson wrote:
> On 2016-07-27, Manuel Ortega wrote:
>
>> If "syntax on" is in the system vimrc as proposed, then I can't seem to find
>> any way *at all* to disable the loading of the system menu.vim (short of
>> unacceptable hacks like bash-aliasing 'vim' to
2016-07-28 1:04 GMT+09:00 Manuel Ortega :
> On Wed, Jul 27, 2016 at 11:40 AM, Manuel Ortega
> wrote:
>
>>
>>> I agree that "syntax on" and "filetype on" (maybe even "filetype plugin
>>> indent on") are pretty core features that should probably be enabled by
>>> default, as nearly everyone will us
On Wed, Jul 27, 2016 at 12:26 PM, Gary Johnson wrote:
> On 2016-07-27, Manuel Ortega wrote:
>
> > What if "syntax on" and "filetype plugin indent on" were moved into the
> autocmd
> > group "vimStartup" that the proposed system vimrc defines, under VimEnter
> > autocmds:
> >
> > au VimEnter * syn
On 2016-07-27, Manuel Ortega wrote:
> What if "syntax on" and "filetype plugin indent on" were moved into the
> autocmd
> group "vimStartup" that the proposed system vimrc defines, under VimEnter
> autocmds:
>
> au VimEnter * syntax on
> au VimEnter * filetype plugin on
>
> This way, everyone w
On Wed, Jul 27, 2016 at 11:40 AM, Manuel Ortega
wrote:
>
>> I agree that "syntax on" and "filetype on" (maybe even "filetype plugin
>> indent on") are pretty core features that should probably be enabled by
>> default, as nearly everyone will use them.
>>
>
>
>> However, I disagree that this shou
On Wed, Jul 27, 2016 at 10:45 AM, Ben Fritz wrote:
> On Wednesday, July 27, 2016 at 5:20:14 AM UTC-5, Kazunobu Kuriyama wrote:
> > 2016-07-27 17:01 GMT+09:00 Manuel Ortega :
> >
> > > If "syntax on" is in the system vimrc as proposed, then I can't seem
> > > to find any way *at all* to disable th
On Wed, Jul 27, 2016 at 10:43 AM, Gary Johnson wrote:
> On 2016-07-27, Manuel Ortega wrote:
>
> > If "syntax on" is in the system vimrc as proposed, then I can't seem to
> find
> > any way *at all* to disable the loading of the system menu.vim (short of
> > unacceptable hacks like bash-aliasing '
On Wed, Jul 27, 2016 at 6:20 AM, Kazunobu Kuriyama <
kazunobu.kuriy...@gmail.com> wrote:
> 2016-07-27 17:01 GMT+09:00 Manuel Ortega :
>
>> On Wed, Jul 27, 2016 at 3:51 AM, Manuel Ortega
>> wrote:
>>
>>> On Wed, Jul 27, 2016 at 2:51 AM, Manuel Ortega
>>> wrote:
>>>
On Tue, Jul 26, 2016 at 5:
On Wednesday, July 27, 2016 at 9:45:11 AM UTC-5, Ben Fritz wrote:
>
> What if the default settings were not applied, if the user has specified
> a .vimrc?
...or maybe a new file sourced before the default settings? The default
settings file itself could source it, if it exists.
--
--
You rece
On Wednesday, July 27, 2016 at 5:20:14 AM UTC-5, Kazunobu Kuriyama wrote:
> 2016-07-27 17:01 GMT+09:00 Manuel Ortega :
>
> > If "syntax on" is in the system vimrc as proposed, then I can't seem
> > to find any way *at all* to disable the loading of the system
> > menu.vim (short of unacceptable ha
On 2016-07-27, Manuel Ortega wrote:
> If "syntax on" is in the system vimrc as proposed, then I can't seem to find
> any way *at all* to disable the loading of the system menu.vim (short of
> unacceptable hacks like bash-aliasing 'vim' to 'vim -u ~/.vimrc'.)
How about "sudo rm /usr/share/vim/vimr
Hi James!
On Mi, 27 Jul 2016, James McCoy wrote:
> I'd wager it's more than you think. I know many people that change gvim to
> basically look like console vim. Personally, I set 'guioptions' to just
> "cM".
I do as well, but then I do not use vimrc_example. And that file should
be an example f
On Jul 27, 2016 6:20 AM, "Kazunobu Kuriyama"
wrote:
>
> 2016-07-27 17:01 GMT+09:00 Manuel Ortega :
>> If "syntax on" is in the system vimrc as proposed, then I can't seem to
find any way *at all* to disable the loading of the system menu.vim (short
of unacceptable hacks like bash-aliasing 'vim' to
2016-07-27 17:01 GMT+09:00 Manuel Ortega :
> On Wed, Jul 27, 2016 at 3:51 AM, Manuel Ortega
> wrote:
>
>> On Wed, Jul 27, 2016 at 2:51 AM, Manuel Ortega
>> wrote:
>>
>>> On Tue, Jul 26, 2016 at 5:17 PM, Bram Moolenaar
>>> wrote:
>>>
" Switch syntax highlighting on when the termin
On Wed, Jul 27, 2016 at 3:51 AM, Manuel Ortega
wrote:
> On Wed, Jul 27, 2016 at 2:51 AM, Manuel Ortega
> wrote:
>
>> On Tue, Jul 26, 2016 at 5:17 PM, Bram Moolenaar
>> wrote:
>>
>>>
>>>
>>> " Switch syntax highlighting on when the terminal has colors or when
>>> using the
>>> " GUI (which alway
On Wed, Jul 27, 2016 at 2:51 AM, Manuel Ortega
wrote:
> On Tue, Jul 26, 2016 at 5:17 PM, Bram Moolenaar
> wrote:
>
>>
>>
>> " Switch syntax highlighting on when the terminal has colors or when
>> using the
>> " GUI (which always has colors).
>> if &t_Co > 2 || has("gui_running")
>> syntax on
>
On Tue, Jul 26, 2016 at 5:17 PM, Bram Moolenaar wrote:
>
>
> " Switch syntax highlighting on when the terminal has colors or when using
> the
> " GUI (which always has colors).
> if &t_Co > 2 || has("gui_running")
> syntax on
>
Wait a sec. If "syntax on" is done here, then won't it be impossi
On Tue, Jul 26, 2016 at 5:17 PM, Bram Moolenaar wrote:
>
> " Only do this part when compiled with support for autocommands.
> if has("autocmd")
>
> " Enable file type detection.
> " Use the default filetype settings, so that mail gets 'tw' set to 72,
> " 'cindent' is on in C files, etc.
>
On 2016-07-26, Bram Moolenaar wrote:
> Gary Johnson wrote:
>
> > On 2016-07-26, Bram Moolenaar wrote:
> > > James McCoy wrote:
> > >
> > > > On Mon, Jul 25, 2016 at 07:39:55AM -0700, Ben Fritz wrote:
> > > > > On Sunday, July 24, 2016 at 8:03:06 AM UTC-5, Bram Moolenaar wrote:
> > > > > >
> > >
Gary Johnson wrote:
> On 2016-07-26, Bram Moolenaar wrote:
> > James McCoy wrote:
> >
> > > On Mon, Jul 25, 2016 at 07:39:55AM -0700, Ben Fritz wrote:
> > > > On Sunday, July 24, 2016 at 8:03:06 AM UTC-5, Bram Moolenaar wrote:
> > > > >
> > > > > if has("autocmd")
> > > > > " Enable file
On 2016-07-26, Bram Moolenaar wrote:
> James McCoy wrote:
>
> > On Mon, Jul 25, 2016 at 07:39:55AM -0700, 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 p
James McCoy wrote:
> On Mon, Jul 25, 2016 at 07:39:55AM -0700, 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 plugi
On Mon, Jul 25, 2016 at 07:37:46AM -0700, Ben Fritz wrote:
> If one were to change anything for ease-of-use for new users, it wouldn't be
> 'hidden', it would be 'confirm', so that Vim becomes consistent with many
> other programs which don't just refuse to quit when you have unsaved changes,
>
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 personal
> >> preferen
Hi Bram,
On Sun, Jul 24, 2016 at 03:02:56PM +0200, Bram Moolenaar
wrote:
> Vim has always been conservative about the default option values.
And that is actually a very good thing.
As I work as a consultant, and the systems the customers use have
a wide variety of Linux distributions of varyin
On Tue, Jul 26, 2016 at 5:03 AM, Matthew Winn wrote:
> On 24/07/16 20:43, Bram Moolenaar wrote:
>>
>> Christian Brabandt wrote:
>>>
>>> please no hlsearch. That is most often annoying.
>>
>> Well, I find it useful. But I suppose that's more a personal
>> preference.
>
> Searching for a pattern is
On 24/07/16 20:43, Bram Moolenaar wrote:
Christian Brabandt wrote:
please no hlsearch. That is most often annoying.
Well, I find it useful. But I suppose that's more a personal
preference.
Searching for a pattern is a fundamentally different operation from
highlighting matches of a pattern. I
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 hlsearch. That is most often anno
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...
>>
>> Obviously useful things
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 made
On Mon, Jul 25, 2016 at 07:39:55AM -0700, 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 on filet
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 find it useful. But I suppose
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 made ctrl-l clear the s
On Mon, Jul 25, 2016 at 4: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...
> >
> > Obviously us
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 made ctrl-l clear the search highlighting by default?
>
>>> some
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
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'.
On Mon, Jul 25, 2016 at 8:03 PM, Charles E Campbell
wrote:
+>> set langnoremap
>> endif
>
> I had to look this one up as I've never had cause to use it. Easily
> reversed, so I'm neutral on this one.
>>
>>
>> Probably not:
>>
>> " these two leave files behind
>> set backup
>> set undo
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', thus create a .v
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 on filetype stuff at a ver
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 receive
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 man
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
> > improvements.
> >
> > Here is
On 2016-07-24 15:02, Bram Moolenaar wrote:
> " For all text files set 'textwidth' to 78 characters.
> autocmd FileType text setlocal textwidth=78
I'd object to that, autocommands are executed after ftplugins and would
overwrite user settings (unless the user creates an au to change it).
S
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':
[...]
> set hidden
>
> Because 'no
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', t
Manuel Ortega wrote:
> On Sun, Jul 24, 2016 at 9:02 AM, Bram Moolenaar wrote:
> > " For all text files set 'textwidth' to 78 characters.
> > autocmd FileType text setlocal textwidth=78
> Please don't "setlocal" a &textwidth value for text files. Don't mess
> with this at all, but if you
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 settin
Tyru wrote:
> so do you think this setting is also personal preference, not 'compatible'
> one?
>
> set display+=lastline
>
> Any reason to not display long line instead of '@' ?
> for speed?
> is it really good default value for "normal user" ?
I'm not sure if I am a good example, but I don't
> 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
> se
Hi Bram,
2016/07/25 0:33 "Bram Moolenaar" :
>
>
> Nicola wrote:
>
> > On 2016-07-24 13:02:56 +, Bram Moolenaar said:
> >
> > > 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 o
On Sun, Jul 24, 2016 at 12:09 PM, Manuel Ortega
wrote:
> On Sun, Jul 24, 2016 at 9:02 AM, Bram Moolenaar
> wrote:
>
>>
>>
>> Probably not:
>>
>> " these two leave files behind
>> set backup
>> set undofile
>>
>> " may conflict with a user mapping
>> inoremap u
>>
>> " hard to revert
On Sun, Jul 24, 2016 at 9:02 AM, 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
Nicola wrote:
> On 2016-07-24 13:02:56 +, Bram Moolenaar said:
>
> > 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
> > nea
Hi Bram,
> 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.
>
Hi,
On Sun, Jul 24, 2016 at 7:04 AM, lilydjwg wrote:
> Hi,
>
> On Sun, Jul 24, 2016 at 10:21:32PM +0900, tyru wrote:
>> I want to propose the following settings additionally.
>>
>>
>> set ambiwidth=double
>
> Please don't do this for Linux terminals, at least when
Hi,
On Sun, Jul 24, 2016 at 10:21:32PM +0900, tyru wrote:
> I want to propose the following settings additionally.
>
>
> set ambiwidth=double
Please don't do this for Linux terminals, at least when it doesn't work
well:
For the following text,
“test”
‘test’
gv
On 2016-07-24 13:02:56 +, Bram Moolenaar said:
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 'nocompa
Hi Bram!
2016-07-24 22:02 GMT+09:00 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 wan
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
84 matches
Mail list logo
