aboutsummaryrefslogtreecommitdiff
path: root/docs/user
Commit message (Collapse)AuthorAgeFilesLines
* Snippetify fix_visibilityAleksey Kladov2020-05-201-1/+1
|
* Snippetify fill_match_armsAleksey Kladov2020-05-201-1/+1
|
* Split change_ and fix_ visibility assistsAleksey Kladov2020-05-201-0/+22
|
* Use snippets in change_return_type_to_resultAleksey Kladov2020-05-201-1/+1
|
* Snippetify add_newAleksey Kladov2020-05-201-1/+1
|
* Better cursor placement when adding impl membersAleksey Kladov2020-05-201-2/+2
|
* Use snippets in add_missing_membersAleksey Kladov2020-05-201-2/+2
|
* Use snippets in add functionAleksey Kladov2020-05-201-1/+1
|
* New assist: add turbo fishAleksey Kladov2020-05-191-0/+18
|
* Add snippet support for some assistsAleksey Kladov2020-05-191-5/+5
|
* Relax VS Code version requirementAleksey Kladov2020-05-171-1/+1
|
* Update features.mdCoenen Benjamin2020-05-121-2/+12
|
* Use RA_LOG instead of RUST_LOG for loggingAleksey Kladov2020-05-111-1/+1
| | | | | | RUST_LOG might be set up for debugging the user's problem, slowing down rust-analyzer considerably. That's the same reason why rustc uses RUSTC_LOG.
* Merge #4333bors[bot]2020-05-061-15/+8
|\ | | | | | | | | | | | | | | | | | | | | | | 4333: Update Arch Linux and ALE install instructions r=matklad a=polyzen Package has been added to the Arch repos: https://www.archlinux.org/packages/community/x86_64/rust-analyzer/ ALE merged rust-analyzer support: https://github.com/dense-analysis/ale/commit/70005134e5b2d40d176ee5b851ac64a296b22201 Co-authored-by: Daniel M. Capella <[email protected]>
| * Update Arch Linux and ALE install instructionsDaniel M. Capella2020-05-051-15/+8
| | | | | | | | | | | | | | | | Package has been added to the Arch repos: https://www.archlinux.org/packages/community/x86_64/rust-analyzer/ ALE merged rust-analyzer support: https://github.com/dense-analysis/ale/commit/70005134e5b2d40d176ee5b851ac64a296b22201
* | Fix Windows server pathLaurențiu Nicola2020-05-061-1/+1
| | | | | | CC @Coder-256.
* | add Ok wrappingBenjamin Coenen2020-05-061-0/+12
|/ | | | Signed-off-by: Benjamin Coenen <[email protected]>
*-. Merge #4306 #4308bors[bot]2020-05-051-1/+5
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4306: Make incremental sync opt-out and fix line index rebuild r=matklad a=lnicola 4308: Update server binary paths in docs r=matklad a=Coder-256 Fixed incorrect macOS path and converted to a list. Also, should the Windows path include `matklad.rust-analyzer`? (I can't check) Co-authored-by: Laurențiu Nicola <[email protected]> Co-authored-by: Jacob Greenfield <[email protected]>
| | * Update server binary pathsJacob Greenfield2020-05-041-1/+5
| |/ | | | | Fixed macOS path and converted to a list
* / [manual] Improve requirements and editor wordingFrancisco Lopes2020-05-041-3/+3
|/
* Merge branch 'master' of github.com:rust-analyzer/rust-analyzerBenjamin Coenen2020-05-022-2/+13
|\
| * Add missing members generates indented blocksAleksey Kladov2020-05-021-1/+3
| |
| * Document Gnome Builder supportLaurențiu Nicola2020-05-011-1/+10
| |
* | Merge branch 'master' of github.com:rust-analyzer/rust-analyzerBenjamin Coenen2020-05-012-8/+25
|\|
| * Update readme.adochafiz2020-04-301-2/+2
| |
| * Fix typo in language server binary docshafiz2020-04-301-1/+1
| |
| * docs(user): method chaining hints supportHeyward Fann2020-04-301-2/+4
| | | | | | | | https://github.com/fannheyward/coc-rust-analyzer/issues/177#issuecomment-621109410
| * Fix Typos on features.mdKENTARO OKUDA2020-04-291-2/+2
| |
| * Fix YouComplteMe instructions linkBoris Staletic2020-04-291-1/+1
| |
| * add ale to the nvim setup section of the readmeSimon Cruanes2020-04-291-0/+15
| |
* | Add unwrap block assist #4156Benjamin Coenen2020-04-291-2/+2
| | | | | | | | Signed-off-by: Benjamin Coenen <[email protected]>
* | Add unwrap block assist #4156Benjamin Coenen2020-04-291-0/+18
|/ | | | Signed-off-by: Benjamin Coenen <[email protected]>
* Add missing .Günter Zöchbauer2020-04-261-1/+1
|
* Change install directory suggestion to `~/.local/bin`Günter Zöchbauer2020-04-261-3/+5
| | | instead of `~/.cargo/bin`
* xtask does not need to be installedGünter Zöchbauer2020-04-261-4/+1
| | | because it's contained in the dart-analyzer repo.
* Clarify rust-analyzer binary installGünter Zöchbauer2020-04-261-7/+23
|
*-. Merge #3998 #4006bors[bot]2020-04-241-2/+2
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3998: Make add_function generate functions in other modules via qualified path r=matklad a=TimoFreiberg Additional feature for #3639 - [x] Add tests for paths with more segments - [x] Make generating the function in another file work - [x] Add `pub` or `pub(crate)` to the generated function if it's generated in a different module - [x] Make the assist jump to the edited file - [x] Enable file support in the `check_assist` helper 4006: Syntax highlighting for format strings r=matklad a=ltentrup I have an implementation for syntax highlighting for format string modifiers `{}`. The first commit refactors the changes in #3826 into a separate struct. The second commit implements the highlighting: first we check in a macro call whether the macro is a format macro from `std`. In this case, we remember the format string node. If we encounter this node during syntax highlighting, we check for the format modifiers `{}` using regular expressions. There are a few places which I am not quite sure: - Is the way I extract the macro names correct? - Is the `HighlightTag::Attribute` suitable for highlighting the `{}`? Let me know what you think, any feedback is welcome! Co-authored-by: Timo Freiberg <[email protected]> Co-authored-by: Leander Tentrup <[email protected]> Co-authored-by: Leander Tentrup <[email protected]>
| * | Make add_function generate functions in other modules via qualified pathTimo Freiberg2020-04-211-2/+2
| | |
* | | Add YouCompleteMe as a LSP option for vim/neovimWeihang Lo2020-04-231-0/+20
|/ /
* | docs(readme): improve user docsHeyward Fann2020-04-211-2/+2
| | | | | | | | cleanup unavailable configurations/commands
* | Move the PATH issue up to the non-editor specific sectionNikolai Morin2020-04-211-1/+3
| |
* | Delete commaNikolai Morin2020-04-211-1/+1
| |
* | Update docs/user/readme.adocNikolai Morin2020-04-211-1/+1
| | | | | | Co-Authored-By: Laurențiu Nicola <[email protected]>
* | Update docs/user/readme.adocNikolai Morin2020-04-211-1/+1
| | | | | | Co-Authored-By: Laurențiu Nicola <[email protected]>
* | More detailed Sublime Text install instructionsNikolai Morin2020-04-211-14/+23
|/ | | | | * People might typically jump directly to their editor and wonder where the part about installing rust-analyzer is – at least I did. I added a link to the relevant section for ST. * Make ST instructions more detailed and user friendly (especially beginners), include troubleshooting tips. * Minor grammar improvements throughout.
* Change add_function assist to use todo!()Timo Freiberg2020-04-131-1/+1
|
* Merge #3925bors[bot]2020-04-111-0/+15
|\ | | | | | | | | | | | | | | | | | | 3925: Implement assist "Reorder field names" r=matklad a=geoffreycopin This PR implements the "Reorder record fields" assist as discussed in issue #3821 . Adding a `RecordFieldPat` variant to the `Pat` enum seemed like the easiest way to handle the `RecordPat` children as a single sequence of elements, maybe there is a better way ? Co-authored-by: Geoffrey Copin <[email protected]>
| * Generate docGeoffrey Copin2020-04-111-0/+15
| |
* | Change missing impl assist to use todo!() instead of unimplemented()Chris Hopman2020-04-101-1/+1
|/ | | | | | | | | | | | todo!() "Indicates unfinished code" (https://doc.rust-lang.org/std/macro.todo.html) Rust documentation provides further clarification: > The difference between unimplemented! and todo! is that while todo! > conveys an intent of implementing the functionality later and the > message is "not yet implemented", unimplemented! makes no such claims. todo!() seems more appropriate for assists that insert missing impls.
* Better Sublime documentationElinvynia2020-04-081-24/+1
|