aboutsummaryrefslogtreecommitdiff
path: root/docs
Commit message (Collapse)AuthorAgeFilesLines
* Merge #9264bors[bot]2021-06-211-5/+10
|\ | | | | | | | | | | | | | | | | | | 9264: feat: Make documentation on hover configurable r=Veykril a=Veykril This also implements deprecation support for config options as this renames `hoverActions_linksInHover` to `hover_linksInHover`. Fixes #9232 Co-authored-by: Lukas Wirth <[email protected]>
| * Remove deprecation support in configLukas Wirth2021-06-211-5/+0
| |
| * Add configuration deprecationLukas Wirth2021-06-141-0/+5
| |
| * Make documentation on hover configurableLukas Wirth2021-06-141-5/+10
| |
* | Merge #9227bors[bot]2021-06-211-0/+5
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 9227: Add a config setting to disable the 'test' cfg in specified crates r=matklad a=lf- If you are opening libcore from rust-lang/rust as opposed to e.g. goto definition from some other crate which would use the sysroot instance of libcore, a `#![cfg(not(test))]` would previously have made all the code excluded from the module tree, breaking the editor experience. Core does not need to ever be edited with `#[cfg(test)]` enabled, as the tests are in another crate. This PR puts in a slight hack that checks for the crate name "core" and turns off `#[cfg(test)]` for that crate. Fixes #9203 Fixes #9226 Co-authored-by: Jade <[email protected]>
| * | Implement a config override for the default #[cfg(test)] in cargo cratesJade2021-06-191-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | Fixes crates which vanish when the 'test' cfg atom is set. Fix #7243. Fix #9203. Fix #7225.
* | | add note about passing cfg(debug_assertions)rezural2021-06-201-0/+5
|/ / | | | | add note about passing cfg(debug_assertions) to rustc on build. The server will not spin without this arcane hack
* | Allow to disable import insertion on single path glob importsLukas Wirth2021-06-181-0/+5
| |
| |
| \
*-. \ Merge #9267 #9279bors[bot]2021-06-152-3/+18
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 9267: fix: Code: update the LSP server without asking r=matklad a=lnicola Most LSP extensions seem to do the same thing, and this is causing some confusion for users who don't notice the update prompt before Code hides it. 9279: minor: Document installation via Homebrew r=matklad a=Svetlitski `rust-analyzer` can be installed via [Homebrew](https://brew.sh) (AKA`brew`) on macOS. I've added instructions on how to do so to the documentation. Additionally, I added a `.gitignore` rule to ignore the HTML documentation produced by `asciidoctor manual.adoc` so that it is not accidentally checked into `git`. Co-authored-by: Laurențiu Nicola <[email protected]> Co-authored-by: Kevin Svetlitski <[email protected]> Co-authored-by: Aleksey Kladov <[email protected]>
| | * | Update docs/user/manual.adocAleksey Kladov2021-06-151-1/+1
| | | |
| | * | Document installation via Homebrew; Add gitignore entry for asciidoctor outputKevin Svetlitski2021-06-142-0/+10
| | |/
| * / Consolidate the privacy notesLaurențiu Nicola2021-06-151-3/+8
| |/
* / internal: document that we don't #[ignore] testsAleksey Kladov2021-06-151-0/+7
|/
* Fix typo in env-var quotingJade2021-06-141-1/+1
|
* Further clarificationFlorian Diebold2021-06-071-1/+2
|
* One additional grammar fixFlorian Diebold2021-06-071-1/+1
|
* Clarify label documentationFlorian Diebold2021-06-071-7/+8
| | | Also some other cleanups while I'm there.
* Add function references hover actionLukas Wirth2021-06-041-0/+6
|
* Make it opt-inJonas Schievink2021-06-031-0/+5
|
* manual.adoc: add Gentoo Linux installation methodmjkalyan2021-06-031-0/+14
| | | Added installation instructions for the binary ebuild of the "latest" `rust-analyzer` in Gentoo's GURU repository.
* Document that `addCallArgumentSnippets` requires `addCallParenthesisLukas Wirth2021-06-021-0/+1
|
* minor: expand docs a tiny bitAleksey Kladov2021-05-311-0/+3
|
* Add config setting for self-on-the-flyLukas Wirth2021-05-312-0/+11
|
* Fix incorrect setting descriptionsLucas Schwiderski2021-05-291-6/+6
| | | | | | | | Descriptions for diagnostic warning hint and info display were swapped. Fixes #8485. Signed-off-by: Lucas Schwiderski <[email protected]>
* internal: explain the motivation behind early configurationAleksey Kladov2021-05-271-6/+12
|
* Merge #8767bors[bot]2021-05-251-0/+7
|\ | | | | | | | | | | | | | | | | | | | | | | 8767: implement range formatting r=matklad a=euclio Fixes #7580. This PR implements the `textDocument/rangeFormatting` request using `rustfmt`'s `--file-lines` option. Still needs some tests. What I want to know is how I should handle the instability of the `--file-lines` option. It's still unstable in rustfmt, so it's only available on nightly, and needs a special flag to enable. Is there a way for `rust-analyzer` to detect if it's using nightly rustfmt, or for users to opt-in? Co-authored-by: Andy Russell <[email protected]>
| * implement range formattingAndy Russell2021-05-231-0/+7
| |
* | Update download instructionsLaurențiu Nicola2021-05-241-4/+4
| |
* | docs: fix binary installation instructionsChristoph Schmatzler2021-05-241-1/+1
|/ | | | issue #8926 removed uncompressed release artifacts. This updates the documentation to update instructions accordingly.
* docs(manual): Add rust-tools.nvim to nvim-lspsim2021-05-231-0/+2
|
* Update lsp-extensions.mdJonas Schievink2021-05-211-2/+18
|
* Update outdated auto-import documentationLukas Tobias Wirth2021-05-201-1/+1
|
* Merge #8873bors[bot]2021-05-201-2/+7
|\ | | | | | | | | | | | | | | | | | | | | | | 8873: Implement import-granularity guessing r=matklad a=Veykril This renames our `MergeBehavior` to `ImportGranularity` as rustfmt has it as the purpose of them are basically the same. `ImportGranularity::Preserve` currently has no specific purpose for us as we don't have an organize imports assist yet, so it currently acts the same as `ImportGranularity::Item`. We now try to guess the import style on a per file basis and fall back to the user granularity setting if the file has no specific style yet or where it is ambiguous. This can be turned off by setting `import.enforceGranularity` to `true`. Closes https://github.com/rust-analyzer/rust-analyzer/issues/8870 Co-authored-by: Lukas Tobias Wirth <[email protected]>
| * Replace ImportGranularity::Guess with guessing boolean flagLukas Tobias Wirth2021-05-191-2/+7
| |
* | feat: allow clients to feature detect symbol filteringAleksey Kladov2021-05-191-12/+16
| |
* | Add new LSP extension for workspace symbol lookupalcroito2021-05-172-1/+41
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The new extension allows filtering of workspace symbool lookup results by search scope or search kind. Filtering can be configured in 3 different ways: - The '#' or '*' markers can be added inline with the symbol lookup query. The '#' marker means symbols should be looked up in the current workspace and any dependencies. If not specified, only current workspace is considered. The '*' marker means all kinds of symbols should be looked up (types, functions, etc). If not specified, only type symbols are returned. - Each LSP request can take an optional search_scope or search_kind argument query parameter. - Finally there are 2 global config options that can be set for all requests served by the active RA instance. Add support for setting the global config options to the VSCode extension. The extension does not use the per-request way, but it's useful for other IDEs. The latest version of VSCode filters out the inline markers, so currently the only reasonable way to use the new functionality is via the global config.
* minor: adjust config nameAleksey Kladov2021-05-172-13/+14
|
* Merge #8795bors[bot]2021-05-171-0/+9
|\ | | | | | | | | | | | | | | | | | | 8795: Allow semantic tokens for strings to be disabled r=matklad a=djrenren Fixes https://github.com/rust-analyzer/rust-analyzer/issues/7111 Pretty straightforward change, but open to any suggestions if there's a more recommended testing strategy than what I went with. Co-authored-by: John Renner <[email protected]>
| * Formatting and docsJohn Renner2021-05-101-0/+9
| |
* | minor: and one more recipe for aceAleksey Kladov2021-05-171-0/+1
| |
* | internal: remove one more immutable treeAleksey Kladov2021-05-141-0/+22
| |
* | Cleanup importsAleksey Kladov2021-05-131-0/+7
| |
* | Document viewCrateGraph requestJonas Schievink2021-05-111-1/+11
| |
* | Update docsLukas Wirth2021-05-101-1/+1
| |
* | fix: fix manual renderingAleksey Kladov2021-05-101-1/+0
| | | | | | | | We add `// see the other repo` comments before headers (==). This one isn't a header, but a closing of the example block.
* | feat: make troubleshooting a top-level sectionAleksey Kladov2021-05-081-35/+35
| |
* | feat: friendlier trouble shooting guideAleksey Kladov2021-05-081-8/+32
| |
* | docs: Add Kate installation sectionMéven Car2021-05-081-0/+27
| |
* | fix: direct people to the right repositoryAleksey Kladov2021-05-071-2/+0
|/
* internal: explain why sentence-per-lineAleksey Kladov2021-05-061-1/+1
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-17 11:00:22 +0000