| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
Problem: Crash with pattern: \(\)\{80000} (Dominique Pelle)
Solution: When the max limit is large fall back to the old engine.
https://github.com/vim/vim/commit/a1d2c58985584116d20fa5e132137d8ff1a535f7
|
|\
| |
| | |
tutor: Fix mistaken option name
|
|/
|
| |
Closes #3754
|
|\
| |
| | |
src/*: Remove `VIM - Vi improved ...` header
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Regarding the individual items in the header:
`Vim - Vi improved by Bram Moolenar`
Bram Moolenar is already mentioned throughout the documentation, as
well as the intro screen.
`:help uganda`
It's already shown to all users who don't use `shortmess+=I` upon
starting nvim, and is already placed prominently in help.txt, i.e.,
`:help` run with no arguments.
`:help credits`
Already mentioned near the top of help.txt.
`README.md`
Already mentioned in develop.txt.
|
|\ \
| | |
| | | |
tutor: Update vim-tutor to 0.2.1
|
| | |
| | |
| | |
| | | |
Also, some tweaks based on input by @fdinoff on gitter.
|
|\ \ \
| |_|/
|/| | |
shada: Do not save unlisted and quickfix buffers
|
| | |
| | |
| | | |
Fixes #3635
|
|\ \ \
| | | |
| | | | |
[RFC] doc: Remove todo.txt
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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
|
| | | |
| | | |
| | | |
| | | | |
MinGW already has a redefine for ssize_t.
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
[RFC] Cleanup use of os_* functions errors and errno
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
In Windows we can't assume errno will be set by calls to os_* functions,
instead the return value from os_* functions can be used. This commit fixes two
occurences for os_open().
1. EFBIG is replaced with UV_EFBIG and checked against the return from os_open().
2. EOVERFLOW does not have a corresponding libuv constant, and is not defined
by open() in Windows - disabled this case with a UNIX guard, and check the return
value against -EOVERFLOW (libuv errors are negative errno values in Unix).
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
From #3473, shada.c used errno constants (e.g. ENOENT) to check the return
of os_open(), but in Windows the return from libuv functions is not -errno.
Instead use libuv error constants (e.g UV_ENOENT) for error checks.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Replaced old unit tests for errno with libuv error codes UV_ENOENT
and UV_EEXIST (for os_open and os_getperms).
Added libuv include path to test/includes compiler calls - needed
to get hold of libuv headers.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Previously os_getperms() returned -1 for any error condition, it
now returns the libuv error code (as returned by os_stat()). This
allows checking for error conditions without relying on errno
(which not available in Windows).
The only case where the errno value from os_getperms() was being used
was in readfile() to set the new-file flag - replaced the errno check
with UV_ENOENT.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Instead of returning bool from os_stat return the actual libuv return code.
This function is static and used internally in nvim/os/fs.c it should not
impact the rest of the API. This is a first step to change other fs functions.
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | | |
In windows libuv does not return -errno, instead it uses negative
error codes e.g. UV_ENOENT. This commit changes the comments in os_*
functions to reflect this.
|
| | | | |
|
|\ \ \ \
| |/ / /
|/| | | |
[RFC] Remove 'antialias' remnants
|
|/ / /
| | |
| | |
| | | |
It never did anything (see `:h hidden-options`).
|
|\ \ \
| | | |
| | | | |
[RFC] doc: More vi_diff.txt cleanup
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| | | |
| | | |
| | | |
| | | | |
We don't care about Vi here, only Vim.
|
|/ / /
| | |
| | |
| | |
| | | |
This stuff is no longer relevant, as we don't care about Vi
compatibility just for the sake of it.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | | |
[RFC] doc/develop.txt pruning
Reviewed-by: Felipe Morales < hel DOT sheep AT gmail DOT com >
Reviewed-by: Marco Hinz < mh DOT codebro AT gmail DOT com >
|
| | | |
| | | |
| | | |
| | | |
| | | | |
By and large, it's very outdated, and we already have a style guide
available online (see CONTRIBUTING.md).
|
| | | | |
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
|\ \ \
| | | |
| | | | |
[RFC] src: README.txt -> README.md
|
|/ / /
| | |
| | |
| | |
| | | |
The former no longer exists in this repo; see the top of
src/nvim/README.md.
|
|\ \ \
| | | |
| | | | |
Update .gitignore
|
|/ / /
| | |
| | |
| | | |
refs #3687
|
|\ \ \
| | | |
| | | | |
[RFC] vi_diff.txt pruning
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The compatibility stubs for these options were removed in [1], so this
section is nearly useless.
[1]: cc76c5b0cfb6233ff36949a4422d59cd4bc6efd5
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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!!!).
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| | | |
| | | |
| | | |
| | | | |
This was missed in 818f7aefd2fe7eacd7135c5e3154934f24c85ca7
|
|\ \ \ \
| |/ / /
|/| | | |
Store last search direction when writing ShaDa files
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
|\ \ \ |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Source: https://github.com/mpeterv/luacheck
Docs: http://luacheck.readthedocs.org/en/0.12.0/index.html
Run via "make testlint".
|
|/ / / |
|
|\ \ \
| |/ /
|/| | |
|