| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
| |
We have two ways to disable third-party/
1. make USE_BUNDLED_DEPS=OFF
2. cmake USE_BUNDLED=OFF
The example used the make option in a cmake context.
|
| |
|
|
|
|
|
|
| |
The main purpose of this build-type was to avoid unwanted ~/.nvimlog
files (which could get really big, and also affects performance) for
non-devs. But that is no longer necessary since the log system now
avoids non-critical logging by default (#6827).
This essentially reverts 87e5a4131666e44354f280538cbc6bbe52225092
|
| |
|
|
|
|
| |
- Establish ERROR log level as "critical". Such errors are rare and will
be valuable when users encounter unusual circumstances.
- Set -DMIN_LOG_LEVEL=3 for release-type builds
|
| |
|
|
|
|
|
|
| |
- Remove some unnecessary code: IsHeaderFile is no longer required, as the logic
to find flags to headers is now built into YCM
- Add function to make paths in flags absolute: It seems YCM is not correctly
resolving paths in flags to consider `build` as the compiler working
directory.
- Update documentation.
|
| | |
|
| |
|
|
|
|
| |
This reverts commit c13f72ee0a6600963a10e57155d2e814d56599e2.
References #5447.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
We use a Makefile which in turn uses cmake. If we wanted to set the install
prefix for cmake, we had to do this so far:
make CMAKE_FLAGS="-DCMAKE_INSTALL_PREFIX=/tmp/nvim"
That's long and hard to remember. Following the conventions of other Makefiles,
this now works as well and is equivalent:
make PREFIX=/tmp/nvim
|
| | |
|
| |
|
|
|
|
|
| |
- Check if MIN_LOG_LEVEL value is a number 0-3, default to
INFO (1) or ignore it in Release mode
- When TRAVIS_CI_BUILD is ON the default is DEBUG (0)
- Add local.mk.example
|
| |
|
|
|
| |
It hasn't been used in quite a while, so it's probably safe to move it
out of the repository root.
|
| |
|
|
|
|
|
|
|
|
| |
"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.
|
| |
|
|
| |
This setup is only meant for developers, not all users of YCM.
|
| |
|
|
|
|
| |
Introduce new build type Dev that replaces RelWithDebInfo for development
builds off master and has optimizations, debug info, and logging enabled.
Keep assertions enabled for RelWithDebInfo.
|
| |
|
|
|
|
|
|
| |
This doesn't prevent compilation of jemalloc, but the important thing is
that it prevents it being used in nvim.
refs 6cd20177df9d675c4c8de9ae27ce8c0ea2a94cca
refs 95707bf336794c7ec8991917f184c02ae873dd8c
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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).
|
| | |
|
| |
|
|
|
|
|
| |
DUSE_JEMALLOC was removed in 8130eb1191aece52d8b2790302abf1bd09aaf90f
Helped-by: Florian Walch <florian@fwalch.com>
Helped-by: John Szakmeister <john@szakmeister.net>
|
| | |
|
| |
|
|
|
| |
- Mention how to disable jemalloc during compilation
- Mention using additional CFLAGS during compilation
|
| |
|
|
|
|
| |
This library makes it easier to script communication with interactive programs.
It is similar to what the "expect" tcl extension does, but uses an object
oriented API and is designed to integrate nicely with Neovim job control.
|
| |
|
|
| |
[ci skip]
|
| |
|
|
| |
[ci skip]
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem: YCM was reporting a much disturbing warning about a missing
newline at the end of some files. This was odd, as the
newlines were there and the warning only was shown for some
files, not for all of them.
Cause: After discussing this issue with @Valloric (see
https://github.com/Valloric/YouCompleteMe/issues/950), it
turned out that not YCM, but libclang is responsible for it.
This is, same compilation flags that produce no warnings with
clang-the-binary on the command line, do produce them with
libclang-the-library when used by YCM.
Solution: Add an extra flag (-Wno_newline_eof) to those extracted from
configuration database before passing them to YCM.
|
| |
|
|
| |
some icon images in the html are replaced with css.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Python-mode signaled a couple of issues here:
- Multiple imports on same line.
- Line too long.
|
| |
|
|
| |
Build directory calculation had not been correctly updated in #716.
|
| |
|
|
| |
- Fix instructions to install youcompleteme configuration.
|
| |
|
