aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKim F. Storm2004-09-22 23:11:12 +0000
committerKim F. Storm2004-09-22 23:11:12 +0000
commit80174a97549ed5da5911152e918cd28f0b0b3446 (patch)
treee98f26141a46c9b4a9d97e24d4553d6f963a6a80
parent9b6e4bc3d990b77a742821fb5fd8a0c1c07c85f2 (diff)
downloademacs-80174a97549ed5da5911152e918cd28f0b0b3446.tar.gz
emacs-80174a97549ed5da5911152e918cd28f0b0b3446.zip
(Display Custom): Add `overflow-newline-into-fringe',
`indicate-buffer-boundaries' and `default-indicate-buffer-boundaries'.
-rw-r--r--man/display.texi40
1 files changed, 40 insertions, 0 deletions
diff --git a/man/display.texi b/man/display.texi
index b78eb8ab939..ad3f0dfcd00 100644
--- a/man/display.texi
+++ b/man/display.texi
@@ -990,6 +990,46 @@ the value of @code{truncate-lines}. For information about side-by-side
990windows, see @ref{Split Window}. See also @ref{Display,, Display, 990windows, see @ref{Split Window}. See also @ref{Display,, Display,
991elisp, The Emacs Lisp Reference Manual}. 991elisp, The Emacs Lisp Reference Manual}.
992 992
993@vindex overflow-newline-into-fringe
994 If the variable @code{overflow-newline-into-fringe} is
995non-@code{nil} on a window system, it specifies that lines which are
996exactly as wide as the window (not counting the final newline
997character) shall not be broken into two lines on the display (with
998just the newline on the second line). Instead, the newline
999overflows into the right fringe, and the cursor will be displayed in
1000the fringe when positioned on that newline.
1001@end defvar
1002
1003@vindex indicate-buffer-boundaries
1004 On a window system, Emacs may indicate the buffer boundaries in the
1005fringes. The buffer boundaries, i.e. first and last line in the
1006buffer, can be marked with angle bitmaps in the left or right fringe.
1007This can be combined with up and down arrow bitmaps shown at the top
1008and bottom of the left or right fringe if the window can be scrolled
1009in either direction.
1010
1011The buffer-local variable @code{indicate-buffer-boundaries} controls
1012how the buffer boundaries and window scrolling is indicated in the
1013fringes.
1014
1015If the value is @code{left} or @code{right}, both angle and arrow
1016bitmaps are displayed in the left or right fringe, respectively.
1017Any other non-@code{nil} value causes the bitmap on the top line to be
1018displayed in the left fringe, and the bitmap on the bottom line in the
1019right fringe.
1020
1021If value is a cons @code{(angles . arrows)}, the car specifies the
1022position of the angle bitmaps, and the cdr specifies the position of
1023the arrow bitmaps. For example, @code{(t . right)} places the top
1024angle bitmap in left fringe, the bottom angle bitmap in right fringe,
1025and both arrow bitmaps in right fringe. To show just the angle
1026bitmaps in the left fringe, but no arrow bitmaps, use @code{(left . nil)}.
1027
1028@vindex default-indicate-buffer-boundaries
1029 The value of the variable @code{default-indicate-buffer-boundaries}
1030is the default value for @code{indicate-buffer-boundaries} in buffers
1031that do not override it.
1032
993@vindex baud-rate 1033@vindex baud-rate
994 The variable @code{baud-rate} holds the output speed of the 1034 The variable @code{baud-rate} holds the output speed of the
995terminal, as far as Emacs knows. Setting this variable does not 1035terminal, as far as Emacs knows. Setting this variable does not