comparison lisp/simple.el @ 61121:ca079ae96939

(set-mark): Doc fix.
author Richard M. Stallman <rms@gnu.org>
date Tue, 29 Mar 2005 23:17:30 +0000
parents 43d165e3db5b
children 728460f45e1e 4da4a09e8b1b
comparison
equal deleted inserted replaced
61120:8f420e73d2eb 61121:ca079ae96939
2997 That is to say, don't use this function unless you want 2997 That is to say, don't use this function unless you want
2998 the user to see that the mark has moved, and you want the previous 2998 the user to see that the mark has moved, and you want the previous
2999 mark position to be lost. 2999 mark position to be lost.
3000 3000
3001 Normally, when a new mark is set, the old one should go on the stack. 3001 Normally, when a new mark is set, the old one should go on the stack.
3002 This is why most applications should use push-mark, not set-mark. 3002 This is why most applications should use `push-mark', not `set-mark'.
3003 3003
3004 Novice Emacs Lisp programmers often try to use the mark for the wrong 3004 Novice Emacs Lisp programmers often try to use the mark for the wrong
3005 purposes. The mark saves a location for the user's convenience. 3005 purposes. The mark saves a location for the user's convenience.
3006 Most editing commands should not alter the mark. 3006 Most editing commands should not alter the mark.
3007 To remember a location for internal use in the Lisp program, 3007 To remember a location for internal use in the Lisp program,