summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoost Kremers <joostkremers@fastmail.com>2026-01-18 12:03:27 +0100
committerJoost Kremers <joostkremers@fastmail.com>2026-01-18 12:03:27 +0100
commit9bc65bf17162f4839e6ef8f7126ffe107681f8a4 (patch)
tree893d3b41f82c3365fcd8f259d6ac7faa0b36cc9e
parent5c9fadbae23d5ba51b65a4620354621ee8c1907d (diff)
Small change to the README.externals/cm-mode
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index dc3fe26..c252aab 100644
--- a/README.md
+++ b/README.md
@@ -37,7 +37,7 @@ To mitigate this problem, you can use soft wrap (with `visual-line-mode`). Since
Comments can be used to keep track of who made a particular change. If you want to do this automatically, you can set the variable `cm-author`. When this variable is set, its value is automatically added as a comment to every change you make, preceded by `@`. If you explicitly make a comment with `C-c * c`, the value of `cm-author` is inserted at the beginning of the comment.
-The variable `cm-author` can be set through Customize or with `setq-default` in your init file. This sets the global value. You can override this global value in a particular buffer by setting a buffer-local value. There are two ways to do this: you can use `C-c * t` (for *tag*), which will only set the value for the current session, or you can use a file-local (or directory-local) variable, which makes sure the value is set every time the file is loaded. (Note: if you use [Pandoc](http://johnmacfarlane.net/pandoc/), you can specify file-local variables with html comments, since Pandoc ignores html comments for all output formats.)
+The variable `cm-author` can be set through Customize or with `setq-default` in your init file. This sets the global value. You can override this global value in a particular buffer by setting a buffer-local value. There are two ways to do this: you can use `C-c * t` (for *tag*), which will only set the value for the current session, or you can use a directory-local variable, which makes sure the value is set every time the file is loaded. (You could also use a file-local variable, but that is less than ideal in a document that you cooperate on with others, which is usually the case when you record who is making changes.)
If `cm-author` is set, a new addition or deletion that is adjacent to an existing one is not combined with it if it has a different author tag. This way you can add changes to a text that already has changes from another author and still keep track of who did what. This *only* works for changes that have a comment with an author tag, however. If the existing addition/deletion does not have an author tag, any addition/deletion made adjacent to it is simply combined with it.