![]() ![]() There are additional local customizations one can apply besides those found in your personal vimrc file. "When you say 'NONE' don't you really mean 'SOME'?" The 'compatible' part can be solved by using -N with -u NONE but everything else is off/default and you still have the potential issue described in the next section. And surely worst of all, 'compatible' will be enabled which makes Vim behave in ways alien to many modern Vimmers. File type detection is disabled so you won't have syntax highlighting to make things more legible. For example, command-line history and command and filename completion are gone which means having to type everything manually. With -u NONE enabled you may find Vim annoying if not difficult to use. u NONE is fairly well known and widely used to help debug issues with Vim that are thought to be caused by user/local configuration. In other words, don't enable emulation of legacy editor 'vi'.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |