Mercurial > emacs
changeset 57705:804f28bbd89c
(syms_of_buffer): Fix a few typos.
| author | David Kastrup <dak@gnu.org> |
|---|---|
| date | Tue, 26 Oct 2004 09:45:16 +0000 |
| parents | 4ff1d695430a |
| children | 26ee7f4433d0 |
| files | src/ChangeLog src/buffer.c |
| diffstat | 2 files changed, 10 insertions(+), 6 deletions(-) [+] |
line wrap: on
line diff
--- a/src/ChangeLog Tue Oct 26 09:28:01 2004 +0000 +++ b/src/ChangeLog Tue Oct 26 09:45:16 2004 +0000 @@ -1,3 +1,7 @@ +2004-10-26 David Kastrup <dak@gnu.org> + + * buffer.c (syms_of_buffer): Fix a few typos. + 2004-10-26 Jan Dj,Ad(Brv <jan.h.d@swipnet.se> * xsmfns.c: Put empty line between comment and function body.
--- a/src/buffer.c Tue Oct 26 09:28:01 2004 +0000 +++ b/src/buffer.c Tue Oct 26 09:45:16 2004 +0000 @@ -5812,21 +5812,21 @@ doc: /* Non-nil means that Emacs should use caches to handle long lines more quickly. Normally, the line-motion functions work by scanning the buffer for -newlines. Columnar operations (like move-to-column and -compute-motion) also work by scanning the buffer, summing character +newlines. Columnar operations (like `move-to-column' and +`compute-motion') also work by scanning the buffer, summing character widths as they go. This works well for ordinary text, but if the buffer's lines are very long (say, more than 500 characters), these motion functions will take longer to execute. Emacs may also take longer to update the display. -If cache-long-line-scans is non-nil, these motion functions cache the +If `cache-long-line-scans' is non-nil, these motion functions cache the results of their scans, and consult the cache to avoid rescanning regions of the buffer until the text is modified. The caches are most beneficial when they prevent the most searching---that is, when the buffer contains long lines and large regions of characters with the same, fixed screen width. -When cache-long-line-scans is non-nil, processing short lines will +When `cache-long-line-scans' is non-nil, processing short lines will become slightly slower (because of the overhead of consulting the cache), and the caches will use memory roughly proportional to the number of newlines and characters whose screen width varies. @@ -5906,8 +5906,8 @@ hollow display a hollow box cursor bar display a vertical bar cursor with default width (bar . WIDTH) display a vertical bar cursor with width WIDTH - hbar display a horisontal bar cursor with default width - (hbar . WIDTH) display a horisontal bar cursor with width WIDTH + hbar display a horizontal bar cursor with default width + (hbar . WIDTH) display a horizontal bar cursor with width WIDTH ANYTHING ELSE display a hollow box cursor. When the buffer is displayed in a nonselected window,