aboutsummaryrefslogtreecommitdiff
path: root/runtime
Commit message (Collapse)AuthorAge
...
| * | shada: Do not save unlisted and quickfix buffersZyX2015-11-23
| | | | | | | | | Fixes #3635
* | | Merge pull request #3741 from Pyrohh/doc-rm-todoMichael Reed2015-11-27
|\ \ \ | | | | | | | | [RFC] doc: Remove todo.txt
| * | | doc: Remove todo.txtMichael Reed2015-11-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It's not documentation in the same sense as the majority of files in runtime/doc, so is of little use to most users and should probably not be installed alongside the "real" documentation. It may be full of good ideas, but it's also full of things which are no longer applicable to Nvim, such as references to platforms we no longer support (e.g., MS-DOS), Vi compatibility, Autoconf, the Perl interface, etc. If someone is looking for things to fix or improve, the GitHub issue tracker should prove useful, and, unlike todo.txt, the issues are generally much more relevant to Nvim. Besides all that, removing todo.txt makes porting runtime patches a bit easier. refs #2911, discussed briefly in #2608 and #2553
* | | | Remove 'antialias' remnantsMichael Reed2015-11-25
|/ / / | | | | | | | | | It never did anything (see `:h hidden-options`).
* | | doc/vi_diff.txt: Remove unneeded opening paragraphMichael Reed2015-11-24
| | | | | | | | | | | | | | | | | | | | | All `{not in Vi}' tags have been removed, so the first sentence is no longer true. As for the second sentence, the header ("Differences between Vim and Vi") is already self-explanatory, so it can be removed as well.
* | | doc/vi_diff.txt: Remove remaining "{Vi: ...}" noteMichael Reed2015-11-24
| | | | | | | | | | | | We don't care about Vi here, only Vim.
* | | doc: Remove some Vi-compatibility stuffMichael Reed2015-11-24
| | | | | | | | | | | | | | | This stuff is no longer relevant, as we don't care about Vi compatibility just for the sake of it.
* | | doc/develop.txt: Remove "coding-style" sectionMichael Reed2015-11-24
| | | | | | | | | | | | | | | By and large, it's very outdated, and we already have a style guide available online (see CONTRIBUTING.md).
* | | doc/develop.txt: Mention src/nvim/README.mdMichael Reed2015-11-24
| | |
* | | doc/develop.txt: Remove "design-assumptions" sectionMichael Reed2015-11-24
| | | | | | | | | | | | | | | | | | | | | We don't make such assumptions; new code should use fixed-width integer types [1]. [1]: https://neovim.io/develop/style-guide.xml?showone=Integer_Types#Integer_Types
* | | Merge pull request #3624 from Pyrohh/vi_diffMichael Reed2015-11-23
|\ \ \ | | | | | | | | [RFC] vi_diff.txt pruning
| * | | doc: vi_diff: Remove 'Missing options' sectionMichael Reed2015-11-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The compatibility stubs for these options were removed in [1], so this section is nearly useless. [1]: cc76c5b0cfb6233ff36949a4422d59cd4bc6efd5
| * | | doc: vi_diff: Remove 'Other vim features' sectionMichael Reed2015-11-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These are more like notes than proper documentation, so remove it as they're not of much use unless you don't know what you're looking for. Many of these are somewhat useful, but many also duplicate what's already documented elsewhere. In any case, vi_diff.txt is the last place that assorted tips'n'tricks should be located (we already have tips.txt!!!).
| * | | doc: vi_diff: Remove 'Command line arguments' sectionMichael Reed2015-11-23
| | | | | | | | | | | | | | | | | | | | | | | | In regards to Nvim, it's very outdated; for an updated list of such arguments refer to the manual page or `nvim --help`. In all other regards, it's of little to no use to end-users.
| * | | doc: Remove stray {not in Vi} tagMichael Reed2015-11-23
| |/ / | | | | | | | | | This was missed in 818f7aefd2fe7eacd7135c5e3154934f24c85ca7
* / / shada: Also store last search directionZyX2015-11-23
|/ / | | | | | | | | | | | | | | | | | | Note: it looks like viminfo files do not store search direction intentionally. After reading viminfo file search direction was considered to be “forward”. Note 2: all files created on earlier Neovim version will automatically receive “forward” direction. Fixes #3580
* | Merge pull request #3270 from ZyX-I/shada-supportFelipe Morales2015-11-23
|\ \ | |/ |/| Add plugin for editing ShaDa files
| * documentation: Add documentation on shada pluginZyX2015-11-01
| |
| * documentation: Add documentation for autoload/msgpack.vimZyX2015-11-01
| |
| * runtime: Add shada.vim syntax fileZyX2015-11-01
| |
| * runtime: Add [ft]plugin/shada.vim files that automatically open .shadaZyX2015-11-01
| |
| * runtime: Add autoload/shada.vim helper fileZyX2015-11-01
| | | | | | | | Contains most of the logic
| * runtime: Add autoload/msgpack.vim helper fileZyX2015-11-01
| |
* | Add TermClose eventMarco Hinz2015-11-15
| | | | | | | | | | | | | | | | A terminal buffer now exits with: [Process exited <return value>] You can hook into it. E.g. :au TermClose * call feedkeys('<cr>') Closes #2293.
* | vim_diff: Fix incorrect ShaDa pathJohannes Löthberg2015-11-14
| | | | | | | | Signed-off-by: Johannes Löthberg <johannes@kyriasis.com>
* | Doc: minor fix for ":ls u"Bohr Shaw2015-11-12
| | | | | | | | | | | | This fixes a typo that was already contained in the original Vim patch: https://github.com/vim/vim/commit/d51cb706a4e3ae99555bc214a64c83603c701139
* | Merge pull request #3651 from mhinz/remove-nvimrc-refsJustin M. Keyes2015-11-11
|\ \ | | | | | | Remove all invalid nvimrc references
| * | Remove all invalid nvimrc and ngvimrc referencesMarco Hinz2015-11-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | "vimrc" refers to all files that are used to configure Neovim. The main configuration file is init.vim nowadays. All nvimrc references that are left refer to a local ".nvimrc" which is read if 'exrc' is set. ".ngvimrc" references were completely wiped. Closes #3552.
* | | vim-patch:7.4.791 #3078Marco Hinz2015-11-11
| | | | | | | | | | | | | | | | | | | | | | | | Problem: The buffer list can be very long. Solution: Add an argument to ":ls" to specify the type of buffer to list. (Marcin Szamotulski) https://github.com/vim/vim/commit/d51cb706a4e3ae99555bc214a64c83603c701139
* | | Merge pull request #3652 from Pyrohh/rm-os-macMichael Reed2015-11-11
|\ \ \ | | | | | | | | [RDY] Remove os_mac.txt
| * | | doc: Nuke os_mac.txtMichael Reed2015-11-11
| |/ / | | | | | | | | | | | | | | | Pretty much all of this stuff is outdated. Reviewed-by: @justinmk
* / / Be more explicit about the lack of X11 integrationMichael Reed2015-11-10
|/ / | | | | | | | | I don't want anyone getting the idea that the `-X` flag they might have used has anything to do with why the `+` is working for them
* | Add file selection prompt on ":oldfiles!"Marco Hinz2015-11-10
| | | | | | | | | | | | | | | | :browse was removed for good, but some people miss ":browse oldfiles". The same functionality is now provided by ":oldfiles!". Helped-by: @Pyrohh
* | Add ":profile stop"Marco Hinz2015-11-10
| | | | | | | | This writes the logfile and stops profiling.
* | Add ":profile dump"Marco Hinz2015-11-10
| | | | | | | | | | Currently the logfile (":profile start {logfile}") only gets written when Vim exits. This new command allows to dump the log immediately without exiting.
* | eval: Implement dictionary change notificationsThiago de Arruda2015-11-09
| |
* | vim-patch:7.4.686 #3629Johan Klokkhammer Helsing2015-11-08
| | | | | | | | | | | | | | | | Problem: "zr" and "zm" do not take a count. Solution: Implement the count, restrict the fold level to the maximum nesting depth. (Marcin Szamotulski) https://github.com/vim/vim/commit/7d2757a47204d00cd47e3db94f1bd248c499d4e3
* | Update runtime/syntax/css.vimMarco Hinz2015-11-08
| | | | | | | | This file was missing from the previous runtime update (975a610).
* | vim-patch:f2571c6Marco Hinz2015-11-08
| | | | | | | | | | | | Update runtime files. References #3625.
* | Merge pull request #3622 from Sean1708/patch-1Michael Reed2015-11-07
|\ \ | | | | | | [RFC] Fix doc discrepancy in 'complete' defaults.
| * | doc: Remove example in 'complete' doc.Sean Marshallsay2015-11-07
| | | | | | | | | | | | | | | The example needlessly replicates information and using the defaults causes discrepancies to occur over time.
* | | Remove :open commandMichael Reed2015-11-07
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | From the documentation itself: :[range]o[pen] Works like |:visual|: end Ex mode. {Vi: start editing in open mode} ... Vim does not support open mode, since it's not really useful. For those situations where ":open" would start open mode Vim will leave Ex mode, which allows executing the same commands, but updates the whole screen instead of only one line. Part of the reason behind this is to make removing vi_diff.txt easier, although it's also because :open is not too useful. Helped-by: @fdinoff Helped-by: @dsummersl Helped-by: @mhinz Helped-by: @justinmk
* | doc: remove balloon options. #3524Victor Adam2015-11-07
| |
* | docJustin M. Keyes2015-11-07
| | | | | | | | | | | | | | | | - design-not. Closes #2940 - :terminal - vim_diff: 'termencoding' footnote - 'shada'. Closes #3619 - eval.txt: job* functions list. Closes #3222
* | runtime/autoload/provider/python{,3}.vim: fix E168Daniel Hahler2015-11-03
|/ | | | Do not use `finish` inside of `provider#python{,3}#Call`, but `return`.
* Merge pull request #3570 from srobbibaro/srobbibaro/doc-updateMichael Reed2015-10-31
|\ | | | | [RFC] Update terminal documentation for clarity
| * Update terminal documentation for claritySteve Robbibaro2015-10-31
| | | | | | | | | | | | A couple lines tripped me up while reading through this document for the first time. This change aims to reword/rework these areas, so that they are clearer on the first read.
* | doc: Fix lint warningMichael Reed2015-10-31
| | | | | | | | found with `gmake html'
* | doc: Nuke os_unix.txtMichael Reed2015-10-31
|/ | | | | | | | All of this information is a combination of incorrect, outdated, or redundant given its availability in other help files. Reviewed-by: Justin M. Keyes <justinkz@gmail.com> Reviewed-by: Felipe Morales <hel.sheep@gmail.com>
* documentation: Fix &undodir defaultZyX2015-10-30
|