[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] /srv/bzr/emacs/trunk r107243: Improve fringe documentation
From: |
Chong Yidong |
Subject: |
[Emacs-diffs] /srv/bzr/emacs/trunk r107243: Improve fringe documentation in Lisp manual. |
Date: |
Sat, 11 Feb 2012 22:56:54 +0800 |
User-agent: |
Bazaar (2.3.1) |
------------------------------------------------------------
revno: 107243
committer: Chong Yidong <address@hidden>
branch nick: trunk
timestamp: Sat 2012-02-11 22:56:54 +0800
message:
Improve fringe documentation in Lisp manual.
* doc/lispref/display.texi (Fringe Indicators): Add xref to Fringe Bitmaps.
Move the list of standard bitmaps there.
(Fringe Cursors): Rewrite for clarity.
(Fringe Bitmaps): Consolidate the list of standard bitmaps here.
modified:
doc/lispref/ChangeLog
doc/lispref/display.texi
=== modified file 'doc/lispref/ChangeLog'
--- a/doc/lispref/ChangeLog 2012-02-11 13:32:02 +0000
+++ b/doc/lispref/ChangeLog 2012-02-11 14:56:54 +0000
@@ -1,5 +1,10 @@
2012-02-11 Chong Yidong <address@hidden>
+ * display.texi (Fringe Indicators): Add xref to Fringe Bitmaps.
+ Move the list of standard bitmaps there.
+ (Fringe Cursors): Rewrite for clarity.
+ (Fringe Bitmaps): Consolidate the list of standard bitmaps here.
+
* commands.texi (Command Overview): Mention read-key.
(Using Interactive, Interactive Call): Minor clarifications.
(Function Keys, Click Events): Avoid "input stream" terminology.
=== modified file 'doc/lispref/display.texi'
--- a/doc/lispref/display.texi 2012-02-07 07:42:12 +0000
+++ b/doc/lispref/display.texi 2012-02-11 14:56:54 +0000
@@ -3380,12 +3380,11 @@
Used for truncation and continuation lines.
@item @code{up}, @code{down}, @code{top}, @code{bottom}, @code{top-bottom}
-Used to indicate buffer boundaries when
address@hidden is address@hidden: @code{up} and
address@hidden indicate a buffer boundary lying above or below the window
-edge; @code{top} and @code{bottom} indicate the topmost and bottommost
-buffer text line; and @code{top-bottom} indicates where there is just
-one line of text in the buffer.
+Used when @code{indicate-buffer-boundaries} is address@hidden:
address@hidden and @code{down} indicate a buffer boundary lying above or
+below the window edge; @code{top} and @code{bottom} indicate the
+topmost and bottommost buffer text line; and @code{top-bottom}
+indicates where there is just one line of text in the buffer.
@item @code{empty-line}
Used to indicate empty lines when @code{indicate-empty-lines} is
@@ -3407,24 +3406,9 @@
Alternatively, @var{bitmaps} may be a single symbol which is used in
both left and right fringes.
- The standard symbols for fringe bitmaps are:
-
address@hidden
-left-arrow right-arrow up-arrow down-arrow
-left-curly-arrow right-curly-arrow
-left-triangle right-triangle
-top-left-angle top-right-angle
-bottom-left-angle bottom-right-angle
-left-bracket right-bracket
-filled-rectangle hollow-rectangle
-filled-square hollow-square
-vertical-bar horizontal-bar
-empty-line question-mark
address@hidden example
-
address@hidden
-In addition, @code{nil} represents the empty bitmap (i.e.@: an
-indicator that is not shown).
+ @xref{Fringe Bitmaps}, for a list of standard bitmap symbols and how
+to define your own. In addition, @code{nil} represents the empty
+bitmap (i.e.@: an indicator that is not shown).
When @code{fringe-indicator-alist} has a buffer-local value, and
there is no bitmap defined for a logical indicator, or the bitmap is
@@ -3442,16 +3426,6 @@
bitmaps are used to represent the cursor in the fringe depending on
the current buffer's cursor type.
address@hidden @asis
address@hidden Logical cursor types:
address@hidden , @code{hollow}, @code{bar},
address@hidden, @code{hollow-small}.
address@hidden table
-
-The @code{hollow-small} type is used instead of @code{hollow} when the
-normal @code{hollow-rectangle} bitmap is too tall to fit on a specific
-display line.
-
@defopt overflow-newline-into-fringe
If this is address@hidden, lines exactly as wide as the window (not
counting the final newline character) are not continued. Instead,
@@ -3462,24 +3436,31 @@
@defvar fringe-cursor-alist
This variable specifies the mapping from logical cursor type to the
actual fringe bitmaps displayed in the right fringe. The value is an
-alist where each element @code{(@var{cursor} . @var{bitmap})} specifies
-the fringe bitmaps used to display a specific logical cursor type in
-the fringe. Here, @var{cursor} specifies the logical cursor type and
address@hidden is a symbol specifying the fringe bitmap to be displayed
-for that logical cursor type.
+alist where each element has the form @code{(@var{cursor-type}
+. @var{bitmap})}, which means to use the fringe bitmap @var{bitmap} to
+display cursors of type @var{cursor-type}.
+
+Each @var{cursor-type} should be one of @code{box}, @code{hollow},
address@hidden, @code{hbar}, or @code{hollow-small}. The first four have
+the same meanings as in the @code{cursor-type} frame parameter
+(@pxref{Cursor Parameters}). The @code{hollow-small} type is used
+instead of @code{hollow} when the normal @code{hollow-rectangle}
+bitmap is too tall to fit on a specific display line.
+
+Each @var{bitmap} should be a symbol specifying the fringe bitmap to
+be displayed for that logical cursor type.
address@hidden
+See the next subsection for details.
address@hidden iftex
address@hidden
address@hidden Bitmaps}.
address@hidden ifnottex
When @code{fringe-cursor-alist} has a buffer-local value, and there is
no bitmap defined for a cursor type, the corresponding value from the
default value of @code{fringes-indicator-alist} is used.
@end defvar
-Standard bitmaps for displaying the cursor in right fringe:
address@hidden
-filled-rectangle hollow-rectangle filled-square hollow-square
-vertical-bar horizontal-bar
address@hidden example
-
-
@node Fringe Bitmaps
@subsection Fringe Bitmaps
@cindex fringe bitmaps
@@ -3487,22 +3468,74 @@
The @dfn{fringe bitmaps} are the actual bitmaps which represent the
logical fringe indicators for truncated or continued lines, buffer
-boundaries, overlay arrow, etc. Fringe bitmap symbols have their own
-name space. The fringe bitmaps are shared by all frames and windows.
-You can redefine the built-in fringe bitmaps, and you can define new
-fringe bitmaps.
-
- The way to display a bitmap in the left or right fringes for a given
-line in a window is by specifying the @code{display} property for one
-of the characters that appears in it. Use a display specification of
-the form @code{(left-fringe @var{bitmap} address@hidden)} or
address@hidden(right-fringe @var{bitmap} address@hidden)} (@pxref{Display
-Property}). Here, @var{bitmap} is a symbol identifying the bitmap you
-want, and @var{face} (which is optional) is the name of the face whose
-colors should be used for displaying the bitmap, instead of the
-default @code{fringe} face. @var{face} is automatically merged with
-the @code{fringe} face, so normally @var{face} need only specify the
-foreground color for the bitmap.
+boundaries, overlay arrows, etc. Each bitmap is represented by a
+symbol.
address@hidden
+These symbols are referred to by the variables
address@hidden and @code{fringe-cursor-alist},
+described in the previous subsections.
address@hidden iftex
address@hidden
+These symbols are referred to by the variable
address@hidden, which maps fringe indicators to bitmaps
+(@pxref{Fringe Indicators}), and the variable
address@hidden, which maps fringe cursors to bitmaps
+(@pxref{Fringe Cursors}).
address@hidden ifnottex
+
+ Lisp programs can also directly display a bitmap in the left or
+right fringe, by using a @code{display} property for one of the
+characters appearing in the line (@pxref{Other Display Specs}). Such
+a display specification has the form
+
address@hidden
+(left-fringe @var{bitmap} address@hidden)
address@hidden example
+
address@hidden
+or
+
address@hidden
+(right-fringe @var{bitmap} address@hidden)
address@hidden example
+
address@hidden
+The symbol @var{bitmap} identifies the bitmap to display. The
+optional @var{face} names a face whose foreground color is used to
+display the bitmap; this face is automatically merged with the
address@hidden face.
+
+ Here is a list of the standard fringe bitmaps defined in Emacs, and
+how they are currently used in Emacs (via
address@hidden and @code{fringe-cursor-alist}):
+
address@hidden @asis
address@hidden @code{left-arrow}, @code{right-arrow}
+Used to indicate truncated lines.
+
address@hidden @code{left-curly-arrow}, @code{right-curly-arrow}
+Used to indicate continued lines.
+
address@hidden @code{right-triangle}, @code{left-triangle}
+The former is used by overlay arrows. The latter is unused.
+
address@hidden @code{up-arrow}, @code{down-arrow}, @code{top-left-angle}
@code{top-right-angle}
address@hidden @code{bottom-left-angle}, @code{bottom-right-angle}
address@hidden @code{top-right-angle}, @code{top-left-angle}
address@hidden @code{left-bracket}, @code{right-bracket},
@code{top-right-angle}, @code{top-left-angle}
+Used to indicate buffer boundaries.
+
address@hidden @code{filled-rectangle}, @code{hollow-rectangle}
address@hidden @code{filled-square}, @code{hollow-square}
address@hidden @code{vertical-bar}, @code{horizontal-bar}
+Used for different types of fringe cursors.
+
address@hidden @code{empty-line}, @code{question-mark}
+Unused.
address@hidden table
+
address@hidden
+The next subsection describes how to define your own fringe bitmaps.
@defun fringe-bitmaps-at-pos &optional pos window
This function returns the fringe bitmaps of the display line
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Emacs-diffs] /srv/bzr/emacs/trunk r107243: Improve fringe documentation in Lisp manual.,
Chong Yidong <=