git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v3 2/2] userdiff: extend Scheme support to cover other Lisp dialects

From
Johannes Sixt <j6t@kdbg.org>
Date
Jan 16, 2026, 08:49 UTC
Message-ID
<3243b63b-b0c1-42d5-beeb-df42b891f09e@kdbg.org>
In-Reply-To
<fb4c8dc5d4434deab9c8f1872f309a79351dc799.1768519120.git.gitgitgadget@gmail.com>
Am 16.01.26 um 00:18 schrieb Scott L. Burson via GitGitGadget:
Show 22 quoted lines
> From: "Scott L. Burson" <Scott@sympoiesis.com>
> 
> Common Lisp has top-level forms, such as 'defun' and 'defmacro', that
> are not matched by the current Scheme pattern.  Also, it is more
> common in CL, when defining user macros intended as top-level forms,
> to prefix their names with "def" instead of "define"; such forms are
> also not matched.  And some top-level forms don't even begin with
> "def".
> 
> On the other hand, it is an established formatting convention in the
> Lisp community that only top-level forms start at the left margin.  So
> matching any unindented line starting with an open parenthesis is an
> acceptable heuristic; false positives will be rare.
> 
> However, there are also cases where notionally top-level forms are
> grouped together within some containing form.  At least in the Common
> Lisp community, it is conventional to indent these by two spaces, or
> sometimes one.  But matching just an open parenthesis indented by two
> spaces would be too broad; so the pattern added by this commit
> requires an indented form to start with "(def".  It is believed that
> this strikes a good balance between potential false positives and
> false negatives.

The commit message doesn't mention the changes regarding the word-diff pattern. I would have prefered to have them in their own patch; it would make the patch text less obscure about what it actually changes.

> 
> Signed-off-by: Scott L. Burson <Scott@sympoiesis.com>
Show 9 quoted lines
> diff --git a/Documentation/gitattributes.adoc b/Documentation/gitattributes.adoc
> index f20041a323..a9ce5adef9 100644
> --- a/Documentation/gitattributes.adoc
> +++ b/Documentation/gitattributes.adoc
> @@ -912,6 +912,7 @@ patterns are available:
>  - `rust` suitable for source code in the Rust language.
>  
>  - `scheme` suitable for source code in the Scheme language.
> +Also handles Emacs Lisp, Common Lisp, and most other dialects.

Saying "most dialects" immediately begs the questions "which dialects are not covered" and "is the dialect that I'm using covered". Let's write it this way:

- `scheme` suitable for source code in the Lisp dialects including
  Scheme, Emacs Lisp, Common Lisp.

Note the indentation of the continuation line (see the 'bash' entry, for example).

Show 13 quoted lines
>  
>  - `tex` suitable for source code for LaTeX documents.
>  
> diff --git a/t/t4018/scheme-lisp-defun-a b/t/t4018/scheme-lisp-defun-a
> new file mode 100644
> index 0000000000..c3c750f76d
> --- /dev/null
> +++ b/t/t4018/scheme-lisp-defun-a
> @@ -0,0 +1,4 @@
> +(defun some-func (x y z) RIGHT
> +  (let ((a x)
> +        (b y))
> +        (ChangeMe a b)))
This also demonstrates that "(let" isn't picked up. Good.
Show 10 quoted lines
> diff --git a/t/t4018/scheme-lisp-defun-b b/t/t4018/scheme-lisp-defun-b
> new file mode 100644
> index 0000000000..21be305968
> --- /dev/null
> +++ b/t/t4018/scheme-lisp-defun-b
> @@ -0,0 +1,4 @@
> +(macrolet ((foo (x) `(bar ,x)))
> +  (defun mumble (x) ; RIGHT
> +    (when (> x 0)
> +      (foo x)))) ; ChangeMe

Indented "(defun" overrides the earlier structure that begins in the first column. Good.

Show 10 quoted lines
> diff --git a/t/t4018/scheme-lisp-eval-when b/t/t4018/scheme-lisp-eval-when
> new file mode 100644
> index 0000000000..5d941d7e0e
> --- /dev/null
> +++ b/t/t4018/scheme-lisp-eval-when
> @@ -0,0 +1,4 @@
> +(eval-when (:compile-toplevel :load-toplevel :execute)  ; RIGHT
> +  (set-macro-character #\?
> +		       (lambda (stream char)
> +			 `(make-pattern-variable ,(read stream)))))  ; ChangeMe
Any structure beginning in the first column is picked up. Good.
Show 16 quoted lines
> diff --git a/t/t4018/scheme-module b/t/t4018/scheme-module-a
> similarity index 100%
> rename from t/t4018/scheme-module
> rename to t/t4018/scheme-module-a
> diff --git a/t/t4018/scheme-module-b b/t/t4018/scheme-module-b
> new file mode 100644
> index 0000000000..77bc0c5eff
> --- /dev/null
> +++ b/t/t4018/scheme-module-b
> @@ -0,0 +1,6 @@
> +(module A
> +  (export with-display-exception)
> +  (extern (display-exception display-exception))
> +  (def (with-display-exception thunk) RIGHT
> +    (with-catch (lambda (e) (display-exception e (current-error-port)) e)
> +      thunk ChangeMe)))

module-a and module-b are basically the same text. module-b changes the last line, so that "(def" is picked up, while module-a changes the "(extern" line, so that "(module" is picked up. Good.

Show 13 quoted lines
> diff --git a/t/t4034/scheme/expect b/t/t4034/scheme/expect
> index 138abe9f56..72592665f1 100644
> --- a/t/t4034/scheme/expect
> +++ b/t/t4034/scheme/expect
> @@ -6,7 +6,7 @@
>  (define (<RED>myfunc a b<RESET><GREEN>my-func first second<RESET>)
>    ; This is a <RED>really<RESET><GREEN>(moderately)<RESET> cool function.
>    (<RED>this\place<RESET><GREEN>that\place<RESET> (+ 3 4))
> -  (define <RED>|the greeting|<RESET><GREEN>|a greeting|<RESET> "hello")
> +  (define <RED>|the \greeting|<RESET><GREEN>|a \greeting|<RESET> |hello there|)
>    ({<RED>}<RESET>(([<RED>]<RESET>(func-n)<RED>[<RESET>]))<RED>{<RESET>})
>    (let ((c (<RED>+ a b<RESET><GREEN>add1 first<RESET>)))
>      (format "one more than the total is %d" (<RED>add1<RESET><GREEN>+<RESET> c <GREEN>second<RESET>))))

This tests backslash between vertical bars and non-greediness of the pattern. Good.

Using the identifier "|the \| greeting|" could make the test even more complete, I think.

Show 61 quoted lines
> diff --git a/t/t4034/scheme/post b/t/t4034/scheme/post
> index 0e3bab101d..450cc234f7 100644
> --- a/t/t4034/scheme/post
> +++ b/t/t4034/scheme/post
> @@ -1,7 +1,7 @@
>  (define (my-func first second)
>    ; This is a (moderately) cool function.
>    (that\place (+ 3 4))
> -  (define |a greeting| "hello")
> +  (define |a \greeting| |hello there|)
>    ({(([(func-n)]))})
>    (let ((c (add1 first)))
>      (format "one more than the total is %d" (+ c second))))
> diff --git a/t/t4034/scheme/pre b/t/t4034/scheme/pre
> index 03d77c7c43..ba8b8ac0a4 100644
> --- a/t/t4034/scheme/pre
> +++ b/t/t4034/scheme/pre
> @@ -1,7 +1,7 @@
>  (define (myfunc a b)
>    ; This is a really cool function.
>    (this\place (+ 3 4))
> -  (define |the greeting| "hello")
> +  (define |the \greeting| |hello there|)
>    ({}(([](func-n)[])){})
>    (let ((c (+ a b)))
>      (format "one more than the total is %d" (add1 c))))
> diff --git a/userdiff.c b/userdiff.c
> index fe710a68bf..b5412e6bc3 100644
> --- a/userdiff.c
> +++ b/userdiff.c
> @@ -344,14 +344,24 @@ PATTERNS("rust",
>  	 "|[0-9][0-9_a-fA-Fiosuxz]*(\\.([0-9]*[eE][+-]?)?[0-9_fF]*)?"
>  	 "|[-+*\\/<>%&^|=!:]=|<<=?|>>=?|&&|\\|\\||->|=>|\\.{2}=|\\.{3}|::"),
>  PATTERNS("scheme",
> -	 "^[\t ]*(\\(((define|def(struct|syntax|class|method|rules|record|proto|alias)?)[-*/ \t]|(library|module|struct|class)[*+ \t]).*)$",
>  	 /*
> -	  * R7RS valid identifiers include any sequence enclosed
> -	  * within vertical lines having no backslashes
> +	  * An unindented opening parenthesis identifies a top-level
> +	  * expression in all Lisp dialects.
>  	  */
> -	 "\\|([^\\\\]*)\\|"
> -	 /* All other words should be delimited by spaces or parentheses */
> -	 "|([^][)(}{[ \t])+"),
> +	 "^(\\(.*)$\n"
> +	 /* For Scheme: a possibly indented left paren followed by a keyword. */
> +	 "^[\t ]*(\\(((define|def(struct|syntax|class|method|rules|record|proto|alias)?)[-*/ \t]|(library|module|struct|class)[*+ \t]).*)$\n"
> +	 /*
> +	  * For all Lisp dialects: a slightly indented line starting with "(def".
> +	  */
> +	 "^  ?(\\([Dd][Ee][Ff].*)$",
> +	 /*
> +	  * The union of R7RS and Common Lisp symbol syntax: allows arbitrary
> +	  * strings between vertical bars, including any escaped characters.
> +	  */
> +	 "\\|([^|\\\\]|\\\\.)*\\|"
> +	 /* All other words should be delimited by spaces or parentheses. */
> +	 "|([^][)(}{ \t])+"),
>  PATTERNS("tex", "^(\\\\((sub)*section|chapter|part)\\*{0,1}\\{.*)$",
>  	 "\\\\[a-zA-Z@]+|\\\\.|([a-zA-Z0-9]|[^\x01-\x7f])+"),
>  { .name = "default", .binary = -1 },
This change matches my expectations.
-- Hannes
Previous: Scott L. Burson via GitGitGadgetNext: Scott L. Burson
Message 21 of 27 in “diff: "lisp" userdiff_driver”
  1. diff: "lisp" userdiff_driverScott L. Burson via GitGitGadget, Nov 15, 2025
  2. Johannes SixtNov 15, 2025
  3. Scott L. BursonNov 15, 2025
  4. D. Ben KnobleNov 20, 2025
  5. Scott L. BursonNov 27, 2025
  6. Junio C HamanoNov 16, 2025
  7. Scott L. BursonNov 17, 2025
  8. Junio C HamanoNov 18, 2025
  9. 0/2 userdiff: extend Scheme support to cover other Lisp dialectsScott L. Burson via GitGitGadget, Nov 27, 2025
  10. 1/2 diff: "lisp" userdiff_driverScott L. Burson via GitGitGadget, Nov 27, 2025
  11. Scott L. BursonNov 27, 2025
  12. Johannes SixtNov 27, 2025
  13. 2/2 merge with Scheme regexp; fix bugsScott L. Burson via GitGitGadget, Nov 27, 2025
  14. Johannes SixtNov 27, 2025
  15. Johannes SixtDec 2, 2025
  16. Scott L. BursonJan 14, 2026
  17. Johannes SixtJan 14, 2026
  18. 0/2 userdiff: extend Scheme support to cover other Lisp dialectsScott L. Burson via GitGitGadget, Jan 15, 2026
  19. 1/2 userdiff: tighten word-diff test case of the scheme driverJohannes Sixt via GitGitGadget, Jan 15, 2026
  20. 2/2 userdiff: extend Scheme support to cover other Lisp dialectsScott L. Burson via GitGitGadget, Jan 15, 2026
  21. Johannes SixtJan 16, 2026
  22. Scott L. BursonJan 17, 2026
  23. Johannes SixtJan 17, 2026
  24. 0/2 userdiff: extend Scheme support to cover other Lisp dialectsScott L. Burson via GitGitGadget, Apr 15, 2026
  25. 1/2 userdiff: tighten word-diff test case of the scheme driverJohannes Sixt via GitGitGadget, Apr 15, 2026
  26. 2/2 userdiff: extend Scheme support to cover other Lisp dialectsScott L. Burson via GitGitGadget, Apr 15, 2026
  27. Johannes SixtApr 15, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.