aboutsummaryrefslogtreecommitdiff
path: root/runtime
Commit message (Collapse)AuthorAge
* memline: Automatically create swap file directory for last directoryZyX2015-10-23
|
* main,version: Remove USR_EXRC_FILE*ZyX2015-10-23
|
* 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.
* option: Use proper printexprZyX2015-10-23
|
* vim-patch:7.4.793Johan Klokkhammer Helsing2015-10-18
| | | | | | | Problem: Can't specify when not to ring the bell. Solution: Add the 'belloff' option. (Christian Brabandt) https://github.com/vim/vim/commit/165bc69d1b7f70ca9d5b657f35d0584ecb7b5183
* Merge pull request #2506 from ZyX-I/shadaJustin M. Keyes2015-10-16
|\ | | | | Replace viminfo with ShaDa files
| * documentation: Disambiguate ShaDa abbreviationZyX2015-10-08
| |
| * shada: When using shada-r normalize option pathZyX2015-10-08
| |
| * shada: First write temporary file and only then check any permissionsZyX2015-10-08
| | | | | | | | | | | | It is not logical that on UNIX permissions can prevent even writing temporary file, while on other OS it will first write temporary file and then fail during rename.
| * documentation: Extend shada error handling documentationZyX2015-10-08
| |
| * documentation/functests: Replace NeoVim with NeovimZyX2015-10-08
| |
| * shada: Add generator key to the headerZyX2015-10-08
| | | | | | | | | | For use in viminfo→shada converters, plugins that allow editing ShaDa files or any other software which generates ShaDa files for whatever purpose.
| * documentation: Update vim differences list, reference critical errorsZyX2015-10-08
| |
| * documentation: Add extended ShaDa format descriptionZyX2015-10-08
| |
| * documentation: Describe forward compatibility limitationsZyX2015-10-08
| |
| * shada,documentation: Extend read error handling, handle write errorsZyX2015-10-08
| | | | | | | | | | | | | | | | Modifications: - If file was not written due to write error then writing stops and temporary file will not be renamed. - If NeoVim detects that target file is not a ShaDa file then temporary file will not be renamed.
| * documentation: Document ShaDa compatibility featuresZyX2015-10-08
| |
| * shada: Translate errors and add error codesZyX2015-10-08
| | | | | | | | | | | | | | | | | | | | Notes: - E136 code greatly changed its meaning: now it is write error and not read error. - E195 was removed because shada_read_everything will already do all the necessary error reporting. - E886 can be reported by both :rshada and :wshada, but :rshada comes first and AFAIR it is the only error which is not E575 and can be reported by :rshada.
| * documentation: Document how ShaDa entries should be mergedZyX2015-10-08
| |
| * Deprecate &viminfo and :[rw]v, add &shada and :[rw]shZyX2015-10-08
| |
| * Replace references to viminfo in various placesZyX2015-10-08
| |
| * documentation: Update documentationZyX2015-10-08
| |
| * viminfo: First version of ShaDa file dumpingZyX2015-10-08
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | What works: 1. ShaDa file dumping: header, registers, jump list, history, search patterns, substitute strings, variables. 2. ShaDa file reading: registers, global marks, variables. Most was not tested. TODO: 1. Merging. 2. Reading history, local marks, jump and buffer lists. 3. Documentation update. 4. Converting some data from &encoding. 5. Safer variant of dumping viminfo (dump to temporary file then rename). 6. Removing old viminfo code (currently masked with `#if 0` in a ShaDa file for reference).
* | doc: drop obsolete 'langnoremap' section. #3448Ben Noordhuis2015-10-11
| | | | | | | | | | | | | | | | | | | | Commit e3568364 ("default: enable 'langnoremap'. #2853") enabled it by default but forgot to remove the lines saying it's disabled by default. tweaked by Michael Reed Reviewed-by: Felipe Morales <hel.sheep@gmail.com> [ci skip]
* | vim-patch:8feef4f #3444rosston2015-10-11
|/ | | | | | Update runtime files. https://github.com/vim/vim/commit/8feef4ff6253afb9dcc61c40082ed4fbb96b685c
* api: represent api type String as msgpack type STR. closes #1250Björn Linse2015-10-08
|
* eval/string(): Share code between msgpackdump() and string()+:echoZyX2015-09-30
|
* tutor-mode: update pluginFelipe Morales2015-09-27
|
* defaults: revert wildmode to 'full'Felipe Morales2015-09-26
|
* man.vim: Prevent sourcing in startup.Justin M. Keyes2015-09-25
| | | | | | | It is common practice for Vim users to :runtime! ftplugin/man.vim in order to get the :Man command. That will cause weird settings for non-man files.
* man.vim: avoid creating extra blank buffers.Justin M. Keyes2015-09-25
|
* man.vim: accept [count] for section number.Justin M. Keyes2015-09-23
|
* man.vim: window-local optionsJustin M. Keyes2015-09-23
| | | | | Set window-local options only on a newly-created "man" tab or if we're already in one.
* man.vim: man#get_page(): parse page and section.Justin M. Keyes2015-09-23
| | | | | - Eliminate man#pre_get_page(). - Temporarily remove () from 'iskeyword' to avoid spurious \k match.
* man.vim: convert ftplugin to actual plugin.Justin M. Keyes2015-09-23
| | | | | | | | | | | | | - do not create leader maps - :norm! instead of :norm - :keepjumps during layout - use blackhole reg to avoid polluting unnamed reg - format buffer name as "man://foo(2)" - simulate behavior of `man` - buffer-local mapping of q to quit - open in new tab instead of new window - set 'nolist' - set tabstop=8
* 'keywordprg': support ex commandsJustin M. Keyes2015-09-23
| | | | | | - new feature: if the first character of 'keywordprg' is ":", the command is invoked as a Vim ex-command prefixed with [count]. - change default 'keywordprg' to :Man
* Merge pull request #3353 from yagebu/docs-miscJustin M. Keyes2015-09-17
|\ | | | | docs cleanup: misc
| * options: unify undolevels defaultJakob Schnitzer2015-09-17
| | | | | | | | | | Considering Nvim's supported platforms, having a different default for (!Unix and !Windows) doesn't seem very useful.
| * 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
| * doc: feature-refs cleanupJakob Schnitzer2015-09-17
| |
* | provider/pythonx: Improve detection code and error messages.Florian Walch2015-09-17
|/ | | | | | | | | | | | | | | | | | | | | | | | | | "python -c" returns 1 in case of an error. Use a return code of 2 if the Neovim module is not found to distinguish these cases. Verify the interpreter version before checking for an installed Neovim module. Show a new error message if the Python interpreter version is below the minimum required version. Always use "pkgutil" to determine if the Neovim module is installed. In contrast to "importlib", which was used for Python 3, "pkgutil.find_loader" is available for all Python versions [1,2]. "pkgutil.find_loader" internally uses "importlib" for Python >= 3.3 [2]. Also, the previously used "importlib.find_loader" is only available since Python 3.3 (so checking the major Python version was not enough) and deprecated since Python 3.4 [3]. Finally, conditioning on the major version in Vimscript was incorrect, as checking the Neovim module for a certain Python major version does not mean that the tested interpreters are actually of that version. For example, we test the "python" executable, which is Python 2 on Ubuntu and Python 3 on Arch Linux. [1] https://docs.python.org/2/library/pkgutil.html#pkgutil.find_loader [2] https://docs.python.org/3/library/pkgutil.html#pkgutil.find_loader [3] https://docs.python.org/3/library/importlib.html#importlib.find_loader
* host.vim: expand $MYVIMRC. #3342Jonathan Skeate2015-09-14
| | | | | | | | | | | | According to the vim helpfile: > fnamemodify({fname}, {mods}) > ... > Note: Environment variables don't work in {fname}, use > expand() first then. So this causes issues if your $MYVIMRC contains environment variables (e.g. $XDG_CONFIG_HOME)
* python: remove current working directory from pathJakob Schnitzer2015-09-14
| | | | | | | | | | Before, running Nvim in a directory containing a Python module `neovim`, or one that is imported by it or a plugin, will load that module and not the system one. So Nvim might be tricked into running arbitrary scripts from the current working directory. Fixes #1665 Fixes #2530
* runtime: remove dvorak macro #3325Justin M. Keyes2015-09-10
| | | | | This macro does the same thing as `set keymap=dvorak`, so it serves no purpose.
* doc: 'encoding'Justin M. Keyes2015-09-09
|
* encoding: update docs for encodingBjörn Linse2015-09-08
| | | | | Helped-By: Michael Reed <m.reed@mykolab.com> Helped-By: Justin M. Keyes <justinkz@gmail.com>
* vim-patch:7.4.602oni-link2015-09-06
| | | | | | | Problem: ":set" does not accept hex numbers as documented. Solution: Use vim_str2nr(). (ZyX) https://github.com/vim/vim/commit/18400e6430755c97eb7e31525ab4744502603731
* doc: fix some typos in nvim docs #3280Aaron O'Leary2015-09-01
| | | | Reviewed-by: Michael Reed <Pyrohh@users.noreply.github.com>
* runtime: `::` token is valid in C#. #3144Jerome Leclanche2015-08-31
| | | | https://msdn.microsoft.com/en-us/library/c3ay4x3d.aspx
* runtime: fix for python highlighting #3154Victor Adam2015-08-31
| | | | | | | """\"""" was highlighted incorrectly. The fix is simply adding skip=+\\["']+ to the syntax of triple-quoted strings. Closes #3151
generated by cgit (git 2.34.1) at 2025-06-25 03:01:19 +0000