Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update a few outdated links in docs #2287

Merged
merged 1 commit into from
Jun 12, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/src/customization.md
Original file line number Diff line number Diff line change
Expand Up @@ -103,7 +103,7 @@ If you use a custom color scheme, select `UI: Customize Color Scheme` from the C

Furthermore, it is possible to adjust the colors for semantic tokens by applying a foreground color to the individual token types:

| scope | [Semantic Token Type](https://microsoft.github.io/language-server-protocol/specifications/specification-3-17/#semanticTokenTypes) |
| scope | [Semantic Token Type](https://microsoft.github.io/language-server-protocol/specifications/specification-current/#semanticTokenTypes) |
| ----- | ------------------ |
| `meta.semantic-token.namespace` | namespace |
| `meta.semantic-token.type` | type |
Expand Down Expand Up @@ -133,7 +133,7 @@ By default, LSP will assign scopes based on the [scope naming guideline](https:/
Language servers can also add their custom token types, which are not defined in the protocol.
An "LSP-\*" helper package (or user) can provide a `semantic_tokens` mapping in the server configuration for such additional token types, or to override the scopes used for the predefined tokens from the table above.
The keys of this mapping should be the token types and values should be the corresponding scopes.
Semantic tokens with exactly one [token modifier](https://microsoft.github.io/language-server-protocol/specifications/specification-3-17/#semanticTokenModifiers) can be addressed by appending the modifier after a dot.
Semantic tokens with exactly one [token modifier](https://microsoft.github.io/language-server-protocol/specifications/specification-current/#semanticTokenModifiers) can be addressed by appending the modifier after a dot.

```json
{
Expand Down
11 changes: 5 additions & 6 deletions docs/src/language_servers.md
Original file line number Diff line number Diff line change
Expand Up @@ -144,24 +144,23 @@ Follow installation instructions on [LSP-elm](https://github.com/sublimelsp/LSP-

## Fortran

1. Install the [ Fortran](https://packagecontrol.io/packages/Fortran) package from Package Control for syntax highlighting.
2. Install the [Fortran Language Server](https://github.com/hansec/fortran-language-server#installation).
1. Install the [ModernFortran](https://packagecontrol.io/packages/ModernFortran) or the [Fortran](https://packagecontrol.io/packages/Fortran) package from Package Control for syntax highlighting.
2. Install the [fortls](https://fortls.fortran-lang.org/quickstart.html#download) language server.
3. Open `Preferences > Package Settings > LSP > Settings` and add the `"fortls"` client configuration to the `"clients"`:

```json
{
"clients": {
"fortls": {
"enabled": true,
"command": ["fortls"],
"selector": "source.modern-fortran | source.fixedform-fortran"
"command": ["fortls", "--notify_init"],
"selector": "source.fortran | source.modern-fortran | source.fixedform-fortran"
}
}
}
```

!!! info "See available [configuration options](https://github.com/hansec/fortran-language-server#language-server-settings)."
For example set `"command": ["fortls", "--lowercase_intrinsics"]` to use lowercase for autocomplete suggestions.
!!! info "See available [configuration options](https://fortls.fortran-lang.org/options.html)."

## Go

Expand Down