APPROVE COMMIT 21.5 Index: lisp/ChangeLog =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/lisp/ChangeLog,v retrieving revision 1.601 diff -u -U0 -r1.601 ChangeLog --- lisp/ChangeLog 12 Dec 2004 02:47:06 -0000 1.601 +++ lisp/ChangeLog 13 Dec 2004 00:31:11 -0000 ＠＠ -0,0 +1,6 ＠＠ +2004-12-13 Stephen J. Turnbull <stephen(a)xemacs.org&gt; + + * simple.el (next-line): + (previous-line): + Document effect of `signal-error-on-buffer-boundary'. + Index: lisp/simple.el =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/lisp/simple.el,v retrieving revision 1.47 diff -u -r1.47 simple.el --- lisp/simple.el 20 Sep 2003 01:46:54 -0000 1.47 +++ lisp/simple.el 13 Dec 2004 00:31:18 -0000 ＠＠ -2238,7 +2238,9 ＠＠ If there is no line in the buffer after this one, behavior depends on the value of `next-line-add-newlines'. If non-nil, it inserts a newline character to create a line, and moves the cursor to that line. Otherwise it moves the -cursor to the end of the buffer. +cursor to the end of the buffer. If `signal-error-on-buffer-boundary' is +non-nil and you attempt to move past a buffer boundary, XEmacs will ring the +bell using `ding'. The command \\[set-goal-column] can be used to create a semipermanent goal column to which this command always moves. ＠＠ -2285,6 +2287,9 ＠＠ \(i.e. active region) if the Shift key is held down, a motion key is used to invoke this command, and `shifted-motion-keys-select-region' is t; see the documentation for this variable for more details. + +If `signal-error-on-buffer-boundary' is non-nil and you attempt to move past +a buffer boundary, XEmacs will ring the bell using `ding'. If you are thinking of using this in a Lisp program, consider using `forward-line' with a negative argument instead. It is usually easier -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.