| Commit message (Collapse) | Author | Age |
... | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Nvim has no direct integration with X.
Helped-by: Florian Walch <florian@fwalch.com>
|
|/ / /
| | |
| | |
| | |
| | | |
This is primarily low-hanging fruit; there are still many references to
things such as MS-DOS throughout (see os_dos.txt).
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | | |
Tests currently time out and will be fixed by @tarruda in a future PR.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* Functional tests fail with SIGPIPE: disable them until we
figure out the exact problem.
* MSan reports some warnings: allow failures for the Travis
build to allow fixing them in individual follow-up PRs.
|
| | | | |
|
| | | | |
|
| | | | |
|
|/ / / |
|
|\ \ \
| | | |
| | | | |
[RDY] Doc cleanup (4) - clipboard docs + various
|
| | | |
| | | |
| | | |
| | | | |
Nvim hasn't ever had X11 integration, so this has was never needed.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
|/ / /
| | |
| | |
| | | |
We've never had an X11 GUI.
|
| | |
| | |
| | |
| | |
| | | |
This occured when clipboard=unnamedplus and doing "+p in visual mode.
Fixes #2942.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Using e.g. a Linux distribution's package manager should be preferred
over installing the `neovim` Python modules with `pip`.
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Extract the RBuffer class from rstream.c and reimplement it as a ring buffer,
a more efficient version that doesn't need to relocate memory.
The old rbuffer_read/rbuffer_write interfaces are kept for simple
reading/writing, and the RBUFFER_UNTIL_{FULL,EMPTY} macros are introduced to
hide wrapping logic when more control is required(such as passing the buffer
pointer to a library function that writes directly to the pointer)
Also add a basic infrastructure for writing helper C files that are only
compiled in the unit test library, and use this to write unit tests for RBuffer
which contains some macros that can't be accessed directly by luajit.
Helped-by: oni-link <knil.ino@gmail.com>
Reviewed-by: oni-link <knil.ino@gmail.com>
Reviewed-by: Scott Prager <splinterofchaos@gmail.com>
Reviewed-by: Justin M. Keyes <justinkz@gmail.com>
Reviewed-by: Michael Reed <m.reed@mykolab.com>
|
| | |
| | |
| | |
| | |
| | | |
Libuv will return 0 to signal that the buffer allocated by `alloc_cb` wasn't
used, and in this case the read_cb should simply be ignored.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- Add `kl_shift_at` macro and backing function. This can be used to shift
elements at arbitrary positions. `kl_shift` is now defined on top of the new
macro.
- Change shift/push API, now `kl_push` accepts an object as parameter and
`kl_shift` returns the object instead of a status. An assertion against
shifting at the end of a list(or empty lists) was added.
- Add `kl_iter` and `kl_iter_at` macros. `kl_iter_at` is for starting the
iteration at arbitrary positions.
|
| | |
| | |
| | |
| | |
| | |
| | | |
This event loop is just a stub instance used in synchronous libuv function
calls, it needs to be decoupled from the main event loop in order to run it from
another thread.
|
| | |
| | |
| | |
| | |
| | | |
The python3 emulation layer doesn't work well enough to run that test. Also add
notes to test86/test87 explaining why.
|
|/ /
| |
| |
| |
| | |
Remove helpers.vim_init and simply perform the required initialization in
helpers.lua.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Arguments passed to xmemdupz() are sometimes NULL, but xmemdupz() has
FUNC_ATTR_NONNULL_ALL. Check pointers for NULL before calling
xmemdupz().
Resolves #2533.
|
|\ \
| |/
|/|
| |
| |
| | |
[RFC] Update vimrc_example file and remove gvimrc_example file
Reviewed-by: Michael Reed <m.reed@mykolab.com>
Reviewed-by: Justin M. Keyes <justinkz@gmail.com>
|
| | |
|
|/
|
|
|
| |
Because of recent work on defaults (see
https://github.com/neovim/neovim/issues/2676)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem : Argument with 'nonnull' attribute passed null @ 203.
Diagnostic : False positive.
Rationale : Problem is supposed to appear when argv[0] is NULL within
do_os_system. But argv is being generated by
shell_build_argv(), which implies argv[0] is the current
value for 'shell' option. Now, option has a non-null
default ($SHELL or "sh"), and, if set by the user, it can
be empty, but not NULL. So, argv[0] can never be NULL.
Resolution : Assert shell_build_argv() postcondition.
|
|
|
|
|
|
|
| |
Re: compatibility issues with users doing `:so
$VIMRUNTIME/macros/matchit.vim`
Fixes #2918
|
|
|
|
|
| |
- It's severely outdated
- We already have (up to date) installation instructions on the wiki
|
|\
| |
| |
| |
| | |
[RFC] clint.py stuff
Reviewed-by: Florian Walch <florian@fwalch.com>
|
| |
| |
| |
| |
| | |
It unnecessarily complicates spotting linter errors, as they're usually
surrounded by a bunch of lines saying "Done processing ... ".
|
|/
|
|
|
|
|
|
|
| |
a) It's not an error
b) It requires manual redirection of stderr into stdout ('2>&1') in
order to be viewed with a pager, which it warrants given how long the
help message is.
Helped-by: Florian Walch <florian@fwalch.com>
|
|
|
|
|
| |
igor(1) checks if the document date is today, so this should prevent
forgetting to bump the date in the future.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
abort() causes a bad exit; retry uv_loop_close() instead.
Before this change, this ruby script will cause nvim to abort() instead
of exiting cleanly:
```
require 'open3'
require 'base64'
Open3.popen3('nvim --embed -u -NONE') {|stdin, stdout, stderr, wait_thr|
# base64-encoded msgpack message for the vim_command "qa!".
stdin.write Base64.decode64('kwKrdmltX2NvbW1hbmSRo3FhIQ==')
puts wait_thr.value
}
```
References ##2663
Closes #2466
Closes #2648
Helped-by: Rui Abreu Ferreira <raf-ep@gmx.com>
|
|\
| |
| |
| | |
clipboard'.
|
| |
| |
| |
| |
| |
| | |
Fixes #2712
Helped-By: Michael Reed <m.reed@mykolab.com>
|
| |
| |
| |
| | |
Helped-By: Justin M. Keyes <justinkz@gmail.com>
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
`nvim-[lang].1`:
The non-english manuals are completely outdated and still written in
roff, as opposed to mdoc, which is used for `nvim.1`.
Given that, they're nearly useless at the moment, and when/if they are
updated, they should probably be rewritten from scratch using `nvim.1`
as a reference.
`xxd*.1`:
xxd hasn't been in the source tree for a long time, so the manual is of
little use.
`nvimtutor*.1`:
The vimtutor script hasn't ever shipped with nvim, and the consensus
seems to be that it won't, at least in the form of an executable
installed alongside `$(PREFIX)/bin/nvim` (see #2700).
In `nvim.1`, the argument to the `.Os` macro was removed. This was done
because its only purpose was to signify that nvim and nvimtutor
were part of the "Neovim" distribution, i.e., one and the same, which
isn't applicable anymore because `nvimtutor.1` is being removed.
From the `.Os` documentation in `man mdoc`:
Os
Operating system version for display in the page footer. This is the
mandatory third macro of any mdoc file. Its syntax is as follows:
.Os [system [version]]
The optional system parameter specifies the relevant operating system or
environment. It is suggested to leave it unspecified, in which case
mandoc(1) uses its -Ios argument or, if that isn't specified either,
sysname and release as returned by uname(3).
Examples:
.Os
.Os KTH/CSC/TCS
.Os BSD 4.3
See also Dd and Dt.
Reviewed-by: Felipe Morales <hel.sheep@gmail.com>
Reviewed-by: Florian Walch <florian@fwalch.com>
Reviewed-by: Justin M. Keyes <justinkz@gmail.com>
[ci skip]
|
| |
|
| |
|
|
|
|
| |
Closes #2816
|
|
|
|
|
|
|
|
|
| |
refs #2895
Helped-by: Bohr Shaw <pubohr@gmail.com>
Helped-by: Justin M. Keyes <justinkz@gmail.com>
[ci skip]
|
|
|
|
|
|
| |
In general, attempt to make things more concise.
Reviewed-by: Michael Reed <m.reed@mykolab.com>
|
| |
|
| |
|
|\ |
|