aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRichard M. Stallman2005-03-29 23:17:30 +0000
committerRichard M. Stallman2005-03-29 23:17:30 +0000
commitf59006cb6e45c0611c6658e8375369f930e02589 (patch)
treea200984803e6bffe06bab5d9b9245aa896227710
parent39df553f4d983f57c83fcca5c3f6ccd6e9d24c06 (diff)
downloademacs-f59006cb6e45c0611c6658e8375369f930e02589.tar.gz
emacs-f59006cb6e45c0611c6658e8375369f930e02589.zip
(set-mark): Doc fix.
-rw-r--r--lisp/simple.el2
1 files changed, 1 insertions, 1 deletions
diff --git a/lisp/simple.el b/lisp/simple.el
index 4d1369ddeda..753391dabe8 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
2999mark position to be lost. 2999mark position to be lost.
3000 3000
3001Normally, when a new mark is set, the old one should go on the stack. 3001Normally, when a new mark is set, the old one should go on the stack.
3002This is why most applications should use push-mark, not set-mark. 3002This is why most applications should use `push-mark', not `set-mark'.
3003 3003
3004Novice Emacs Lisp programmers often try to use the mark for the wrong 3004Novice Emacs Lisp programmers often try to use the mark for the wrong
3005purposes. The mark saves a location for the user's convenience. 3005purposes. The mark saves a location for the user's convenience.