aboutsummaryrefslogtreecommitdiff
path: root/docs/user/manual.adoc
Commit message (Collapse)AuthorAgeFilesLines
* update vim ycm installation instructionPSeitz2021-03-291-15/+2
|
* Mention the rustup version in the manualLaurențiu Nicola2021-03-271-0/+9
|
* Fix manual description for rust_project.jsonThiébaud Weksteen2021-03-251-1/+1
|
* Apply suggestions from code reviewAleksey Kladov2021-03-221-2/+2
| | | Co-authored-by: Laurențiu Nicola <[email protected]>
* Update docs/user/manual.adocAleksey Kladov2021-03-221-1/+1
| | | Co-authored-by: bjorn3 <[email protected]>
* Document our security stanceAleksey Kladov2021-03-221-0/+14
| | | | changelog: feature
* Update docs/user/manual.adocAleksey Kladov2021-03-181-1/+1
|
* Update info about Eclipse CorrosionMickael Istria2021-03-181-4/+2
|
* Fix remaining references to `cargo xtask codegen`Lukas Wirth2021-03-121-1/+1
|
* Add a line about code action commands to the CoC section of the docsFlorian Diebold2021-03-061-0/+2
|
* Fix typo.boxdot2021-02-241-1/+1
|
* 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
|
* Update remaining serverPath referencesLaurențiu Nicola2021-01-071-2/+2
|
* 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
|
* 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
|
* 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-091-0/+9
|
* docs: Update Neovim nvim-lspconfig repository linkDave Lage2020-10-291-2/+2
|
* Add generated diagnostic docs to the manualFlorian Diebold2020-10-221-0/+7
|
* 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
| |
* | Allow redirecting logs to a specific fileAleksey Kladov2020-08-261-1/+1
|/ | | | | There's a surprising lack of crates which are like env_logger, but also allow writing to a file. Let's write our own then!
* Add sysroot shortcut to rust-project.jsonAleksey Kladov2020-08-251-3/+13
|
* Improve loggingAleksey Kladov2020-08-251-0/+2
|
* minorAleksey Kladov2020-07-241-1/+1
|
* Merge #5473bors[bot]2020-07-231-5/+28
|\ | | | | | | | | | | | | | | 5473: Changes to rust-project.json r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * Apply suggestions from code reviewAleksey Kladov2020-07-211-4/+4
| | | | | | Co-authored-by: Laurențiu Nicola <[email protected]>
| * Document new rust-project.json formatAleksey Kladov2020-07-211-5/+28
| |
* | Update manual.adocVeetaha2020-07-221-2/+2
|/
* Merge #5407bors[bot]2020-07-161-0/+19
|\ | | | | | | | | | | | | | | | | 5407: Mentioned problem matchers and running cargo-watch as a VS Code Task r=matklad a=Michael-F-Bryan See https://github.com/rust-analyzer/rust-analyzer/issues/3596#issuecomment-658887055. Co-authored-by: Michael-F-Bryan <[email protected]> Co-authored-by: Michael Bryan <[email protected]>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-29 07:19:17 +0000