summaryrefslogtreecommitdiff
path: root/lisp/hi-lock.el
diff options
context:
space:
mode:
authorJuanma Barranquero <lekktu@gmail.com>2007-09-25 11:07:41 +0000
committerJuanma Barranquero <lekktu@gmail.com>2007-09-25 11:07:41 +0000
commitee44464cb40474d96920528f5bfdca35e35adc2a (patch)
tree7e25e0ae30e5ca9d4d6e8a8637a43e2da897c2c9 /lisp/hi-lock.el
parentcc6650afd62e15a828d7f751dba72ca096d647f6 (diff)
downloademacs-ee44464cb40474d96920528f5bfdca35e35adc2a.tar.gz
(hi-lock-write-interactive-patterns): Use `mapc' rather than `mapcar'.
Diffstat (limited to 'lisp/hi-lock.el')
-rw-r--r--lisp/hi-lock.el4
1 files changed, 2 insertions, 2 deletions
diff --git a/lisp/hi-lock.el b/lisp/hi-lock.el
index b5e62e7a909..d65dd01ee1c 100644
--- a/lisp/hi-lock.el
+++ b/lisp/hi-lock.el
@@ -309,7 +309,7 @@ called interactively, are:
Write active REGEXPs into buffer as comments (if possible). They may
be read the next time file is loaded or when the \\[hi-lock-find-patterns] command
is issued. The inserted regexps are in the form of font lock keywords.
- (See `font-lock-keywords'.) They may be edited and re-loaded with \\[hi-lock-find-patterns],
+ (See `font-lock-keywords'.) They may be edited and re-loaded with \\[hi-lock-find-patterns],
any valid `font-lock-keywords' form is acceptable. When a file is
loaded the patterns are read if `hi-lock-file-patterns-policy is
'ask and the user responds y to the prompt, or if
@@ -515,7 +515,7 @@ be found in variable `hi-lock-interactive-patterns'."
(if (null hi-lock-interactive-patterns)
(error "There are no interactive patterns"))
(let ((beg (point)))
- (mapcar
+ (mapc
(lambda (pattern)
(insert (format "%s: (%s)\n"
hi-lock-file-patterns-prefix