Remove obsolete notes in documentation

This commit is contained in:
micbou 2017-09-17 03:43:57 +02:00
parent b358b5ba8a
commit 8817bc1f25
No known key found for this signature in database
GPG Key ID: C7E8FD1F3BDA1E05
2 changed files with 0 additions and 44 deletions

View File

@ -1406,20 +1406,6 @@ For example:
Invoking this command on `s` returns `std::string => std::basic_string<char>` Invoking this command on `s` returns `std::string => std::basic_string<char>`
**NOTE:** Due to limitations of `libclang`, invoking this command on the word
`auto` typically returns `auto`. However, invoking it on a usage of the variable
with inferred type returns the correct type, but typically it is repeated due to
`libclang` returning that the types differ.
For example:
```c++
const char *s = "String";
auto x = &s; // invoking on x or auto returns "auto";
// invoking on s returns "const char *"
std::cout << *x; // invoking on x returns "const char ** => const char **"
```
**NOTE:** Causes re-parsing of the current translation unit. **NOTE:** Causes re-parsing of the current translation unit.
Supported in filetypes: `c, cpp, objc, objcpp, javascript, typescript` Supported in filetypes: `c, cpp, objc, objcpp, javascript, typescript`
@ -1527,15 +1513,6 @@ indication).
**NOTE:** Causes re-parsing of the current translation unit. **NOTE:** Causes re-parsing of the current translation unit.
**NOTE:** After applying a fix-it, the diagnostics UI is not immediately
updated. This is due to a technical restriction in Vim. Moving the cursor, or
issuing the `:YcmForceCompileAndDiagnostics` command will refresh the
diagnostics. Repeated invocations of the `FixIt` command on a given line,
however, _do_ apply all diagnostics as expected without requiring refreshing of
the diagnostics UI. This is particularly useful where there are multiple
diagnostics on one line, or where after fixing one diagnostic, another fix-it is
available.
Supported in filetypes: `c, cpp, objc, objcpp, cs` Supported in filetypes: `c, cpp, objc, objcpp, cs`
#### The `RefactorRename <new name>` subcommand #### The `RefactorRename <new name>` subcommand

View File

@ -1690,18 +1690,6 @@ For example:
< <
Invoking this command on 's' returns 'std::string => std::basic_string<char>' Invoking this command on 's' returns 'std::string => std::basic_string<char>'
**NOTE:** Due to limitations of 'libclang', invoking this command on the word
'auto' typically returns 'auto'. However, invoking it on a usage of the
variable with inferred type returns the correct type, but typically it is
repeated due to 'libclang' returning that the types differ.
For example:
>
const char *s = "String";
auto x = &s; // invoking on x or auto returns "auto";
// invoking on s returns "const char *"
std::cout << *x; // invoking on x returns "const char ** => const char **"
<
**NOTE:** Causes re-parsing of the current translation unit. **NOTE:** Causes re-parsing of the current translation unit.
Supported in filetypes: 'c, cpp, objc, objcpp, javascript, typescript' Supported in filetypes: 'c, cpp, objc, objcpp, javascript, typescript'
@ -1814,15 +1802,6 @@ indication).
**NOTE:** Causes re-parsing of the current translation unit. **NOTE:** Causes re-parsing of the current translation unit.
**NOTE:** After applying a fix-it, the diagnostics UI is not immediately
updated. This is due to a technical restriction in Vim. Moving the cursor, or
issuing the |:YcmForceCompileAndDiagnostics| command will refresh the
diagnostics. Repeated invocations of the |FixIt| command on a given line,
however, _do_ apply all diagnostics as expected without requiring refreshing of
the diagnostics UI. This is particularly useful where there are multiple
diagnostics on one line, or where after fixing one diagnostic, another fix-it
is available.
Supported in filetypes: 'c, cpp, objc, objcpp, cs' Supported in filetypes: 'c, cpp, objc, objcpp, cs'
------------------------------------------------------------------------------- -------------------------------------------------------------------------------