aboutsummaryrefslogtreecommitdiff
path: root/docs
Commit message (Collapse)AuthorAgeFilesLines
* 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
|
* simplify macro expansion codeAleksey Kladov2021-05-041-0/+33
| | | | | Using `Option` arguments such that you always pass `None` or `Some` at the call site is a code smell.
* Merge #8482bors[bot]2021-05-031-0/+35
|\ | | | | | | | | | | | | | | 8482: Mention how to customize unsafe operation styles r=matklad a=danielzfranklin I was confused about how to do this, so I filed #8474. I apologize for initially filing this incorrectly and spamming people. Co-authored-by: Daniel Franklin <[email protected]>
| * Merge with semantic style sectionDaniel Franklin2021-05-031-8/+25
| |
| * Mention how to customize unsafe operation stylesDaniel Franklin2021-04-121-0/+18
| | | | | | | | | | I was confused about how to do this, so I filed [an issue][issue]. [issue]: rust-analyzer/rust-analyzer#8474
* | internal: ensure that client and server-side configs are not mixed upAleksey Kladov2021-04-281-5/+0
| | | | | | | | https://github.com/rust-lang/rust/issues/84647 would help big time here.
* | Add config optionsJorge Mederos Alvarado2021-04-271-0/+5
| |
* | Merge #8605bors[bot]2021-04-221-6/+12
|\ \ | | | | | | | | | | | | | | | | | | | | | 8605: internal: Automatically categorize the changelog entries r=matklad a=lnicola Co-authored-by: Laurențiu Nicola <[email protected]>
| * | Automatically categorize the changelog entriesLaurențiu Nicola2021-04-201-6/+12
| | |
* | | Merge #8621bors[bot]2021-04-221-0/+4
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8621: feat: make sure nightly regressions don't break users r=lnicola a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | | feat: make sure nightly regressions don't break usersAleksey Kladov2021-04-221-0/+4
| |/ /
* | | Code review feedback.James Leitch2021-04-211-2/+2
| | |
* | | Diagnostic Remap Path Prefixes added.James Leitch2021-04-211-0/+6
|/ /
* | Merge #8598bors[bot]2021-04-201-26/+48
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | 8598: minor: fix ugly line wrapping in the rendered manual r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | minor: fix ugly line wrapping in the rendered manualAleksey Kladov2021-04-201-26/+48
| | |
* | | Merge #8588bors[bot]2021-04-191-0/+11
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | 8588: internal: Add guidelines for release notes PR descriptions r=matklad a=lnicola Co-authored-by: Laurențiu Nicola <[email protected]>
| * | internal: Add guidelines for release notes PR descriptionsLaurențiu Nicola2021-04-191-0/+11
| | |
* | | Remove confusion around serverStatusNotificationAleksey Kladov2021-04-191-3/+8
| | |
* | | Fix spec bugAleksey Kladov2021-04-191-1/+1
|/ /
* | Update docs/dev/README.mdAleksey Kladov2021-04-191-1/+1
| | | | | | Co-authored-by: Laurențiu Nicola <[email protected]>
* | internal: document review requesting etiquetteAleksey Kladov2021-04-191-0/+3
| | | | | | | | | | | | * don't feel obliged to quickly review every PR assigned to you * so that other folks can notify you about interesting PRs without thinking to much about creating additional work for you
* | Update lsp-extensions docsLukas Wirth2021-04-181-1/+2
| |
* | Fix markdown linksJonas Schievink2021-04-151-3/+3
| |
| |
| \
*-. \ Merge #8510 #8533bors[bot]2021-04-152-4/+4
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8510: Move cursor position when using item movers r=jonas-schievink a=jonas-schievink This updates the cursor position when moving items around to stay in the same location within the moved node. I changed the `moveItem` response to `SnippetTextEdit[]`, since that made more sense to me (the file was ignored by the client anyways, since the edits always apply to the current document). It also matches `onEnter`, which seems logical to me, but please let me know if this doesn't make sense. There's still a bug in the client-side snippet code that will cause the cursor position to be slightly off when moving parameters in the same line (presumably we don't track the column correctly after deleting `$0`). Not really sure how to fix that immediately, but this PR should already be an improvement despite that bug. 8533: Fix typo in style guide r=jonas-schievink a=jonas-schievink Fixes bold text rendering bors r+ Co-authored-by: Jonas Schievink <[email protected]>
| | * | Fix typo in style guideJonas Schievink2021-04-151-1/+1
| |/ / |/| |
| * | Move cursor position when using item moversJonas Schievink2021-04-131-3/+3
|/ /
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-04 21:32:08 +0000