aboutsummaryrefslogtreecommitdiffstats
path: root/lisp/simple.el
diff options
context:
space:
mode:
authorRichard M. Stallman <[email protected]>2005-03-29 23:17:30 +0000
committerRichard M. Stallman <[email protected]>2005-03-29 23:17:30 +0000
commitf59006cb6e45c0611c6658e8375369f930e02589 (patch)
treea200984803e6bffe06bab5d9b9245aa896227710 /lisp/simple.el
parent39df553f4d983f57c83fcca5c3f6ccd6e9d24c06 (diff)
(set-mark): Doc fix.
Diffstat (limited to 'lisp/simple.el')
-rw-r--r--lisp/simple.el2
1 files changed, 1 insertions, 1 deletions
diff --git a/lisp/simple.el b/lisp/simple.el
index 4d1369dded..753391dabe 100644
--- a/lisp/simple.el
+++ b/lisp/simple.el
@@ -2999,7 +2999,7 @@ the user to see that the mark has moved, and you want the previous
mark position to be lost.
Normally, when a new mark is set, the old one should go on the stack.
-This is why most applications should use push-mark, not set-mark.
+This is why most applications should use `push-mark', not `set-mark'.
Novice Emacs Lisp programmers often try to use the mark for the wrong
purposes. The mark saves a location for the user's convenience.