aboutsummaryrefslogtreecommitdiff
path: root/runtime/doc/quickref.txt
Commit message (Collapse)AuthorAge
* vim-patch:85850f3a5ef9Justin M. Keyes2019-08-02
| | | | | Update runtime files https://github.com/vim/vim/commit/85850f3a5ef9f5a9d22e908ef263de8faa265a95
* vim-patch:7dd64a3e57d2Justin M. Keyes2019-08-02
| | | | | Update runtime files. https://github.com/vim/vim/commit/7dd64a3e57d296fdee3b3ffe6d938f634b59848c
* vim-patch:68e6560b84f1Justin M. Keyes2019-08-02
| | | | | Update runtime files. https://github.com/vim/vim/commit/68e6560b84f196c82e27a72669684d5506a3a837
* doc [ci skip] #10177Justin M. Keyes2019-06-30
| | | ref #10278 #10279 #10353
* signs: support multiple columns #9295Dan Aloni2019-03-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | closes #990 closes #9295 - Support for multiple auto-adjusted sign columns. With this change, having more than one sign on a line, and with the 'auto' setting on 'signcolumn', extra columns will shown automatically to accomodate all the existing signs. For example, suppose we have this view: 5147 } 5148 5149 return sign->typenr; 5150 } 5151 } 5152 return 0; 5153 } 5154 We have GitGutter installed, so it tells us about modified lines that are not commmited. So let's change line 5152: 5147 } 5148 5149 return sign->typenr; 5150 } 5151 } ~ 5152 return 0; 5153 } 5154 Now we add a mark over line 5152 using 'ma' in normal mode: 5147 } 5148 5149 return sign->typenr; 5150 } 5151 } a ~ 5152 return 0; 5153 } 5154 Previously, Vim/Nvim would have picked only one of the signs, because there was no support for having multiple signs in a line. - Remove signs from deleted lines. Suppose we have highlights on a group of lines and we delete them: + 6 use std::ops::Deref; --+ 7 use std::borrow::Cow; --+ 8 use std::io::{Cursor}; 9 use proc_macro2::TokenStream; 10 use syn::export::ToTokens; --+ 11 use std::io::Write; >> 12 use std::ops::Deref; Without this change, these signs will momentarily accumulate in the sign column until the plugins wake up to refresh them. + --+ --+ --+ >> 6 Discussion: It may be better to extend the API a bit and allow this to happen for only certain types of signs. For example, VIM marks and vim-gitgutter removal signs may want to be presreved, unlike line additions and linter highlights. - 'signcolumn': support 'auto:NUM' and 'yes:NUM' settings - sort signs according to id, from lowest to highest. If you have git-gutter, vim-signature, and ALE, it would appear in this order: git-gutter - vim-signature - ALE. - recalculate size before screen update - If no space for all signs, prefer the higher ids (while keeping the rendering order from low to high). - Prevent duplicate signs. Duplicate signs were invisible to the user, before using our extended non-standard signcolumn settings. - multi signcols: fix bug related to wrapped lines. In wrapped lines, the wrapped parts of a line did not include the extra columns if they existed. The result was a misdrawing of the wrapped parts. Fix the issue by: 1. initializing the signcol counter to 0 when we are on a wrap boundary 2. allowing for the draw of spaces in that case.
* vim-patch:8.1.0932: remove Farsi support (#9622)Justin M. Keyes2019-02-17
| | | | | Problem: Farsi support is outdated and unused. Solution: Delete the Farsi support. https://github.com/vim/vim/commit/14184a3133b9a6ee5f711d493c04e41ba4fa7c2f
* vim-patch:8.0.0251: not easy to select Python 2 or 3 (#9173)David Jimenez2019-01-02
| | | | | | Problem: It is not so easy to write a script that works with both Python 2 and Python 3, even when the Python code works with both. Solution: Add 'pyxversion', :pyx, etc. (Marc Weber, Ken Takata) https://github.com/vim/vim/commit/f42dd3c3901ea0ba38e67a616aea9953cae81b8d
* vim-patch:91f84f6e11cdJustin M. Keyes2018-10-29
| | | | | Update runtime files. https://github.com/vim/vim/commit/91f84f6e11cd879d43d651c0903d85bff95f0716
* vim-patch:675e8d6adb88Justin M. Keyes2018-10-29
| | | | | | | | | | | | Update runtime files. https://github.com/vim/vim/commit/675e8d6adb88d5b38087870dfda51c0205070741 --- NA: vim-patch:ffd112edc6a8 Fix missing patch number. https://github.com/vim/vim/commit/ffd112edc6a8f72b66c06207bff4431f6aec7b6f
* vim-patch:22f1d0e35eb0Justin M. Keyes2018-10-28
| | | | | | | Updated runtime files. Add Serbian translations and spell checking. https://github.com/vim/vim/commit/22f1d0e35eb0e503c2dc7813a973c7e6ca1b7dde
* vim-patch:a2a80162deb1Justin M. Keyes2018-10-28
| | | | | Update runtime files. https://github.com/vim/vim/commit/a2a80162deb1e96e16b097dfe48b61b6eb0824bf
* Merge #4486 'refactor: Remove maxmem, maxmemtot options'Justin M. Keyes2018-05-02
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | After this change we never release blocks from memory (in practice it never happened because the memory limits are never reached). Let the OS take care of that. --- On today's systems the 'maxmem' and 'maxmemtot' values are huge (4+ GB) so the limits are never reached in practice, but Vim wastes a lot of time checking if the limit was reached. If the limit is reached Vim starts saving pieces of the swap file that were in memory to the disk. Said in a different way: Vim implements its own memory-paging mechanism. This is unnecessary and inefficient since the operating system already has virtual memory and will swap to the disk if programs start using too much memory. This change does... 1. Reduce the number of config options and need for documentation. 2. Make the code more efficient as we don't have to keep track of memory usage nor check if the memory limits were reached to start swapping to disk every time we need memory for buffers. 3. Simplify the code. Once memfile.c is simple enough it could be replaced by actual operating system memory mapping (mmap, MemoryViewOfFile...). This change does not prevent Vim to recover changes from swap files since the swapping code is never triggered with the huge limits set by default.
| * Remove maxmem and maxmemtot optionsFelipe Oliveira Carvalho2017-04-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | > The option 'maxmem' ('mm') is used to set the maximum memory used for one > buffer (in kilobytes). 'maxmemtot' is used to set the maximum memory used for > all buffers (in kilobytes). The defaults depend on the system used. These > are not hard limits, but tell Vim when to move text into a swap file. If you > don't like Vim to swap to a file, set 'maxmem' and 'maxmemtot' to a very large > value. The swap file will then only be used for recovery. If you don't want > a swap file at all, set 'updatecount' to 0, or use the "-n" argument when > starting Vim. On today's systems these values are huge (4GB in my machine with 8GB of RAM since it's set as half the available memory by default) so the limits are never reached in practice, but Vim wastes a lot of time checking if the limit was reached. If the limit is reached Vim starts saving pieces of the swap file that were in memory to the disk. Said in a different way: Vim implements its own memory swapping mechanism. This is unnecessary and inefficient since the operating system already virtualized the memory and will swap to the disk if programs start using too much memory. This change does... 1. Reduce the number of config options and need for documentation. 2. Make the code more efficient as we don't have to keep track of memory usage nor check if the memory limits were reached to start swapping to disk every time we need memory for buffers. 3. Simplify the code. Once `memfile.c` is simple enough it could be replaced by actual operating system memory mapping (`mmap`, `MemoryViewOfFile`...). This change does not prevent Vim to recover changes from swap files since the swapping code is never triggered with the huge limits set by default.
* | defaults: enable 'cscopeverbose', and deprecate itJustin M. Keyes2018-01-21
| |
* | vim-patch:8.0.0420: text garbled when the system encoding differs from ↵James McCoy2017-12-17
| | | | | | | | | | | | | | | | | | | | 'encoding' Problem: When running :make the output may be in the system encoding, different from 'encoding'. Solution: Add the 'makeencoding' option. (Ken Takata) https://github.com/vim/vim/commit/2c7292dc5bbf155fe2192d417363b8c085759cad
* | vim-patch:74675a666b51Justin M. Keyes2017-11-07
| | | | | | | | | | | | Updated runtime files and translations. https://github.com/vim/vim/commit/74675a666b51edd61e0210132658d81a86c5102c
* | doc: deprecate 'highlight'; remove howto.txt (#7497)Justin M. Keyes2017-11-07
| |
* | options: remove ghost of `:set termcap` (#7102)Justin M. Keyes2017-07-31
| | | | | | Closes #6763
* | doco: Replace termcap with terminfo where appropriate.Jonathan de Boyne Pollard2017-06-03
| | | | | | | | Also document better what to do on slow terminals.
* | doc: Replace hardcoded TOCs with <M-]> advice.Justin M. Keyes2017-05-01
| |
* | vim-patch:bc2eada5424bJustin M. Keyes2017-05-01
| | | | | | | | | | | | | | | | | | | | | | | | | | Updated runtime files. https://github.com/vim/vim/commit/bc2eada5424bff06f7eb77c032ecc067da52b846 NA patches: vim-patch:294740d2ac42 vim-patch:a4ce25bd987a vim-patch:7034a8374345 vim-patch:14a612fa2e57 vim-patch:aaeabfbca571
* | vim-patch:e4a3bcf28d92Justin M. Keyes2017-04-19
|/ | | | | | Updated runtime files. Add Scala files. https://github.com/vim/vim/commit/e4a3bcf28d92d0bde9ca227ccb40d401038185e5
* options: remove 'guiheadroom'Justin M. Keyes2017-04-04
|
* doc: Replace "For Vim ... Last change ..." headers (#6328)Justin M. Keyes2017-03-21
|
* options: Remove 'esckeys' (#6138)Justin M. Keyes2017-02-18
| | | This was never supported and it does not make sense for Nvim.
* vim-patch:a02a551James McCoy2017-02-01
| | | | | | Updated runtime files. https://github.com/vim/vim/commit/a02a551e18209423584fcb923e93c6be18f3aa45
* vim-patch:0952131James McCoy2016-12-28
| | | | | | Updated runtime files. https://github.com/vim/vim/commit/0952131376a517fc12dc5ae908a97018b4ee23f0
* vim-patch:03413f4James McCoy2016-07-08
| | | | | | | | | | | | | Updated runtime files. https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf Ignore changes to * doc/Makefile, doc/help.txt: Related to Vim's version8 documentation * doc/gui_x11.txt, doc/todo.txt, doc/vim.1, gvim.desktop, vim.desktop: Irrelevant to Neovim * doc/quickref.txt, doc/options.txt: As of yet unported 'emoji' * doc/tags, syntax/vim.vim: Generated at build time
* vim-patch:f391327James McCoy2016-07-08
| | | | | | | | | | | Updated runtime files. https://github.com/vim/vim/commit/f391327adbbffb11180cf6038a92af1ed144e907 Ignore changes to * doc/todo.txt: Irrelevant for Neovim * doc/channel.txt: Channel docs * doc/tags, syntax/vim.vim: Generated at build time
* vim-patch:b4ff518KillTheMule2016-05-03
| | | | | | | | | | Updated runtime files. https://github.com/vim/vim/commit/b4ff518d95aa57c2f8c0568c915035bef849581b Missing files: runtime/doc/tags, runtime/doc/todo.txt. Changes to runtime/doc/if_pyth.txt, runtime/doc/options.txt and runtime/doc/quickref.txt did not aply. Excluded runtime/syntax/vim.vim.
* Merge pull request #4273 from watiko/vim-7.4.957Justin M. Keyes2016-04-25
|\ | | | | vim-patch:7.4.{941,942,957}
| * vim-patch:7.4.941watiko2016-03-06
| | | | | | | | | | | | | | Problem: There is no way to ignore case only for tag searches. Solution: Add the 'tagcase' option. (Gary Johnson) https://github.com/vim/vim/commit/0f6562e9036f889185dff49a75c7fc5ffb28b307
* | vim-patch:f913281watiko2016-03-29
|/ | | | | | Updated and new runtime files. https://github.com/vim/vim/commit/f91328100db34996ed7e7a800bed0a30ff0890dd
* doc: cleanup. #4032 #4033Seth Jackson2016-01-16
|
* doc: Remove more references to MS-DOSSeth Jackson2016-01-16
| | | | | | Among other things, this includes: - lies about command.com - references to pcterm
* Merge pull request #4009 from sethjackson/swapsyncMichael Reed2016-01-14
|\ | | | | [RFC] Remove 'swapsync'
| * Remove swapsync.Seth Jackson2016-01-14
| | | | | | | | It's complete overkill.
* | doc: Remove references to GTK.Seth Jackson2016-01-14
|/ | | | We don't support it.
* Remove 'restorescreen' optionSeth Jackson2016-01-08
| | | | | | | The relevant code was never actually in Neovim, most likely due to being unifdef(1)'d out during the initial import. see `:h hidden-options'
* Remove 'antialias' remnantsMichael Reed2015-11-25
| | | | It never did anything (see `:h hidden-options`).
* documentation: Update documentationZyX2015-10-23
| | | | | | | Note about ~/.local/share/nvim/site used in one usr_\* file: this one talks about user-local installation of third-party plugins, and ~/.local/share/nvim/site is the proper place for them. Most other files talk about user own configuration and this is ~/.config.
* Deprecate &viminfo and :[rw]v, add &shada and :[rw]shZyX2015-10-08
|
* documentation: Update documentationZyX2015-10-08
|
* doc: mark 'toolbar' and 'toolbariconsize' as removed.Jakob Schnitzer2015-09-17
| | | | | These options have been removed from the code, so also mark them as removed in the docs
* Remove 'guipty' referencesMichael Reed2015-07-04
| | | | | | | | Presumably due to tarruda's unifdefing, it was already a no-op at the time of nvim's first commit. It's probably better to be clear that it doesn't exist, as opposed to users thinking `:set guipty` is doing something when it isn't.
* doc: Remove gui_x11.txt, merge remnants into nvim_clipboard.txtMichael Reed2015-07-04
| | | | We've never had an X11 GUI.
* doc: Misc. X11-related cleanupsMichael Reed2015-06-01
| | | | | | | These were all introduced by the previous commit, and spotted with with `make html` in `runtime/doc`. [ci skip]
* vim-patch:f654ad9 #2659Perry Hung2015-05-20
| | | | | | | | Update runtime files. https://code.google.com/p/vim/source/detail?r=f654ad95fd4e25e014dda71963b9745a4bf5f83b Resolves issue #1999.
* vim-patch:4abac79 #2694Florian Walch2015-05-19
| | | | | | Update runtime files. https://code.google.com/p/vim/source/detail?r=4abac79c0b7ae7aac0cb32d9930e155de628b63f
* Remove `-T` command-line optionMichael Reed2015-05-18
| | | | | | | It didn't actually do anything after 3baba1e7bc6698e6bc9f1d37fce88b30d6274bc9 Helped-by: Justin M. Keyes <justinkz@gmail.com>
generated by cgit (git 2.34.1) at 2025-08-07 18:17:52 +0000