aboutsummaryrefslogtreecommitdiffstats
path: root/lispref
diff options
context:
space:
mode:
authorRichard M. Stallman <[email protected]>1995-07-18 22:10:51 +0000
committerRichard M. Stallman <[email protected]>1995-07-18 22:10:51 +0000
commitea951766c562af6f2ab08016ab83bd18ffbc6168 (patch)
tree7c2aacbaff5fb222a5302b30b602ee7ea009e658 /lispref
parent878c1d73d048d949dbace5688929d2d7701706cd (diff)
Explain how redisplay updates window-start.
Diffstat (limited to 'lispref')
-rw-r--r--lispref/windows.texi10
1 files changed, 8 insertions, 2 deletions
diff --git a/lispref/windows.texi b/lispref/windows.texi
index 27925e9be8..fe6db12f2b 100644
--- a/lispref/windows.texi
+++ b/lispref/windows.texi
@@ -1003,8 +1003,14 @@ When you create a window, or display a different buffer in it, the
display-start position is set to a display-start position recently used
for the same buffer, or 1 if the buffer doesn't have any.
-For a realistic example, see the description of @code{count-lines} in
-@ref{Text Lines}.
+Redisplay updates the window-start position (if you have not specified
+it explicitly since the previous redisplay) so that point appears on the
+screen. Nothing except redisplay automatically changes the window-start
+position; if you move point, do not expect the window-start position to
+change in response until after the next redisplay.
+
+For a realistic example of using @code{window-start}, see the
+description of @code{count-lines} in @ref{Text Lines}.
@end defun
@defun window-end &optional window