| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
| |
otherwise, system headers cannot be found on Mojave
they were moved from /usr/include to SDK path
|
|
|
|
|
| |
prevent luajit to assigning default value to MACOSX_DEPLOYMENT_TARGET
ref #9050
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the 20180331 release, the format was slightly changed:
> 20180331
> + improve terminfo write/read by modifying the fourth item of the
> extended header to denote the number of valid strings in the extended
> string table (prompted by a comment in unibilium's sources).
Since the number of valid string capabilities is not necessarily the
same as extstrslen, it's not possible to sanity check the total number
of items up front anymore.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- Since the jemalloc upgrade to 5.1.0, I'm seeing weird behavior such as
infinite loops inside jemalloc routines.
- VimR maintainer reported major performance regression correlated with
jemalloc 5.1.0.
ref https://github.com/neovim/neovim/pull/7808
reverts 765515010f8e60596ec67eb7cdfbe7f5e4e60c7d
|
|
|
|
|
| |
Not needed after libvterm commit:
https://github.com/neovim/libvterm/commit/487f21dbf65f1c28962fef3f064603f415fbaeb2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Changes: https://github.com/neovim/libvterm/compare/a9c7c6fd20fa...3f62ac6b7bdf
- "better handling of double-width unicode characters"
https://github.com/neovim/libvterm/commit/cfde7f2095f00fe3b54418af0b77d3f69c20f71e
https://github.com/neovim/neovim/issues/4976#issuecomment-418170022
- "Fix implementation of query on bracketed paste mode"
https://github.com/neovim/libvterm/commit/005845cd58ca409a970d822b74e1a02a503d32e7
- compiler-warning fixes
- FocusIn/FocusOut reporting
https://github.com/neovim/libvterm/commit/1343c8c0f9ebdc57ee31ca66e168da6d63a16522
Fixes #4976 (cursor "off-by-one" behavior after ⚡ (Wide unicode glyphs)
in :terminal)
|
|
|
|
| |
ref https://github.com/neovim/neovim/pull/7808
|
|
|
| |
ref https://github.com/equalsraf/neovim-qt/issues/417
|
| |
|
|
|
|
|
|
|
| |
2.8.12 is supported by our main CI targets and [repology] confirms that
this is broadly supported.
[repology]: https://repology.org/metapackage/cmake/information
|
| |
|
|
|
|
|
| |
Only includes the tools needed for Neovim: xgettext, msgfmt, and
msgmerge.
|
| |
|
|
|
|
|
|
| |
- We need the gettext tools (msgmerge.exe) because these aren't built
when we build from source (not trivial).
- We can use the pre-built libiconv-2.dll for DYNAMIC_ICONV_DLL.
|
|
|
|
|
| |
The escape sequence `\e` is non-standard and not supported by MSVC.
It caused the terminal emulator to incorrectly interpret certain keys.
|
| |
|
| |
|
|\ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|
|
|
|
|
|
| |
Upgrade msgpack so that Nvim 0.3.0 builds on gcc 8.
ref #7506
|
|
|
|
| |
Fixes abnormal terminaion when TERM environment variable
is set in Windows.
|
|
|
| |
This will be used e.g. by the python client for native asyncio support
|
|
|
|
|
|
|
| |
It's only appropriate to set CMAKE_MAKE_PROGRAM to gmake when we're
using the "Unix Makefiles" generator. On QB, the nodes have Ninja
available and will use it, which means CMAKE_GENERATOR is set to
"Ninja". Setting CMAKE_MAKE_PROGRAM was forcing the build to use gmake
instead of ninja, which was causing the build failure.
|
|
|
| |
fix #8216
|
|\
| |
| | |
closes #6659
|
| | |
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
On Windows the CMake script will replace the Perl script used by
Libvterm to generate headers.
|
|
|
|
|
| |
Adding a CMakeLists.txt for Libuv removes the need for Python
when building on Windows.
|
|
|
|
|
| |
The --ignore-whitespace argument was added when applying patches to
prevent failures when patched files have different line endings.
|
|
|
|
|
|
|
| |
Is there a race between the luarocks `make bootstrap` dependencies?
reverts f73b4911312b35bfe38ed068672a2f8ba8875ba7
ref https://github.com/luarocks/luarocks/pull/774
|
|
|
|
| |
upstream: https://github.com/luarocks/luarocks/pull/774
|
| |
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When building with CMAKE_BUILD_TYPE=Debug, the dependencies are built like this:
| Dep | Defaults | Debug |
|------------|-----------|---------------------------------------------|
| unibilium | `-O2` | `make CFLAGS=-O0 DEBUG=1` |
| msgpack | `-g -O3` | `cmake . -DCMAKE_C_FLAGS_DEBUG="-O0 -ggdb"` |
| libuv | `-g -O2` | `./configure CFLAGS="-O0 -ggdb"` |
| luv | `-g -O2` | `cmake . -DCMAKE_C_FLAGS_DEBUG="-O0 -ggdb"` |
| libvterm | not set | `make CFLAGS=-O0 DEBUG=1` |
| libtermkey | not set | `make CFLAGS=-O0 DEBUG=1` |
| jemalloc | `-g3 -O3` | `./configure CFLAGS="-O0 -ggdb"` |
| gperf | `-g -O2` | `./configure CXXFLAGS="-O0 -ggdb"` |
| luajit | `-g -O2` | haven't checked yet |
This means that only unibilium, libtermkey, and libvterm don't build with
debugging symbols by default.
Build them with debugging symbols and optimisations that don't hinder
debugging: -Og -g
|