aboutsummaryrefslogtreecommitdiffstats
path: root/lisp/repeat.el
diff options
context:
space:
mode:
authorPaul Eggert2011-11-22 23:03:56 -0800
committerPaul Eggert2011-11-22 23:03:56 -0800
commitee7683ebb70c308e596103e379ef6b91d001eebc (patch)
tree45382191619e27df7106a8d990bc03903d0fa03f /lisp/repeat.el
parent6b21de180fba10432988d94d2b8f3e2521be5b17 (diff)
downloademacs-ee7683ebb70c308e596103e379ef6b91d001eebc.tar.gz
emacs-ee7683ebb70c308e596103e379ef6b91d001eebc.zip
Spelling fixes.
Diffstat (limited to 'lisp/repeat.el')
-rw-r--r--lisp/repeat.el2
1 files changed, 1 insertions, 1 deletions
diff --git a/lisp/repeat.el b/lisp/repeat.el
index 8ddc8d41429..13b6a1d2315 100644
--- a/lisp/repeat.el
+++ b/lisp/repeat.el
@@ -363,7 +363,7 @@ recently executed command not bound to an input event\"."
363 363
364;; OK, there's one situation left where that doesn't work correctly: when the 364;; OK, there's one situation left where that doesn't work correctly: when the
365;; most recent self-insertion provoked an auto-fill. The problem is that 365;; most recent self-insertion provoked an auto-fill. The problem is that
366;; unravelling the undo information after an auto-fill is too hard, since all 366;; unraveling the undo information after an auto-fill is too hard, since all
367;; kinds of stuff can get in there as a result of comment prefixes etc. It'd 367;; kinds of stuff can get in there as a result of comment prefixes etc. It'd
368;; be possible to advise do-auto-fill to record the most recent 368;; be possible to advise do-auto-fill to record the most recent
369;; self-insertion before it does its thing, but that's a performance hit on 369;; self-insertion before it does its thing, but that's a performance hit on