flowmark 0.5.0__tar.gz → 0.5.2__tar.gz

{flowmark-0.5.0 → flowmark-0.5.2}/.copier-answers.yml

@@ -1,5 +1,5 @@
 # Changes here will be overwritten by Copier. Do not edit manually.
-_commit: v0.2.14
+_commit: v0.2.15
 _src_path: gh:jlevy/simple-modern-uv
 package_author_email: joshua@cal.berkeley.edu
 package_author_name: Joshua Levy

{flowmark-0.5.0 → flowmark-0.5.2}/.cursor/rules/general.mdc

@@ -7,7 +7,7 @@ alwaysApply: true
 
 **Your fundamental responsibility:** Remember you are a senior engineer and have a
 serious responsibility to be clear, factual, think step by step and be systematic,
-express expert opinion, and make use of the user's attention wisely.
+express expert opinion, and make use of the user’s attention wisely.
 
 **Rules must be followed:** It is your responsibility to carefully read these rules as
 well as Python or other language-specific rules included here.
@@ -22,19 +22,19 @@ Therefore:
   confirmation.
 
 - If you can think of a much better approach that the user requests, be sure to mention
-  it. It's your responsibility to suggest approaches that lead to better, simpler
+  it. It’s your responsibility to suggest approaches that lead to better, simpler
   solutions.
 
-- Give thoughtful opinions on better/worse approaches, but NEVER say "great idea!"
-  or "good job" or other compliments, encouragement, or non-essential banter.
+- Give thoughtful opinions on better/worse approaches, but NEVER say “great idea!”
+  or “good job” or other compliments, encouragement, or non-essential banter.
   Your job is to give expert opinions and to solve problems, not to motivate the user.
 
 - Avoid gratuitous enthusiasm or generalizations.
-  Use thoughtful comparisons like saying which code is "cleaner" but don't congratulate
+  Use thoughtful comparisons like saying which code is “cleaner” but don’t congratulate
   yourself. Avoid subjective descriptions.
-  For example, don't say "I've meticulously improved the code and it is in great shape!"
+  For example, don’t say “I’ve meticulously improved the code and it is in great shape!”
   That is useless generalization.
-  Instead, specifically say what you've done, e.g., "I've added types, including
+  Instead, specifically say what you’ve done, e.g., "I’ve added types, including
   generics, to all the methods in `Foo` and fixed all linter errors."
 
 # General Coding Guidelines
@@ -49,17 +49,17 @@ Therefore:
 - DO NOT repeat in comments what is obvious from the names of functions or variables or
   types.
 
-- DO NOT include comments that reflect what you did, such as "Added this function" as
+- DO NOT include comments that reflect what you did, such as “Added this function” as
   this is meaningless to anyone reading the code later.
   (Instead, describe in your message to the user any other contextual information.)
 
-- DO NOT use fancy or needlessly decorated headings like "===== MIGRATION TOOLS ====="
+- DO NOT use fancy or needlessly decorated headings like “===== MIGRATION TOOLS =====”
   in comments
 
 - DO NOT number steps in comments.
   These are hard to maintain if the code changes.
-  NEVER DO THIS: "// Step 3: Fetch the data from the cache"\
-  This is fine: "// Now fetch the data from the cache"
+  NEVER DO THIS: “// Step 3: Fetch the data from the cache”\
+  This is fine: “// Now fetch the data from the cache”
 
 - DO NOT use emojis or special unicode characters like ① or • or – or — in comments.
 

{flowmark-0.5.0 → flowmark-0.5.2}/.cursor/rules/python.mdc

@@ -87,7 +87,7 @@ Always use full type annotations, generics, and other modern practices.
 - Use pathlib `Path` instead of strings.
   Use `Path(filename).read_text()` instead of two-line `with open(...)` blocks.
 
-- Use strif's `atomic_output_file` context manager when writing files to ensure output
+- Use strif’s `atomic_output_file` context manager when writing files to ensure output
   files are written atomically.
 
 ## Use Modern Python Practices
@@ -112,7 +112,7 @@ Always use full type annotations, generics, and other modern practices.
 
 - You can run such individual tests with `uv run pytest -s src/.../path/to/test`
 
-- Don't add docs to assertions unless it's not obvious what they're checking - the
+- Don’t add docs to assertions unless it’s not obvious what they’re checking - the
   assertion appears in the stack trace.
   Do NOT write `assert x == 5, "x should be 5"`. Do NOT write `assert x == 5 # Check if
   x is 5`. That is redundant.
@@ -122,7 +122,7 @@ Always use full type annotations, generics, and other modern practices.
   assertions that confirm the value of a constant setting.
 
 - NEVER write `assert False`. If a test reaches an unexpected branch and must fail
-  explicitly, `raise AssertionError("Explanation")` instead.
+  explicitly, `raise AssertionError("Some explanation")` instead.
   This is best typical best practice in Python since assertions can be removed with
   optimization.
 
@@ -132,6 +132,21 @@ Always use full type annotations, generics, and other modern practices.
   This is also preferable because then simple tests have no explicit pytest dependencies
   and can be placed in code anywhere.
 
+- DO NOT write trivial tests that test something we know already works, like
+  instantiating a Pydantic object.
+
+  ```python
+  class Link(BaseModel):
+    url: str
+    title: str = None
+  
+  # DO NOT write tests like this. They are trivial and only create clutter!
+  def test_link_model():
+    link = Link(url="https://example.com", title="Example")
+    assert link.url == "https://example.com"
+    assert link.title == "Example"
+  ```
+
 ## Types and Type Annotations
 
 - Use modern union syntax: `str | None` instead of `Optional[str]`, `dict[str]` instead
@@ -142,7 +157,7 @@ Always use full type annotations, generics, and other modern practices.
 - Use modern enums like `StrEnum` if appropriate.
 
 - One exception to common practice on enums: If an enum has many values that are
-  strings, and they have a literal value as a string (like in a JSON protocol), it's
+  strings, and they have a literal value as a string (like in a JSON protocol), it’s
   fine to use lower_snake_case for enum values to match the actual value.
   This is more readable than LONG_ALL_CAPS_VALUES, and you can simply set the value to
   be the same as the name for each.
@@ -228,7 +243,7 @@ Always use full type annotations, generics, and other modern practices.
 - For classes with many methods, use a concise docstring on the class that explains all
   the common information, and avoid repeating the same information on every method.
 
-- Docstrings should provide context or as concisely as possible explain "why", not
+- Docstrings should provide context or as concisely as possible explain “why”, not
   obvious details evident from the class names, function names, parameter names, and
   type annotations.
 
@@ -240,10 +255,10 @@ Always use full type annotations, generics, and other modern practices.
   name, variable name, or types.
   That is silly and obvious and makes the code longer for no reason.
 
-- Do NOT list args and return values if they're obvious.
+- Do NOT list args and return values if they’re obvious.
   In the above examples, you do not need and `Arguments:` or `Returns:` section, since
-  their meaning as obvious from context.
-  do list these if there are many arguments and their meaning isn't clear.
+  sections as it is obvious from context.
+  do list these if there are many arguments and their meaning isn’t clear.
   If it returns a less obvious type like a tuple, do explain in the pydoc.
 
 - Exported/public variables, functions, or methods SHOULD have concise docstrings.

{flowmark-0.5.0 → flowmark-0.5.2}/.github/workflows/ci.yml

@@ -41,7 +41,7 @@ jobs:
         uses: astral-sh/setup-uv@v5
         with:
           # Update this as needed:
-          version: "0.7.13"
+          version: "0.8.0"
           enable-cache: true
           python-version: ${{ matrix.python-version }}
 

{flowmark-0.5.0 → flowmark-0.5.2}/.github/workflows/publish.yml

@@ -21,7 +21,7 @@ jobs:
       - name: Install uv (official Astral action)
         uses: astral-sh/setup-uv@v5
         with:
-          version: "0.7.13"
+          version: "0.8.0"
           enable-cache: true
           python-version: "3.12"
 

{flowmark-0.5.0 → flowmark-0.5.2}/Makefile

@@ -47,3 +47,11 @@ clean:
 
 format-docs:
 	uv run flowmark --auto README.md
+
+# Reset the expected reference docs to the actual ones currently produced.
+reset-ref-docs:
+	cp tests/testdocs/testdoc.actual.auto.md tests/testdocs/testdoc.expected.auto.md
+	cp tests/testdocs/testdoc.actual.cleaned.md tests/testdocs/testdoc.expected.cleaned.md
+	cp tests/testdocs/testdoc.actual.plain.md tests/testdocs/testdoc.expected.plain.md
+	cp tests/testdocs/testdoc.actual.semantic.md tests/testdocs/testdoc.expected.semantic.md
+

{flowmark-0.5.0 → flowmark-0.5.2}/PKG-INFO

@@ -1,7 +1,7 @@
 Metadata-Version: 2.4
 Name: flowmark
-Version: 0.5.0
-Summary: Better auto-formatting and line wrapping for Markdown and plaintext
+Version: 0.5.2
+Summary: Better auto-formatting for Markdown and plaintext
 Project-URL: Repository, https://github.com/jlevy/flowmark
 Author-email: Joshua Levy <joshua@cal.berkeley.edu>
 License-Expression: MIT
@@ -141,16 +141,16 @@ and sometimes controversial.
 However, now we are using versioned Markdown more than ever, it’s a good time to revisit
 this idea, as it can **make diffs in git much more readable**. The change may seem
 subtle but avoids having paragraphs reflow for very small edits, which does a lot to
-**minimize merge conflicts**. 
+**minimize merge conflicts**.
 
-This is my own refinement of [traditional semantic line breaks](https://github.com/sembr/specification).
+This is my own refinement of [traditional semantic line
+breaks](https://github.com/sembr/specification).
 Instead of just allowing you to break lines as you wish, it auto-applies fixed
 conventions about likely sentence boundaries in a conservative and reasonable way.
 It uses simple and fast **regex-based sentence splitting**. While not perfect, this
 works well for these purposes (and is much faster and simpler than a proper sentence
 parser like SpaCy). It should work fine for English and many other Latin/Cyrillic
-languages, but hasn’t been tested on CJK.
-You can see some
+languages, but hasn’t been tested on CJK. You can see some
 [old discussion](https://github.com/shurcooL/markdownfmt/issues/17) of this idea with
 the markdownfmt author.
 
@@ -160,7 +160,9 @@ edit/commit documents.
 
 This feature is enabled with the `--semantic` flag or the `--auto` convenience flag.
 
-## Smart Quote Support
+## Typographic Cleanups
+
+### Smart Quote Support
 
 Flowmark offers optional **automatic smart quotes** to convert \"non-oriented quotes\"
 to “oriented quotes” and apostrophes intelligently.
@@ -175,6 +177,14 @@ quote marks around regular text.
 
 This feature is enabled with the `--smartquotes` flag or the `--auto` convenience flag.
 
+### Ellipsis Support
+
+There is a similar feature for converting `...` to an ellipsis character `…` when it
+appears to be appropriate (i.e., not in code blocks and when adjacent to words or
+punctuation).
+
+This feature is enabled with the `--ellipses` flag or the `--auto` convenience flag.
+
 ## Frontmatter Support
 
 Because **YAML frontmatter** is common on Markdown files, any YAML frontmatter (content
@@ -191,11 +201,11 @@ YAML is not normalized.
 Flowmark can be used as a library or as a CLI.
 
 ```
-usage: flowmark [-h] [-o OUTPUT] [-w WIDTH] [-p] [-s] [-c] [--smartquotes] [-i]
+usage: flowmark [-h] [-o OUTPUT] [-w WIDTH] [-p] [-s] [-c] [--smartquotes] [--ellipses] [-i]
                 [--nobackup] [--auto] [--version]
                 [file]
 
-Flowmark: Better auto-formatting and line wrapping for Markdown and plaintext
+Flowmark: Better auto-formatting for Markdown and plaintext
 
 positional arguments:
   file                 Input file (use '-' for stdin)
@@ -203,21 +213,20 @@ positional arguments:
 options:
   -h, --help           show this help message and exit
   -o, --output OUTPUT  Output file (use '-' for stdout)
-  -w, --width WIDTH    Line width to wrap to, or 0 to disable line wrapping
-                       (default: 88)
+  -w, --width WIDTH    Line width to wrap to, or 0 to disable line wrapping (default: 88)
   -p, --plaintext      Process as plaintext (no Markdown parsing)
-  -s, --semantic       Enable semantic (sentence-based) line breaks (only applies to
-                       Markdown mode)
-  -c, --cleanups       Enable (safe) cleanups for common issues like accidentally
-                       boldfaced section headers (only applies to Markdown mode)
-  --smartquotes        Convert straight quotes to typographic (curly) quotes and
-                       apostrophes (only applies to Markdown mode)
+  -s, --semantic       Enable semantic (sentence-based) line breaks (only applies to Markdown
+                       mode)
+  -c, --cleanups       Enable (safe) cleanups for common issues like accidentally boldfaced
+                       section headers (only applies to Markdown mode)
+  --smartquotes        Convert straight quotes to typographic (curly) quotes and apostrophes
+                       (only applies to Markdown mode)
+  --ellipses           Convert three dots (...) to ellipsis character (…) with normalized
+                       spacing (only applies to Markdown mode)
   -i, --inplace        Edit the file in place (ignores --output)
-  --nobackup           Do not make a backup of the original file when using
-                       --inplace
-  --auto               Same as `--inplace --nobackup --semantic --cleanups
-                       --smartquotes`, as a convenience for fully auto-formatting
-                       files
+  --nobackup           Do not make a backup of the original file when using --inplace
+  --auto               Same as `--inplace --nobackup --semantic --cleanups --smartquotes
+                       --ellipses`, as a convenience for fully auto-formatting files
   --version            Show version information and exit
 
 Flowmark provides enhanced text wrapping capabilities with special handling for
@@ -237,6 +246,10 @@ Command-line usage examples:
   # Format a Markdown file to stdout
   flowmark README.md
 
+  # Format a Markdown file in-place without backups and all auto-formatting
+  # options enabled
+  flowmark --auto README.md
+
   # Format a Markdown file and save to a new file
   flowmark README.md -o README_formatted.md
 

{flowmark-0.5.0 → flowmark-0.5.2}/README.md

@@ -117,16 +117,16 @@ and sometimes controversial.
 However, now we are using versioned Markdown more than ever, it’s a good time to revisit
 this idea, as it can **make diffs in git much more readable**. The change may seem
 subtle but avoids having paragraphs reflow for very small edits, which does a lot to
-**minimize merge conflicts**. 
+**minimize merge conflicts**.
 
-This is my own refinement of [traditional semantic line breaks](https://github.com/sembr/specification).
+This is my own refinement of [traditional semantic line
+breaks](https://github.com/sembr/specification).
 Instead of just allowing you to break lines as you wish, it auto-applies fixed
 conventions about likely sentence boundaries in a conservative and reasonable way.
 It uses simple and fast **regex-based sentence splitting**. While not perfect, this
 works well for these purposes (and is much faster and simpler than a proper sentence
 parser like SpaCy). It should work fine for English and many other Latin/Cyrillic
-languages, but hasn’t been tested on CJK.
-You can see some
+languages, but hasn’t been tested on CJK. You can see some
 [old discussion](https://github.com/shurcooL/markdownfmt/issues/17) of this idea with
 the markdownfmt author.
 
@@ -136,7 +136,9 @@ edit/commit documents.
 
 This feature is enabled with the `--semantic` flag or the `--auto` convenience flag.
 
-## Smart Quote Support
+## Typographic Cleanups
+
+### Smart Quote Support
 
 Flowmark offers optional **automatic smart quotes** to convert \"non-oriented quotes\"
 to “oriented quotes” and apostrophes intelligently.
@@ -151,6 +153,14 @@ quote marks around regular text.
 
 This feature is enabled with the `--smartquotes` flag or the `--auto` convenience flag.
 
+### Ellipsis Support
+
+There is a similar feature for converting `...` to an ellipsis character `…` when it
+appears to be appropriate (i.e., not in code blocks and when adjacent to words or
+punctuation).
+
+This feature is enabled with the `--ellipses` flag or the `--auto` convenience flag.
+
 ## Frontmatter Support
 
 Because **YAML frontmatter** is common on Markdown files, any YAML frontmatter (content
@@ -167,11 +177,11 @@ YAML is not normalized.
 Flowmark can be used as a library or as a CLI.
 
 ```
-usage: flowmark [-h] [-o OUTPUT] [-w WIDTH] [-p] [-s] [-c] [--smartquotes] [-i]
+usage: flowmark [-h] [-o OUTPUT] [-w WIDTH] [-p] [-s] [-c] [--smartquotes] [--ellipses] [-i]
                 [--nobackup] [--auto] [--version]
                 [file]
 
-Flowmark: Better auto-formatting and line wrapping for Markdown and plaintext
+Flowmark: Better auto-formatting for Markdown and plaintext
 
 positional arguments:
   file                 Input file (use '-' for stdin)
@@ -179,21 +189,20 @@ positional arguments:
 options:
   -h, --help           show this help message and exit
   -o, --output OUTPUT  Output file (use '-' for stdout)
-  -w, --width WIDTH    Line width to wrap to, or 0 to disable line wrapping
-                       (default: 88)
+  -w, --width WIDTH    Line width to wrap to, or 0 to disable line wrapping (default: 88)
   -p, --plaintext      Process as plaintext (no Markdown parsing)
-  -s, --semantic       Enable semantic (sentence-based) line breaks (only applies to
-                       Markdown mode)
-  -c, --cleanups       Enable (safe) cleanups for common issues like accidentally
-                       boldfaced section headers (only applies to Markdown mode)
-  --smartquotes        Convert straight quotes to typographic (curly) quotes and
-                       apostrophes (only applies to Markdown mode)
+  -s, --semantic       Enable semantic (sentence-based) line breaks (only applies to Markdown
+                       mode)
+  -c, --cleanups       Enable (safe) cleanups for common issues like accidentally boldfaced
+                       section headers (only applies to Markdown mode)
+  --smartquotes        Convert straight quotes to typographic (curly) quotes and apostrophes
+                       (only applies to Markdown mode)
+  --ellipses           Convert three dots (...) to ellipsis character (…) with normalized
+                       spacing (only applies to Markdown mode)
   -i, --inplace        Edit the file in place (ignores --output)
-  --nobackup           Do not make a backup of the original file when using
-                       --inplace
-  --auto               Same as `--inplace --nobackup --semantic --cleanups
-                       --smartquotes`, as a convenience for fully auto-formatting
-                       files
+  --nobackup           Do not make a backup of the original file when using --inplace
+  --auto               Same as `--inplace --nobackup --semantic --cleanups --smartquotes
+                       --ellipses`, as a convenience for fully auto-formatting files
   --version            Show version information and exit
 
 Flowmark provides enhanced text wrapping capabilities with special handling for
@@ -213,6 +222,10 @@ Command-line usage examples:
   # Format a Markdown file to stdout
   flowmark README.md
 
+  # Format a Markdown file in-place without backups and all auto-formatting
+  # options enabled
+  flowmark --auto README.md
+
   # Format a Markdown file and save to a new file
   flowmark README.md -o README_formatted.md
 

{flowmark-0.5.0 → flowmark-0.5.2}/pyproject.toml

@@ -7,7 +7,7 @@ Repository = "https://github.com/jlevy/flowmark"
 
 [project]
 name = "flowmark"
-description = "Better auto-formatting and line wrapping for Markdown and plaintext"
+description = "Better auto-formatting for Markdown and plaintext"
 authors = [
     { name="Joshua Levy", email="joshua@cal.berkeley.edu" },
 ]

{flowmark-0.5.0 → flowmark-0.5.2}/src/flowmark/cli.py

@@ -1,6 +1,6 @@
 #!/usr/bin/env python3
 """
-Flowmark: Better auto-formatting and line wrapping for Markdown and plaintext
+Flowmark: Better auto-formatting for Markdown and plaintext
 
 Flowmark provides enhanced text wrapping capabilities with special handling for
 Markdown content. It can:
@@ -19,6 +19,10 @@ Command-line usage examples:
   # Format a Markdown file to stdout
   flowmark README.md
 
+  # Format a Markdown file in-place without backups and all auto-formatting
+  # options enabled
+  flowmark --auto README.md
+
   # Format a Markdown file and save to a new file
   flowmark README.md -o README_formatted.md
 
@@ -55,6 +59,7 @@ class Options:
     semantic: bool
     cleanups: bool
     smartquotes: bool
+    ellipses: bool
     inplace: bool
     nobackup: bool
     version: bool
@@ -119,6 +124,13 @@ def _parse_args(args: list[str] | None = None) -> Options:
         help="Convert straight quotes to typographic (curly) quotes and apostrophes "
         "(only applies to Markdown mode)",
     )
+    parser.add_argument(
+        "--ellipses",
+        action="store_true",
+        default=False,
+        help="Convert three dots (...) to ellipsis character (…) with normalized spacing "
+        "(only applies to Markdown mode)",
+    )
     parser.add_argument(
         "-i", "--inplace", action="store_true", help="Edit the file in place (ignores --output)"
     )
@@ -130,7 +142,7 @@ def _parse_args(args: list[str] | None = None) -> Options:
     parser.add_argument(
         "--auto",
         action="store_true",
-        help="Same as `--inplace --nobackup --semantic --cleanups --smartquotes`, as a convenience for "
+        help="Same as `--inplace --nobackup --semantic --cleanups --smartquotes --ellipses`, as a convenience for "
         "fully auto-formatting files",
     )
     parser.add_argument(
@@ -146,6 +158,7 @@ def _parse_args(args: list[str] | None = None) -> Options:
         opts.semantic = True
         opts.cleanups = True
         opts.smartquotes = True
+        opts.ellipses = True
 
     return Options(
         file=opts.file,
@@ -155,6 +168,7 @@ def _parse_args(args: list[str] | None = None) -> Options:
         semantic=opts.semantic,
         cleanups=opts.cleanups,
         smartquotes=opts.smartquotes,
+        ellipses=opts.ellipses,
         inplace=opts.inplace,
         nobackup=opts.nobackup,
         version=opts.version,
@@ -193,6 +207,7 @@ def main(args: list[str] | None = None) -> int:
             semantic=options.semantic,
             cleanups=options.cleanups,
             smartquotes=options.smartquotes,
+            ellipses=options.ellipses,
             make_parents=True,
         )
     except ValueError as e:

{flowmark-0.5.0 → flowmark-0.5.2}/src/flowmark/doc_transforms.py

@@ -5,6 +5,7 @@ from collections.abc import Callable
 from marko import block, inline
 from marko.block import Document
 from marko.element import Element
+from marko.ext import footnote
 
 ContainerElement = (
     block.Document,
@@ -16,6 +17,7 @@ ContainerElement = (
     inline.Emphasis,
     inline.StrongEmphasis,
     inline.Link,
+    footnote.FootnoteDef,  # Footnote definitions contain paragraphs and other elements
 )
 
 

flowmark-0.5.2/src/flowmark/ellipses.py

@@ -0,0 +1,58 @@
+import re
+from re import Pattern
+
+ELLIPSIS_PATTERN: Pattern[str] = re.compile(
+    r"(^|[\w\"\'“‘])(\s*)(\.\.\.)([.,:;?!)\-—\"\'”’]?)(\s*)",
+    re.MULTILINE,
+)
+
+
+def ellipses(text: str) -> str:
+    r"""
+    Replace three consecutive dots with a proper ellipsis character (…).
+
+    Rules:
+    - `...` must be preceded by start of line OR a word character (with optional space)
+    - `...` must be followed by word character (with optional space) OR punctuation OR end of line
+    - If immediately before the `...` is a word character (no whitespace), a space is inserted before it.
+    - If immediately after the `...` is a word character (no whitespace), a space is inserted after it.
+    - If the punctuation [\"\'“‘] immediately precedes the ellipsis, there is no space between the
+      punctuation and the ellipsis.
+    - If punctuation [.,:;?!)\-—] follows the ellipsis, there is no space between the ellipsis and
+      the punctuation.
+    """
+
+    def replace_match(match: re.Match[str]) -> str:
+        prefix = match.group(1)
+        spaces_before = match.group(2)
+        punct = match.group(4)
+        spaces_after = match.group(5)
+
+        # Get what follows the match
+        end_pos = match.end()
+        remaining = text[end_pos:] if end_pos < len(text) else ""
+        next_char = remaining[0] if remaining else ""
+
+        # Check boundary - must be followed by word or end of line
+        if remaining and not re.match(r"\w|$", next_char):
+            return match.group(0)
+
+        result = prefix
+
+        # Add space before ellipsis if word char with no existing space
+        if prefix and re.match(r"\w", prefix) and not spaces_before:
+            result += " "
+        else:
+            result += spaces_before
+
+        result += "…" + punct
+
+        # Add space after ellipsis if word char follows with no space and no punct
+        if next_char and re.match(r"\w", next_char) and not spaces_after and not punct:
+            result += " "
+        else:
+            result += spaces_after
+
+        return result
+
+    return ELLIPSIS_PATTERN.sub(replace_match, text)

{flowmark-0.5.0 → flowmark-0.5.2}/src/flowmark/markdown_filling.py

@@ -18,6 +18,7 @@ from textwrap import dedent
 from flowmark.custom_marko import custom_marko
 from flowmark.doc_cleanups import doc_cleanups
 from flowmark.doc_transforms import rewrite_text_content
+from flowmark.ellipses import ellipses as apply_ellipses
 from flowmark.frontmatter import split_frontmatter
 from flowmark.line_wrappers import LineWrapper, line_wrap_by_sentence, line_wrap_to_width
 from flowmark.sentence_split_regex import split_sentences_regex
@@ -82,6 +83,7 @@ def fill_markdown(
     semantic: bool = False,
     cleanups: bool = False,
     smartquotes: bool = False,
+    ellipses: bool = False,
     line_wrapper: LineWrapper | None = None,
 ) -> str:
     """
@@ -130,6 +132,8 @@ def fill_markdown(
         doc_cleanups(document)
     if smartquotes:
         rewrite_text_content(document, smart_quotes, coalesce_lines=True)
+    if ellipses:
+        rewrite_text_content(document, apply_ellipses, coalesce_lines=True)
     result = marko.render(document)
 
     # Reattach frontmatter if it was present

{flowmark-0.5.0 → flowmark-0.5.2}/src/flowmark/reformat_api.py

@@ -15,6 +15,7 @@ def reformat_text(
     semantic: bool = True,
     cleanups: bool = True,
     smartquotes: bool = False,
+    ellipses: bool = False,
 ) -> str:
     """
     Reformat text or markdown and wrap lines. Simply a convenient wrapper
@@ -31,7 +32,12 @@ def reformat_text(
     else:
         # Markdown mode
         result = fill_markdown(
-            text, width=width, semantic=semantic, cleanups=cleanups, smartquotes=smartquotes
+            text,
+            width=width,
+            semantic=semantic,
+            cleanups=cleanups,
+            smartquotes=smartquotes,
+            ellipses=ellipses,
         )
 
     return result
@@ -47,6 +53,7 @@ def reformat_file(
     semantic: bool = False,
     cleanups: bool = True,
     smartquotes: bool = False,
+    ellipses: bool = False,
     make_parents: bool = True,
 ) -> None:
     """
@@ -66,6 +73,8 @@ def reformat_file(
             headers (only applies to Markdown mode).
         smartquotes: Convert straight quotes to typographic (curly) quotes and apostrophes
             (only applies to Markdown mode).
+        ellipses: Convert three dots (...) to ellipsis character (…) with normalized spacing
+            (only applies to Markdown mode).
         make_parents: Whether to make parent directories if they don't exist.
     """
     read_stdin = path == "-"
@@ -79,7 +88,7 @@ def reformat_file(
     else:
         text = Path(path).read_text()
 
-    result = reformat_text(text, width, plaintext, semantic, cleanups, smartquotes)
+    result = reformat_text(text, width, plaintext, semantic, cleanups, smartquotes, ellipses)
 
     if inplace:
         backup_suffix = ".orig" if not nobackup else ""

{flowmark-0.5.0 → flowmark-0.5.2}/src/flowmark/smartquotes.py

@@ -5,9 +5,11 @@ from re import Match, Pattern
 PARAGRAPH_BREAK_PATTERN: Pattern[str] = re.compile(r"\n\s*\n")
 
 # Pattern excludes content that contains the same type of quote characters
-# Double quotes exclude double quotes, single quotes exclude single quotes
+# Double quotes exclude double quotes, single quotes exclude single quotes.
+# Also as a special case allows quotes to start after an em dash (but not other punctuation
+# as this is more likely to be code).
 QUOTE_PATTERN: Pattern[str] = re.compile(
-    r'(^|\s)(?:"([^"\u201c\u201d]*)"|\'([^\'\u2018\u2019]*)\')(\s|$|\.|,|;|:|\?|!|—|\))',
+    r'(^|\s|—)(?:"([^"\u201c\u201d]*)"|\'([^\'\u2018\u2019]*)\')(\s|$|\.|,|;|:|\?|!|—|\))',
     re.MULTILINE,
 )