aboutsummaryrefslogtreecommitdiff
path: root/docs/user
Commit message (Collapse)AuthorAgeFilesLines
* Revert "Support disabling rustc build scripts"Daniel McNab2021-03-081-2/+0
| | | | This reverts commit ddce6bb282764692d53b719bff4c37e3512d4556.
* Support disabling rustc build scriptsDaniel McNab2021-03-081-0/+2
|
* Add a line about code action commands to the CoC section of the docsFlorian Diebold2021-03-061-0/+2
|
* Migrate to user-centric config name for `cargo check` stuffAleksey Kladov2021-03-041-3/+3
|
* Fix typo.boxdot2021-02-241-1/+1
|
* Allow automatically detect the rustc-src directory (fixes #3517).Benjamin Bouvier2021-02-131-1/+1
| | | | | If the configured rustcSource is set to "discover", try to automatically detect a source from the sysroot rustc directory.
* Add emacs guideAleksey Kladov2021-02-081-0/+2
|
* Merge #7592bors[bot]2021-02-081-0/+10
|\ | | | | | | | | | | | | | | 7592: [Doc] Note about Eclipse IDE support r=lnicola a=mickaelistria Co-authored-by: Mickael Istria <[email protected]>
| * [Doc] Note about Eclipse IDE supportMickael Istria2021-02-081-0/+10
| |
* | Vim docs: vim-lsp with initial configuration.Ilya Bobyr2021-02-081-0/+46
| | | | | | | | | | | | `vim-lsp` is another popular LSP client for Vim. And, as there is no `rust-analyzer` specific UI, it is non-trivial to figure out how the initial configuration is performed.
* | Explain how initial configuration is sent over LSP.Ilya Bobyr2021-02-081-5/+27
|/
* Improve nvim-lsp setup instructionsLaurențiu Nicola2021-02-011-1/+34
|
* Add config option to ignore directoriesAleksey Kladov2021-01-261-0/+2
|
* Remove the need to manually sync config in package.jsonAleksey Kladov2021-01-261-4/+4
|
* Add References code lens.vsrs2021-01-231-0/+2
| | | | For Struct, Enum, Union and Trait symbols.
* Merge #7195bors[bot]2021-01-071-2/+2
|\ | | | | | | | | | | | | | | 7195: Update remaining serverPath references r=lnicola a=lnicola Fixes https://github.com/rust-analyzer/rust-analyzer/pull/7156#issuecomment-755487667 Co-authored-by: Laurențiu Nicola <[email protected]>
| * Update remaining serverPath referencesLaurențiu Nicola2021-01-071-2/+2
| |
* | Use american spelling for configAleksey Kladov2021-01-071-1/+1
|/ | | | | | | | As per https://github.com/rust-analyzer/rust-analyzer/blob/171c3c08fe245938fb25321394233de5fe2abc7c/docs/dev/style.md#variable-naming Also implement config aliasing, for pain-free settings migrations in the future
* More maintainable configAleksey Kladov2021-01-061-0/+2
| | | | | | | Rather than eagerly converting JSON, we losslessly keep it as is, and change the shape of user-submitted data at the last moment. This also allows us to remove a bunch of wrong Defaults
* Allow `#anchor` linking of config optionsAleksey Kladov2021-01-051-53/+53
|
* Merge #7113bors[bot]2021-01-031-0/+3
|\ | | | | | | | | | | | | | | | | | | 7113: Manual updates r=matklad a=tekul Add some details on how to build the manual and some clarification on how to deal with "proc macro2 warnings. For context, this arose from [this question](https://users.rust-lang.org/t/how-to-disable-rust-analyzer-proc-macro-warnings-in-neovim/53150) on users.rust-lang.org. Co-authored-by: Luke Taylor <[email protected]>
| * Expand contributing "tip" in manual.adocLuke Taylor2020-12-311-0/+3
| | | | | | | | | | | | - Add link to asciidoc website - Explain how to create the generated adoc files from the source code - How to run asciidoctor to generate the manual
* | Add support for Rust 2021.Mara Bos2021-01-011-1/+1
|/
* Update manual.adocHeyward Fann2020-12-241-1/+1
|
* Document, how to view config in effectAleksey Kladov2020-12-231-0/+3
|
* Clean up descriptions for settingsRüdiger Herrmann2020-12-221-13/+13
| | | | | | | | | | | | Use two consecutive newlines (`\n\n`) to actually continue text on a new line. Use proper markup to reference related settings. Consistently format references to files, editor commands, command line arguments, files, etc. as `code`. Fix typos, add missing full-stops, add missing default values.
* Split lines between sentencesLaurențiu Nicola2020-12-201-15/+27
|
* Document the version requirements for building from sourceLaurențiu Nicola2020-12-201-1/+1
|
* Link config sourceAleksey Kladov2020-12-141-0/+2
|
* Docs: Explain manual installation in VS CodeChristian Authmann2020-12-131-0/+17
|
* Use natural trait ordering in derive completionAleksey Kladov2020-12-111-119/+0
| | | | | | | | derive(Clone, Copy) reads better than derive(Copy, Clone). However, we preserve the reverse ordering in the lookup text for sorting purposes. That way, it's convenient to type just `Ord` to derive everything.
* Improve docs for building from sourceLaurențiu Nicola2020-12-101-1/+8
|
* Fix a typo in manual.adocJosh Stone2020-12-091-1/+1
|
* Include config into the manualAleksey Kladov2020-12-092-0/+115
|
* More accurately place proc-macro diagnosticJonas Schievink2020-11-271-1/+1
|
* Publish diagnostics for macro expansion errorsJonas Schievink2020-11-271-0/+14
|
* docs: Update Neovim nvim-lspconfig repository linkDave Lage2020-10-291-2/+2
|
* Fix name of InactiveCode diagnosticJonas Schievink2020-10-231-6/+6
|
* Diagnose #[cfg]s in bodiesJonas Schievink2020-10-231-4/+4
|
* Add generated diagnostic docs to the manualFlorian Diebold2020-10-221-0/+7
|
* add completions for clippy lint in attributesBenjamin Coenen2020-10-201-0/+105
| | | | Signed-off-by: Benjamin Coenen <[email protected]>
* Support Display name in project.jsonAleksey Kladov2020-10-201-0/+3
|
* Document logging of project modelAleksey Kladov2020-10-191-0/+1
|
* Update GNOME Builder docsLaurențiu Nicola2020-10-151-10/+1
|
* Update manual.adocAdrian Stanciu2020-10-061-0/+17
|
* Extend **Status** command to also show dep info for the fileAleksey Kladov2020-09-291-2/+2
| | | | This should help with troubleshooting wrong project configuration
* VS Code + WSL: describe binary locationMasaki Hara2020-09-211-0/+1
| | | It looks like VS Code server chooses a different location for `globalStorage`.
* docs: suggest disabling the official extensionJonas Schievink2020-09-181-0/+5
|
* Merge #5885bors[bot]2020-08-261-0/+24
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5885: Make inlay hints colors more configurable r=matklad a=Veetaha **[BREAKING CHANGE]** Tackles https://github.com/rust-analyzer/rust-analyzer/issues/5337#issuecomment-680018601 and generally related to #5337. Added `foreground/background` color configurations with optional more specific overrides `foreground.(type|parameter|chaining)Hints`. One problem I see is that the config keys are long and don't fit into the on-hover hints in the `settings.json` file entirely... <details> <summary>Demo</summary> ![demo](https://user-images.githubusercontent.com/36276403/91238334-77fc3b00-e745-11ea-836b-2822015ece98.gif) </details> Co-authored-by: Veetaha <[email protected]>
| * Make inlay hints colors more configurableVeetaha2020-08-261-0/+24
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-18 15:27:50 +0000