Update editor settings reference with new format (#944)

## Summary

This PR updates the documentation to reflect the changes made in
astral-sh/ruff#19614 and
astral-sh/ty-vscode#106.

## Test Plan

<details><summary>Screenshot of the new editor settings reference
page:</summary>
<p>

<img width="4992" height="3702" alt="image"
src="https://github.com/user-attachments/assets/e3afd5a3-8b5b-43c3-addd-e1d6636ab1b7"
/>

</p>
</details>

Author: dhruvmanila

docs/editors.md

@@ -16,8 +16,8 @@ For Neovim 0.10 or earlier (with [`nvim-lspconfig`](https://github.com/neovim/nv
 
 ```lua
 require('lspconfig').ty.setup({
-  init_options = {
-    settings = {
+  settings = {
+    ty = {
       -- ty language server settings go here
     }
   }
@@ -29,8 +29,8 @@ For Neovim 0.11+ (with [`vim.lsp.config`](<https://neovim.io/doc/user/lsp.html#v
 ```lua
 -- Optional: Only required if you need to update the language server settings
 vim.lsp.config('ty', {
-  init_options = {
-    settings = {
+  settings = {
+    ty = {
       -- ty language server settings go here
     }
   }

docs/reference/editor-settings.md

@@ -1,8 +1,9 @@
 # Editor settings
 
-The editor settings supported by ty's language server, as well as the settings specific to [ty's VS Code extension](https://github.com/astral-sh/ty-vscode/).
+The editor settings supported by ty's language server, as well as the settings specific to [ty's VS
+Code extension][ty-vscode].
 
-## `python.ty.disableLanguageServices`
+## `disableLanguageServices`
 
 Whether to disable the language services for the ty language server like code completion, hover,
 go to definition, etc.
@@ -16,84 +17,142 @@ server for features like code completion, hover, go to definition, etc.
 
 **Example usage**:
 
-```json
-{
-  "python.ty.disableLanguageServices": true
-}
-```
-
-## `diagnosticMode`
-
-Determines the scope of the diagnostics reported by the language server.
-
-- `openFilesOnly`: Diagnostics are reported only for files that are currently open in the editor.
-- `workspace`: Diagnostics are reported for all files in the workspace.
-
-**Default value**: `"openFilesOnly"`
+=== "VS Code"
+
+    ```json
+    {
+      "ty.disableLanguageServices": true
+    }
+    ```
+
+=== "Neovim"
+
+    ```lua
+    require('lspconfig').ty.setup({
+      settings = {
+        ty = {
+          disableLanguageServices = true,
+        },
+      },
+    })
+
+    -- For Neovim 0.11.0 and later:
+    vim.lsp.config('ty', {
+      settings = {
+        ty = {
+          disableLanguageServices = true,
+        },
+      },
+    })
+    ```
+
+=== "Zed"
+
+    ```json
+    {
+      "lsp": {
+        "ty": {
+          "settings": {
+            "ty": {
+              "disableLanguageServices": true
+            }
+          }
+        }
+      }
+    }
+    ```
+
+______________________________________________________________________
 
-**Type**: `"workspace" | "openFilesOnly"`
+## `python.ty.disableLanguageServices`
 
-**Example usage**:
+!!! warning "Deprecated"
 
-```json
-{
-  "ty.diagnosticMode": "workspace"
-}
-```
+    This option has been deprecated. Use [`ty.disableLanguageServices`](#disablelanguageservices) instead.
 
-## `logFile`
+Whether to disable the language services that ty provides like code completion, hover, go to
+definition, etc.
 
-Path to the file to which the language server writes its log messages. By default, ty writes log messages to stderr.
+This is useful if you want to use ty exclusively for type checking in combination with another
+language server for features like code completion, hover, go to definition, etc.
 
-**Default value**: `null`
+**Default value**: `false`
 
-**Type**: `string`
+**Type**: `boolean`
 
 **Example usage**:
 
 ```json
 {
-  "ty.logFile": "~/path/to/ty.log"
+  "python.ty.disableLanguageServices": true
 }
 ```
 
-## `logLevel`
-
-The log level to use for the language server.
-
-**Default value**: `"info"`
-
-**Type**: `"trace" | "debug" | "info" | "warn" | "error"`
-
-**Example usage**:
+______________________________________________________________________
 
-```json
-{
-  "ty.logLevel": "debug"
-}
-```
+## `diagnosticMode`
 
-## `trace.server`
+Determines the scope of the diagnostics reported by the language server.
 
-The detail level at which messages between the language server and the editor (client) are logged. Refer to the [LSP
-specification](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#traceValue)
-for more information.
+- `openFilesOnly`: Diagnostics are reported only for files that are currently open in the editor.
+- `workspace`: Diagnostics are reported for all files in the workspace.
 
-**Default value**: `"off"`
+**Default value**: `"openFilesOnly"`
 
-**Type**: `"off" | "messages" | "verbose"`
+**Type**: `"workspace" | "openFilesOnly"`
 
 **Example usage**:
 
-```json
-{
-  "ty.trace.server": "messages"
-}
-```
+=== "VS Code"
+
+    ```json
+    {
+      "ty.diagnosticMode": "workspace"
+    }
+    ```
+
+=== "Neovim"
+
+    ```lua
+    require('lspconfig').ty.setup({
+      settings = {
+        ty = {
+          diagnosticMode = 'workspace',
+        },
+      },
+    })
+
+    -- For Neovim 0.11.0 and later:
+    vim.lsp.config('ty', {
+      settings = {
+        ty = {
+          diagnosticMode = 'workspace',
+        },
+      },
+    })
+    ```
+
+=== "Zed"
+
+    ```json
+    {
+      "lsp": {
+        "ty": {
+          "settings": {
+            "ty": {
+              "diagnosticMode": "workspace"
+            }
+          }
+        }
+      }
+    }
+    ```
+
+______________________________________________________________________
 
 ## VS Code specific
 
-The following settings are specific to ty's VS Code extension.
+The following settings are specific to [ty's VS Code extension][ty-vscode].
 
 ### `importStrategy`
 
@@ -114,6 +173,8 @@ Strategy for loading the `ty` executable.
 }
 ```
 
+______________________________________________________________________
+
 ### `interpreter`
 
 A list of paths to Python interpreters. Even though this is a list, only the first interpreter is
@@ -134,6 +195,8 @@ The interpreter path is used to find the `ty` executable when
 }
 ```
 
+______________________________________________________________________
+
 ### `path`
 
 A list of path to `ty` executables.
@@ -152,3 +215,139 @@ The extension uses the first executable that exists. This setting takes preceden
   "ty.path": ["/home/user/.local/bin/ty"]
 }
 ```
+
+______________________________________________________________________
+
+### `trace.server`
+
+The detail level at which messages between the language server and the editor (client) are logged.
+
+This setting is useful for debugging issues with the language server. Refer to the [troubleshooting
+guide](https://github.com/astral-sh/ty-vscode/blob/6cf16b4e87342a49f2bec1310a730cde8229e1d9/TROUBLESHOOTING.md)
+in [ty's VS Code extension][ty-vscode] for more information.
+
+**Default value**: `"off"`
+
+**Type**: `"off" | "messages" | "verbose"`
+
+**Example usage**:
+
+```json
+{
+  "ty.trace.server": "messages"
+}
+```
+
+______________________________________________________________________
+
+## Initialization options
+
+The following settings are required when ty is initialized in an editor. These settings are
+static so changing them requires restarting the editor to take effect.
+
+For VS Code users, these settings are defined in the `ty.*` namespace as usual, but for other
+editors, they would need to be provided in a separate field of the configuration that corresponds to
+the initialization options. Refer to the examples below for how to set these options in different
+editors.
+
+### `logFile`
+
+Path to the file to which the language server writes its log messages. By default, ty writes log messages to stderr.
+
+**Default value**: `null`
+
+**Type**: `string`
+
+**Example usage**:
+
+=== "VS Code"
+
+    ```json
+    {
+      "ty.logFile": "/path/to/ty.log"
+    }
+    ```
+
+=== "Neovim"
+
+    ```lua
+    require('lspconfig').ty.setup({
+      init_options = {
+        logFile = '/path/to/ty.log',
+      },
+    })
+
+    -- For Neovim 0.11.0 and later:
+    vim.lsp.config('ty', {
+      init_options = {
+        logFile = '/path/to/ty.log',
+      },
+    })
+    ```
+
+=== "Zed"
+
+    ```json
+    {
+      "lsp": {
+        "ty": {
+          "initialization_options": {
+            "logFile": "/path/to/ty.log"
+          }
+        }
+      }
+    }
+    ```
+
+______________________________________________________________________
+
+### `logLevel`
+
+The log level to use for the language server.
+
+**Default value**: `"info"`
+
+**Type**: `"trace" | "debug" | "info" | "warn" | "error"`
+
+**Example usage**:
+
+=== "VS Code"
+
+    ```json
+    {
+      "ty.logLevel": "debug"
+    }
+    ```
+
+=== "Neovim"
+
+    ```lua
+    require('lspconfig').ty.setup({
+      init_options = {
+        logLevel = 'debug',
+      },
+    })
+
+    -- For Neovim 0.11.0 and later:
+    vim.lsp.config('ty', {
+      init_options = {
+        logLevel = 'debug',
+      },
+    })
+    ```
+
+=== "Zed"
+
+    ```json
+    {
+      "lsp": {
+        "ty": {
+          "initialization_options": {
+            "logLevel": "debug"
+          }
+        }
+      }
+    }
+    ```
+
+[ty-vscode]: https://marketplace.visualstudio.com/items?itemName=astral-sh.ty