rumdl 0.0.63__tar.gz → 0.0.65__tar.gz

{rumdl-0.0.63 → rumdl-0.0.65}/Cargo.lock

@@ -1704,7 +1704,7 @@ dependencies = [
 
 [[package]]
 name = "rumdl"
-version = "0.0.63"
+version = "0.0.65"
 dependencies = [
  "anyhow",
  "assert_cmd",

{rumdl-0.0.63 → rumdl-0.0.65}/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "rumdl"
-version = "0.0.63"
+version = "0.0.65"
 edition = "2021"
 description = "A fast Markdown linter written in Rust (Ru(st) MarkDown Linter)"
 authors = ["Ruben J. Jongejan <ruben.jongejan@gmail.com>"]
@@ -65,7 +65,7 @@ tower-service = "0.3"
 env_logger = "0.11"
 
 [features]
-default = ["parallel", "profiling"]
+default = ["parallel"]
 parallel = ["rayon"]
 profiling = []
 python = ["pyo3"]

{rumdl-0.0.63 → rumdl-0.0.65}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: rumdl
-Version: 0.0.63
+Version: 0.0.65
 Classifier: Development Status :: 4 - Beta
 Classifier: Environment :: Console
 Classifier: Intended Audience :: Developers
@@ -70,8 +70,8 @@ Project-URL: Repository, https://github.com/rvben/rumdl.git
     - [Configuration in pyproject.toml](#configuration-in-pyprojecttoml)
     - [Configuration Output](#configuration-output)
       - [Effective Configuration (`rumdl config`)](#effective-configuration-rumdl-config)
-      - [Defaults Only (`rumdl config --defaults`)](#defaults-only-rumdl-config---defaults)
-  - [Editor Integration (LSP)](#editor-integration-lsp)
+      - [Example output](#example-output)
+    - [Defaults Only (`rumdl config --defaults`)](#defaults-only-rumdl-config---defaults)
   - [Output Style](#output-style)
     - [Output Format](#output-format)
   - [Development](#development)
@@ -377,9 +377,10 @@ Both kebab-case (`line-length`, `ignore-gitignore`) and snake_case (`line_length
 
 #### Effective Configuration (`rumdl config`)
 
-The `rumdl config` command prints the **full effective configuration** (defaults + all overrides), showing every key and its value, annotated with the source of each value. The output is colorized and the `[from ...]` annotation is globally aligned for easy scanning.
+The `rumdl config` command prints the **full effective configuration** (defaults + all overrides), showing every key and its value, annotated with the source of each value.
+The output is colorized and the `[from ...]` annotation is globally aligned for easy scanning.
 
-**Example output:**
+#### Example output
 
 ```text
 [global]
@@ -393,6 +394,7 @@ The `rumdl config` command prints the **full effective configuration** (defaults
   code_blocks        = true                           [from .rumdl.toml]
   ...
 ```
+
 - **Keys** are cyan, **values** are yellow, and the `[from ...]` annotation is colored by source:
   - Green: CLI
   - Blue: `.rumdl.toml`
@@ -400,7 +402,7 @@ The `rumdl config` command prints the **full effective configuration** (defaults
   - Yellow: default
 - The `[from ...]` column is aligned across all sections.
 
-#### Defaults Only (`rumdl config --defaults`)
+### Defaults Only (`rumdl config --defaults`)
 
 The `--defaults` flag prints only the default configuration as TOML, suitable for copy-paste or reference:
 
@@ -418,40 +420,6 @@ code_blocks = true
 ...
 ```
 
-## Editor Integration (LSP)
-
-rumdl includes a built-in Language Server Protocol (LSP) implementation for real-time markdown linting in your favorite editor. Following [Ruff's approach](https://docs.astral.sh/ruff/editors/), the LSP server is built directly into the main `rumdl` binary.
-
-### Starting the LSP Server
-
-```bash
-# Standard mode (stdio) - default
-rumdl server
-
-# Explicit stdio mode
-rumdl server --stdio
-
-# Debug mode (TCP)
-rumdl server --port 8080 --verbose
-```
-
-### Supported Editors
-
-- **VS Code**: Use the official rumdl extension (coming soon)
-- **Neovim**: Configure with nvim-lspconfig
-- **Emacs**: Use with lsp-mode
-- **Sublime Text**: Use with LSP package
-- **Any LSP-compatible editor**
-
-For detailed setup instructions, see our [LSP Setup Guide](docs/lsp-setup.md).
-
-### LSP Features
-
-- **Real-time diagnostics** - See markdown linting errors as you type
-- **Code actions** - One-click fixes for violations (where available)
-- **Configuration support** - Respects your `.rumdl.toml` configuration
-- **Performance optimized** - Built in Rust with all our performance optimizations
-
 ## Output Style
 
 rumdl produces clean, colorized output similar to modern linting tools:

{rumdl-0.0.63 → rumdl-0.0.65}/README.md

@@ -40,8 +40,8 @@
     - [Configuration in pyproject.toml](#configuration-in-pyprojecttoml)
     - [Configuration Output](#configuration-output)
       - [Effective Configuration (`rumdl config`)](#effective-configuration-rumdl-config)
-      - [Defaults Only (`rumdl config --defaults`)](#defaults-only-rumdl-config---defaults)
-  - [Editor Integration (LSP)](#editor-integration-lsp)
+      - [Example output](#example-output)
+    - [Defaults Only (`rumdl config --defaults`)](#defaults-only-rumdl-config---defaults)
   - [Output Style](#output-style)
     - [Output Format](#output-format)
   - [Development](#development)
@@ -347,9 +347,10 @@ Both kebab-case (`line-length`, `ignore-gitignore`) and snake_case (`line_length
 
 #### Effective Configuration (`rumdl config`)
 
-The `rumdl config` command prints the **full effective configuration** (defaults + all overrides), showing every key and its value, annotated with the source of each value. The output is colorized and the `[from ...]` annotation is globally aligned for easy scanning.
+The `rumdl config` command prints the **full effective configuration** (defaults + all overrides), showing every key and its value, annotated with the source of each value.
+The output is colorized and the `[from ...]` annotation is globally aligned for easy scanning.
 
-**Example output:**
+#### Example output
 
 ```text
 [global]
@@ -363,6 +364,7 @@ The `rumdl config` command prints the **full effective configuration** (defaults
   code_blocks        = true                           [from .rumdl.toml]
   ...
 ```
+
 - **Keys** are cyan, **values** are yellow, and the `[from ...]` annotation is colored by source:
   - Green: CLI
   - Blue: `.rumdl.toml`
@@ -370,7 +372,7 @@ The `rumdl config` command prints the **full effective configuration** (defaults
   - Yellow: default
 - The `[from ...]` column is aligned across all sections.
 
-#### Defaults Only (`rumdl config --defaults`)
+### Defaults Only (`rumdl config --defaults`)
 
 The `--defaults` flag prints only the default configuration as TOML, suitable for copy-paste or reference:
 
@@ -388,40 +390,6 @@ code_blocks = true
 ...
 ```
 
-## Editor Integration (LSP)
-
-rumdl includes a built-in Language Server Protocol (LSP) implementation for real-time markdown linting in your favorite editor. Following [Ruff's approach](https://docs.astral.sh/ruff/editors/), the LSP server is built directly into the main `rumdl` binary.
-
-### Starting the LSP Server
-
-```bash
-# Standard mode (stdio) - default
-rumdl server
-
-# Explicit stdio mode
-rumdl server --stdio
-
-# Debug mode (TCP)
-rumdl server --port 8080 --verbose
-```
-
-### Supported Editors
-
-- **VS Code**: Use the official rumdl extension (coming soon)
-- **Neovim**: Configure with nvim-lspconfig
-- **Emacs**: Use with lsp-mode
-- **Sublime Text**: Use with LSP package
-- **Any LSP-compatible editor**
-
-For detailed setup instructions, see our [LSP Setup Guide](docs/lsp-setup.md).
-
-### LSP Features
-
-- **Real-time diagnostics** - See markdown linting errors as you type
-- **Code actions** - One-click fixes for violations (where available)
-- **Configuration support** - Respects your `.rumdl.toml` configuration
-- **Performance optimized** - Built in Rust with all our performance optimizations
-
 ## Output Style
 
 rumdl produces clean, colorized output similar to modern linting tools:

{rumdl-0.0.63 → rumdl-0.0.65}/docs/md002.md

@@ -11,7 +11,7 @@ description: Ensures the first heading in a document is a top-level heading (h1)
 
 ## Description
 
-This rule ensures that the first heading in a document is a top-level heading (h1). Using a top-level heading  
+This rule ensures that the first heading in a document is a top-level heading (h1). Using a top-level heading
 as the first heading helps establish the document's main topic and maintains proper document structure.
 
 ## Configuration
@@ -32,8 +32,6 @@ Example configuration:
 
 ## Examples
 
-<!-- markdownlint-disable -->
-
 ### Valid
 
 ```markdown
@@ -48,6 +46,8 @@ Example configuration:
 
 ### Invalid
 
+<!-- rumdl-disable MD002 -->
+
 ```markdown
 ## Document Title
 
@@ -56,6 +56,8 @@ Example configuration:
 # Main Heading
 ```
 
+<!-- rumdl-enable MD002 -->
+
 ### Fixed
 
 ```markdown
@@ -68,6 +70,8 @@ Example configuration:
 
 ### Special Cases
 
+<!-- rumdl-disable MD002 -->
+
 ```markdown
 ### Third Level Heading
 
@@ -81,7 +85,8 @@ Heading
 Heading
 =======
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD002 -->
 
 ## Rationale
 

{rumdl-0.0.63 → rumdl-0.0.65}/docs/md003.md

@@ -34,7 +34,6 @@ Example configuration:
 }
 ```
 
-<!-- markdownlint-disable -->
 ## Examples
 
 ### ✓ Correct (ATX Style)
@@ -65,6 +64,8 @@ Second Level Heading
 
 ### ❌ Incorrect (Mixed Styles)
 
+<!-- rumdl-disable MD003 -->
+
 ```markdown
 # First Level Heading
 
@@ -73,7 +74,8 @@ Second Level Heading
 
 ### Third Level Heading
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD003 -->
 
 ## Special Cases
 

{rumdl-0.0.63 → rumdl-0.0.65}/docs/md005.md

@@ -18,7 +18,8 @@ This rule has no configuration options. It enforces:
 - 0 spaces for top-level list items
 - 2 spaces per level for nested items (both ordered and unordered lists)
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD005 -->
+
 ## Examples
 
 ### Valid
@@ -98,7 +99,8 @@ This rule has no configuration options. It enforces:
 1. Ordered item at same level
 2. Another ordered item
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD005 -->
 
 ## Related Rules
 

{rumdl-0.0.63 → rumdl-0.0.65}/docs/md006.md

@@ -12,7 +12,8 @@ Using proper indentation helps clearly distinguish between top-level list items
 
 This rule has no configurable options. It always enforces that top-level list items start at the beginning of the line.
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD006 -->
+
 ## Examples
 
 ### Valid
@@ -62,6 +63,7 @@ This is invalid because all top-level list items are indented with 2 spaces. The
 The rule will automatically fix incorrectly indented top-level list items by removing the leading whitespace:
 
 Before:
+
 ```markdown
   * Item 1
   * Item 2
@@ -70,6 +72,7 @@ Before:
 ```
 
 After:
+
 ```markdown
 * Item 1
 * Item 2
@@ -92,7 +95,8 @@ Some text here
   * Indented list 1  <!-- This is an error -->
   * Indented list 2  <!-- This is an error -->
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD006 -->
 
 The second list would trigger warnings because the items are indented.
 

{rumdl-0.0.63 → rumdl-0.0.65}/docs/md007.md

@@ -10,7 +10,8 @@ Nested list items should be indented with exactly 2 spaces per level. This ensur
 
 ## Examples
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD007 -->
+
 ### Valid
 
 ```markdown
@@ -40,7 +41,8 @@ Nested list items should be indented with exactly 2 spaces per level. This ensur
 * Item 2
   * Another nested item
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD007 -->
 
 ## Special Cases
 

{rumdl-0.0.63 → rumdl-0.0.65}/docs/md009.md

@@ -14,7 +14,8 @@ Trailing whitespace can cause issues with some Markdown parsers and is generally
 
 ## Examples
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD009 -->
+
 ### Valid
 
 ```markdown
@@ -35,7 +36,8 @@ And this one too
 This line has no trailing spaces
 And this one is fixed too
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD009 -->
 
 ### Special Cases
 

{rumdl-0.0.63 → rumdl-0.0.65}/docs/md010.md

@@ -14,7 +14,8 @@ leading to inconsistent rendering.
 
 ## Examples
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD010 -->
+
 ### Valid
 
 ```markdown
@@ -38,7 +39,8 @@ leading to inconsistent rendering.
   * Indented with spaces
     * Deeper indentation
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD010 -->
 
 ### Special Cases
 

{rumdl-0.0.63 → rumdl-0.0.65}/docs/md011.md

@@ -13,7 +13,8 @@ This rule has no configurable options. It simply identifies and fixes reversed l
 
 ## Examples
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD011 -->
+
 ### Valid
 
 ```markdown
@@ -32,7 +33,8 @@ These links follow the correct Markdown syntax, with text in square brackets fol
 [Contact us](mailto:example@example.com)
 ```
 
-In these examples, the link syntax is reversed, with text in parentheses and the URL in square brackets. This is incorrect Markdown syntax and will not render as a proper link in most Markdown processors.
+In these examples, the link syntax is reversed, with text in parentheses and the URL in square brackets. This is incorrect Markdown syntax and will not render as a proper link in most Markdown
+processors.
 
 ### Fixed
 
@@ -43,7 +45,8 @@ When running the linter with fixes applied, the above invalid links would be tra
 [Documentation](./docs/README.md)
 [Contact us](mailto:example@example.com)
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD011 -->
 
 ## Special Cases
 

{rumdl-0.0.63 → rumdl-0.0.65}/docs/md013.md

@@ -15,7 +15,8 @@ Lines in the Markdown document should not exceed a certain length. This helps wi
 
 ## Examples
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD013 -->
+
 ### Valid
 
 ```markdown
@@ -36,7 +37,8 @@ This is a very long line that exceeds the maximum line length limit and will tri
 This is a line that has been broken up
 to stay under the maximum line length limit.
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD013 -->
 
 ## Special Cases
 

{rumdl-0.0.63 → rumdl-0.0.65}/docs/md014.md

@@ -12,7 +12,8 @@ When documenting shell commands, it's helpful to show their output to provide co
 
 ## Examples
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD014 -->
+
 ### Valid
 
 ```markdown
@@ -45,7 +46,7 @@ $ ls -l
 ```
 
 $ echo "Hello"
-<!-- markdownlint-enable -->
+<!-- rumdl-enable MD014 -->
 
 ```text
 ```

{rumdl-0.0.63 → rumdl-0.0.65}/docs/md018.md

@@ -5,7 +5,8 @@
 This rule ensures that there is a space between the hash signs (#) and the heading text in ATX-style headings.
 A missing space can cause inconsistent rendering across different Markdown processors.
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD018 -->
+
 ## Examples
 
 ### Valid
@@ -40,7 +41,8 @@ A missing space can cause inconsistent rendering across different Markdown proce
 ##### Heading 5
 ###### Heading 6
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD018 -->
 
 ## Special Cases
 

{rumdl-0.0.63 → rumdl-0.0.65}/docs/md019.md

@@ -5,7 +5,8 @@
 This rule ensures that there is only one space between the hash signs (#) and the heading text in ATX-style headings.
 Multiple spaces can cause inconsistent rendering across different Markdown processors.
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD019 -->
+
 ## Examples
 
 ### Valid
@@ -40,7 +41,8 @@ Multiple spaces can cause inconsistent rendering across different Markdown proce
 ##### Heading 5
 ###### Heading 6
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD019 -->
 
 ## Special Cases
 

{rumdl-0.0.63 → rumdl-0.0.65}/docs/md020.md

@@ -5,7 +5,8 @@
 This rule ensures that there is a space between the hash signs (#) and the heading text in closed ATX-style headings.
 A missing space can cause inconsistent rendering across different Markdown processors.
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD020 -->
+
 ## Examples
 
 ### Valid
@@ -40,7 +41,8 @@ A missing space can cause inconsistent rendering across different Markdown proce
 ##### Heading 5 #####
 ###### Heading 6 ######
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD020 -->
 
 ## Special Cases
 

{rumdl-0.0.63 → rumdl-0.0.65}/docs/md021.md

@@ -5,7 +5,8 @@
 This rule ensures that there is only one space between the hash signs (#) and the heading text in closed ATX-style headings.
 Multiple spaces can cause inconsistent rendering across different Markdown processors.
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD021 -->
+
 ## Examples
 
 ### Valid
@@ -40,7 +41,8 @@ Multiple spaces can cause inconsistent rendering across different Markdown proce
 ##### Heading 5 #####
 ###### Heading 6 ######
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD021 -->
 
 ## Special Cases
 

{rumdl-0.0.63 → rumdl-0.0.65}/docs/md022.md

@@ -10,7 +10,7 @@ Consistent spacing around headings improves readability and ensures proper rende
 - `lines_above`: Number of blank lines that should be above headings (default: 1)
 - `lines_below`: Number of blank lines that should be below headings (default: 1)
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD022 -->
 ## Examples
 
 ### Valid
@@ -55,7 +55,8 @@ More content here.
 
 Even more content.
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD022 -->
 
 ## Special Cases
 

{rumdl-0.0.63 → rumdl-0.0.65}/docs/md023.md

@@ -5,7 +5,8 @@
 This rule ensures that all headings start at the beginning of the line, without any indentation.
 Indented headings can cause inconsistent rendering across different Markdown processors.
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD023 -->
+
 ## Examples
 
 ### Valid
@@ -31,7 +32,8 @@ Indented headings can cause inconsistent rendering across different Markdown pro
 ## Heading 2
 ### Heading 3
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD023 -->
 
 ## Special Cases
 

{rumdl-0.0.63 → rumdl-0.0.65}/docs/md024.md

@@ -8,7 +8,8 @@ Duplicate headings can confuse readers and cause issues with generated tables of
 By default, this rule considers all headings in the document, but it can be configured to  
 only check for duplicates within the same section level.
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD024 -->
+
 ## Examples
 
 ### Valid
@@ -52,7 +53,8 @@ Some content here.
 
 More content here.
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD024 -->
 
 ## Configuration
 
@@ -67,7 +69,8 @@ the document hierarchy) are checked for duplicates. Default is `false`.
 
 MD024 does not support auto-fixing.
 
-Duplicate headings are only reported as warnings; no automatic fix is provided. This is because removing or changing headings automatically could result in data loss or confusion. Please review and resolve duplicate headings manually.
+Duplicate headings are only reported as warnings; no automatic fix is provided. This is because removing or changing headings automatically could result in data loss or confusion. Please review and
+resolve duplicate headings manually.
 
 ## Special Cases
 

{rumdl-0.0.63 → rumdl-0.0.65}/docs/md026.md

@@ -6,7 +6,6 @@ This rule ensures that headings do not end with punctuation characters. Trailing
 
 By default, this rule checks for the following punctuation characters: `.,;:!?`. The list of punctuation characters can be customized through configuration.
 
-<!-- markdownlint-disable -->
 ## Examples
 
 ### Valid
@@ -21,6 +20,8 @@ By default, this rule checks for the following punctuation characters: `.,;:!?`.
 
 ### Invalid
 
+<!-- rumdl-disable MD026 -->
+
 ```markdown
 # Introduction!
 
@@ -29,6 +30,8 @@ By default, this rule checks for the following punctuation characters: `.,;:!?`.
 ### How to Install.
 ```
 
+<!-- rumdl-enable MD026 -->
+
 ### Fixed
 
 ```markdown
@@ -38,7 +41,6 @@ By default, this rule checks for the following punctuation characters: `.,;:!?`.
 
 ### How to Install
 ```
-<!-- markdownlint-enable -->
 
 ## Configuration
 

{rumdl-0.0.63 → rumdl-0.0.65}/docs/md027.md

@@ -6,7 +6,8 @@ This rule ensures that blockquote markers (`>`) are followed by a single space.
 Multiple spaces after the blockquote symbol can lead to inconsistent rendering and  
 are generally considered poor style.
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD027 -->
+
 ## Examples
 
 ### Valid
@@ -32,7 +33,8 @@ are generally considered poor style.
 > Each line now starts with a single space after the '>' symbol.
 > This ensures consistent formatting.
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD027 -->
 
 ## Special Cases