lispref typos

lispref typos

[martin rudalics]

*** display.texi	Fri Dec  2 10:16:32 2005
--- display.texi	Fri Jan  6 17:16:32 2006
***************
*** 1099,1105 ****
   beginning and end.  It also has properties that you can examine and set;
   these affect the display of the text within the overlay.

! An overlays uses markers to record its beginning and end; thus,
   editing the text of the buffer adjusts the beginning and end of each
   overlay so that it stays with the text.  When you create the overlay,
   you can specify whether text inserted at the beginning should be
--- 1099,1105 ----
   beginning and end.  It also has properties that you can examine and set;
   these affect the display of the text within the overlay.

! An overlay uses markers to record its beginning and end; thus,
   editing the text of the buffer adjusts the beginning and end of each
   overlay so that it stays with the text.  When you create the overlay,
   you can specify whether text inserted at the beginning should be
***************
*** 1737,1743 ****
   different kinds of terminals.  It should be an alist whose elements
   have the form @code{(@var{display} @var{atts})}.  Each element's
   @sc{car}, @var{display}, specifies a class of terminals.  (The first
! element, if it s @sc{car} is @code{default}, is special---it specifies
   defaults for the remaining elements).  The element's @sc{cadr},
   @var{atts}, is a list of face attributes and their values; it
   specifies what the face should look like on that kind of terminal.
--- 1737,1743 ----
   different kinds of terminals.  It should be an alist whose elements
   have the form @code{(@var{display} @var{atts})}.  Each element's
   @sc{car}, @var{display}, specifies a class of terminals.  (The first
! element, if it's @sc{car} is @code{default}, is special---it specifies
   defaults for the remaining elements).  The element's @sc{cadr},
   @var{atts}, is a list of face attributes and their values; it
   specifies what the face should look like on that kind of terminal.
***************
*** 4258,4265 ****

     For convenience, there are two sorts of button-creation functions,
   those that add button properties to an existing region of a buffer,
! called @code{make-...button}, and those also insert the button text,
! called @code{insert-...button}.

     The button-creation functions all take the @code{&rest} argument
   @var{properties}, which should be a sequence of @var{property value}
--- 4258,4265 ----

     For convenience, there are two sorts of button-creation functions,
   those that add button properties to an existing region of a buffer,
! called @code{make-...button}, and those that also insert the button
! text, called @code{insert-...button}.

     The button-creation functions all take the @code{&rest} argument
   @var{properties}, which should be a sequence of @var{property value}

----------

*** keymaps.texi	Thu Dec 15 11:32:56 2005
--- keymaps.texi	Fri Jan  6 17:17:18 2006
***************
*** 569,575 ****
   text or overlay property.  If that is non-@code{nil}, it is the first
   keymap to be processed, in normal circumstances.

!   However, there are also special ways for program can to substitute
   other keymaps for some of those.  The variable
   @code{overriding-local-map}, if non-@code{nil}, specifies a keymap
   that replaces all the usual active keymaps except the global keymap.
--- 569,575 ----
   text or overlay property.  If that is non-@code{nil}, it is the first
   keymap to be processed, in normal circumstances.

!   However, there are also special ways for programs to substitute
   other keymaps for some of those.  The variable
   @code{overriding-local-map}, if non-@code{nil}, specifies a keymap
   that replaces all the usual active keymaps except the global keymap.

----------

*** modes.texi	Thu Jan  5 07:44:42 2006
--- modes.texi	Fri Jan  6 12:27:08 2006
***************
*** 1423,1429 ****
   @end defmac

     The initial value must be @code{nil} except in cases where (1) the
! mode is preloaded in Emacs, or (2) it is painless to for loading to
   enable the mode even though the user did not request it.  For
   instance, if the mode has no effect unless something else is enabled,
   and will always be loaded by that time, enabling it by default is
--- 1423,1429 ----
   @end defmac

     The initial value must be @code{nil} except in cases where (1) the
! mode is preloaded in Emacs, or (2) it is painless for loading to
   enable the mode even though the user did not request it.  For
   instance, if the mode has no effect unless something else is enabled,
   and will always be loaded by that time, enabling it by default is
***************
*** 2254,2260 ****
   finds the next ``definition'' to put in the buffer index, scanning
   backward in the buffer from point.  It should return @code{nil} if it
   doesn't find another ``definition'' before point.  Otherwise it should
! leave point at the place it finds a ``definition,'' and return any
   non-@code{nil} value.

   Setting this variable makes it buffer-local in the current buffer.
--- 2254,2260 ----
   finds the next ``definition'' to put in the buffer index, scanning
   backward in the buffer from point.  It should return @code{nil} if it
   doesn't find another ``definition'' before point.  Otherwise it should
! leave point at the place it finds a ``definition'' and return any
   non-@code{nil} value.

   Setting this variable makes it buffer-local in the current buffer.

----------

*** positions.texi	Sat Nov  5 20:46:20 2005
--- positions.texi	Fri Jan  6 12:29:02 2006
***************
*** 417,423 ****
   @defun line-number-at-pos &optional pos
   @cindex line number
   This function returns the line number in the current buffer
! corresponding the buffer position @var{pos}.  If @var{pos} is @code{nil}
   or omitted, the current buffer position is used.
   @end defun

--- 417,423 ----
   @defun line-number-at-pos &optional pos
   @cindex line number
   This function returns the line number in the current buffer
! corresponding to the buffer position @var{pos}.  If @var{pos} is @code{nil}
   or omitted, the current buffer position is used.
   @end defun

----------

*** text.texi	Thu Jan  5 07:44:42 2006
--- text.texi	Fri Jan  6 12:34:50 2006
***************
*** 2714,2720 ****

   @defun remove-list-of-text-properties start end list-of-properties &optional object
   Like @code{remove-text-properties} except that
! @var{list-of-properties} is a list property names only, not an
   alternating list of property names and values.
   @end defun

--- 2714,2720 ----

   @defun remove-list-of-text-properties start end list-of-properties &optional object
   Like @code{remove-text-properties} except that
! @var{list-of-properties} is a list of property names only, not an
   alternating list of property names and values.
   @end defun

Re: lispref typos

[Eli Zaretskii]

> Date: Fri, 06 Jan 2006 17:25:31 +0100
> From: martin rudalics <rudalics@gmx.at>
> 
> *** display.texi	Fri Dec  2 10:16:32 2005
> --- display.texi	Fri Jan  6 17:16:32 2006

I couldn't apply your patches: your mailer somehow munged them.  I
tried to fix the whitespace by hand, but that didn't work as well.
Sorry.

lispref typos

[Nick Roberts]

These changes look good apart from:

   element, if it s @sc{car} is @code{default}, is special---it specifies

to

   element, if it's @sc{car} is @code{default}, is special---it specifies

It should read:

   element, if its @sc{car} is @code{default}, is special---it specifies

(it's - contraction of "it is",  its - possessive pronoun)

Nick

Re: lispref typos

[martin rudalics]

 > I couldn't apply your patches: your mailer somehow munged them.  I
 > tried to fix the whitespace by hand, but that didn't work as well.
 > Sorry.

Sorry for the inconvenience.  Please try again with the patches below.
I also applied Nick's correction.

============================================================
*** display.texi	Fri Dec  2 10:16:32 2005
--- display.texi	Sat Jan  7 10:12:44 2006
***************
*** 1099,1105 ****
   beginning and end.  It also has properties that you can examine and set;
   these affect the display of the text within the overlay.

! An overlays uses markers to record its beginning and end; thus,
   editing the text of the buffer adjusts the beginning and end of each
   overlay so that it stays with the text.  When you create the overlay,
   you can specify whether text inserted at the beginning should be
--- 1099,1105 ----
   beginning and end.  It also has properties that you can examine and set;
   these affect the display of the text within the overlay.

! An overlay uses markers to record its beginning and end; thus,
   editing the text of the buffer adjusts the beginning and end of each
   overlay so that it stays with the text.  When you create the overlay,
   you can specify whether text inserted at the beginning should be
***************
*** 1737,1743 ****
   different kinds of terminals.  It should be an alist whose elements
   have the form @code{(@var{display} @var{atts})}.  Each element's
   @sc{car}, @var{display}, specifies a class of terminals.  (The first
! element, if it s @sc{car} is @code{default}, is special---it specifies
   defaults for the remaining elements).  The element's @sc{cadr},
   @var{atts}, is a list of face attributes and their values; it
   specifies what the face should look like on that kind of terminal.
--- 1737,1743 ----
   different kinds of terminals.  It should be an alist whose elements
   have the form @code{(@var{display} @var{atts})}.  Each element's
   @sc{car}, @var{display}, specifies a class of terminals.  (The first
! element, if its @sc{car} is @code{default}, is special---it specifies
   defaults for the remaining elements).  The element's @sc{cadr},
   @var{atts}, is a list of face attributes and their values; it
   specifies what the face should look like on that kind of terminal.
***************
*** 4258,4265 ****

     For convenience, there are two sorts of button-creation functions,
   those that add button properties to an existing region of a buffer,
! called @code{make-...button}, and those also insert the button text,
! called @code{insert-...button}.

     The button-creation functions all take the @code{&rest} argument
   @var{properties}, which should be a sequence of @var{property value}
--- 4258,4265 ----

     For convenience, there are two sorts of button-creation functions,
   those that add button properties to an existing region of a buffer,
! called @code{make-...button}, and those that also insert the button
! text, called @code{insert-...button}.

     The button-creation functions all take the @code{&rest} argument
   @var{properties}, which should be a sequence of @var{property value}
============================================================
*** keymaps.texi	Thu Dec 15 11:32:56 2005
--- keymaps.texi	Fri Jan  6 17:17:18 2006
***************
*** 569,575 ****
   text or overlay property.  If that is non-@code{nil}, it is the first
   keymap to be processed, in normal circumstances.

!   However, there are also special ways for program can to substitute
   other keymaps for some of those.  The variable
   @code{overriding-local-map}, if non-@code{nil}, specifies a keymap
   that replaces all the usual active keymaps except the global keymap.
--- 569,575 ----
   text or overlay property.  If that is non-@code{nil}, it is the first
   keymap to be processed, in normal circumstances.

!   However, there are also special ways for programs to substitute
   other keymaps for some of those.  The variable
   @code{overriding-local-map}, if non-@code{nil}, specifies a keymap
   that replaces all the usual active keymaps except the global keymap.
============================================================
*** modes.texi	Thu Jan  5 07:44:42 2006
--- modes.texi	Fri Jan  6 12:27:08 2006
***************
*** 1423,1429 ****
   @end defmac

     The initial value must be @code{nil} except in cases where (1) the
! mode is preloaded in Emacs, or (2) it is painless to for loading to
   enable the mode even though the user did not request it.  For
   instance, if the mode has no effect unless something else is enabled,
   and will always be loaded by that time, enabling it by default is
--- 1423,1429 ----
   @end defmac

     The initial value must be @code{nil} except in cases where (1) the
! mode is preloaded in Emacs, or (2) it is painless for loading to
   enable the mode even though the user did not request it.  For
   instance, if the mode has no effect unless something else is enabled,
   and will always be loaded by that time, enabling it by default is
***************
*** 2254,2260 ****
   finds the next ``definition'' to put in the buffer index, scanning
   backward in the buffer from point.  It should return @code{nil} if it
   doesn't find another ``definition'' before point.  Otherwise it should
! leave point at the place it finds a ``definition,'' and return any
   non-@code{nil} value.

   Setting this variable makes it buffer-local in the current buffer.
--- 2254,2260 ----
   finds the next ``definition'' to put in the buffer index, scanning
   backward in the buffer from point.  It should return @code{nil} if it
   doesn't find another ``definition'' before point.  Otherwise it should
! leave point at the place it finds a ``definition'' and return any
   non-@code{nil} value.

   Setting this variable makes it buffer-local in the current buffer.
============================================================
*** positions.texi	Sat Nov  5 20:46:20 2005
--- positions.texi	Fri Jan  6 12:29:02 2006
***************
*** 417,423 ****
   @defun line-number-at-pos &optional pos
   @cindex line number
   This function returns the line number in the current buffer
! corresponding the buffer position @var{pos}.  If @var{pos} is @code{nil}
   or omitted, the current buffer position is used.
   @end defun

--- 417,423 ----
   @defun line-number-at-pos &optional pos
   @cindex line number
   This function returns the line number in the current buffer
! corresponding to the buffer position @var{pos}.  If @var{pos} is @code{nil}
   or omitted, the current buffer position is used.
   @end defun

============================================================
*** text.texi	Thu Jan  5 07:44:42 2006
--- text.texi	Fri Jan  6 12:34:50 2006
***************
*** 2714,2720 ****

   @defun remove-list-of-text-properties start end list-of-properties &optional object
   Like @code{remove-text-properties} except that
! @var{list-of-properties} is a list property names only, not an
   alternating list of property names and values.
   @end defun

--- 2714,2720 ----

   @defun remove-list-of-text-properties start end list-of-properties &optional object
   Like @code{remove-text-properties} except that
! @var{list-of-properties} is a list of property names only, not an
   alternating list of property names and values.
   @end defun

============================================================

Re: lispref typos

[Eli Zaretskii]

> Date: Sat, 07 Jan 2006 11:41:19 +0100
> From: martin rudalics <rudalics@gmx.at>
> CC: emacs-devel@gnu.org, Nick Roberts <nickrob@snap.net.nz>
> 
>  > I couldn't apply your patches: your mailer somehow munged them.  I
>  > tried to fix the whitespace by hand, but that didn't work as well.
>  > Sorry.
> 
> Sorry for the inconvenience.  Please try again with the patches below.

They still don't apply.  And some of the reasons are clearly visible:
look at the wrong indentation of all the lines where you actually made
changes:

> *** 1099,1105 ****
>    beginning and end.  It also has properties that you can examine and set;
>    these affect the display of the text within the overlay.
> 
> ! An overlays uses markers to record its beginning and end; thus,
>    editing the text of the buffer adjusts the beginning and end of each
>    overlay so that it stays with the text.  When you create the overlay,
>    you can specify whether text inserted at the beginning should be
> --- 1099,1105 ----

Do you see the problem? there should be 2 blanks between `!' and the
text after it, but somehow one of the blanks is missing.

Can you tell exactly how you invoke Diff and what switches you pass to
it?  Perhaps therein lies the reason for these problems.  Also, what
version of Diff is that, and on what OS it was run?

If nothing gives a clue, you could send the patches as a binary
attachment.


>    beginning and end.  It also has properties that you can examine and set;
>    these affect the display of the text within the overlay.
> 
> ! An overlay uses markers to record its beginning and end; thus,
>    editing the text of the buffer adjusts the beginning and end of each
>    overlay so that it stays with the text.  When you create the overlay,
>    you can specify whether text inserted at the beginning should be
> ***************
> *** 1737,1743 ****
>    different kinds of terminals.  It should be an alist whose elements
>    have the form @code{(@var{display} @var{atts})}.  Each element's
>    @sc{car}, @var{display}, specifies a class of terminals.  (The first
> ! element, if it s @sc{car} is @code{default}, is special---it specifies
>    defaults for the remaining elements).  The element's @sc{cadr},
>    @var{atts}, is a list of face attributes and their values; it
>    specifies what the face should look like on that kind of terminal.
> --- 1737,1743 ----
>    different kinds of terminals.  It should be an alist whose elements
>    have the form @code{(@var{display} @var{atts})}.  Each element's
>    @sc{car}, @var{display}, specifies a class of terminals.  (The first
> ! element, if its @sc{car} is @code{default}, is special---it specifies
>    defaults for the remaining elements).  The element's @sc{cadr},
>    @var{atts}, is a list of face attributes and their values; it
>    specifies what the face should look like on that kind of terminal.
> ***************
> *** 4258,4265 ****
> 
>      For convenience, there are two sorts of button-creation functions,
>    those that add button properties to an existing region of a buffer,
> ! called @code{make-...button}, and those also insert the button text,
> ! called @code{insert-...button}.
> 
>      The button-creation functions all take the @code{&rest} argument
>    @var{properties}, which should be a sequence of @var{property value}
> --- 4258,4265 ----
> 
>      For convenience, there are two sorts of button-creation functions,
>    those that add button properties to an existing region of a buffer,
> ! called @code{make-...button}, and those that also insert the button
> ! text, called @code{insert-...button}.
> 
>      The button-creation functions all take the @code{&rest} argument
>    @var{properties}, which should be a sequence of @var{property value}
> ============================================================
> *** keymaps.texi	Thu Dec 15 11:32:56 2005
> --- keymaps.texi	Fri Jan  6 17:17:18 2006
> ***************
> *** 569,575 ****
>    text or overlay property.  If that is non-@code{nil}, it is the first
>    keymap to be processed, in normal circumstances.
> 
> !   However, there are also special ways for program can to substitute
>    other keymaps for some of those.  The variable
>    @code{overriding-local-map}, if non-@code{nil}, specifies a keymap
>    that replaces all the usual active keymaps except the global keymap.
> --- 569,575 ----
>    text or overlay property.  If that is non-@code{nil}, it is the first
>    keymap to be processed, in normal circumstances.
> 
> !   However, there are also special ways for programs to substitute
>    other keymaps for some of those.  The variable
>    @code{overriding-local-map}, if non-@code{nil}, specifies a keymap
>    that replaces all the usual active keymaps except the global keymap.
> ============================================================
> *** modes.texi	Thu Jan  5 07:44:42 2006
> --- modes.texi	Fri Jan  6 12:27:08 2006
> ***************
> *** 1423,1429 ****
>    @end defmac
> 
>      The initial value must be @code{nil} except in cases where (1) the
> ! mode is preloaded in Emacs, or (2) it is painless to for loading to
>    enable the mode even though the user did not request it.  For
>    instance, if the mode has no effect unless something else is enabled,
>    and will always be loaded by that time, enabling it by default is
> --- 1423,1429 ----
>    @end defmac
> 
>      The initial value must be @code{nil} except in cases where (1) the
> ! mode is preloaded in Emacs, or (2) it is painless for loading to
>    enable the mode even though the user did not request it.  For
>    instance, if the mode has no effect unless something else is enabled,
>    and will always be loaded by that time, enabling it by default is
> ***************
> *** 2254,2260 ****
>    finds the next ``definition'' to put in the buffer index, scanning
>    backward in the buffer from point.  It should return @code{nil} if it
>    doesn't find another ``definition'' before point.  Otherwise it should
> ! leave point at the place it finds a ``definition,'' and return any
>    non-@code{nil} value.
> 
>    Setting this variable makes it buffer-local in the current buffer.
> --- 2254,2260 ----
>    finds the next ``definition'' to put in the buffer index, scanning
>    backward in the buffer from point.  It should return @code{nil} if it
>    doesn't find another ``definition'' before point.  Otherwise it should
> ! leave point at the place it finds a ``definition'' and return any
>    non-@code{nil} value.
> 
>    Setting this variable makes it buffer-local in the current buffer.
> ============================================================
> *** positions.texi	Sat Nov  5 20:46:20 2005
> --- positions.texi	Fri Jan  6 12:29:02 2006
> ***************
> *** 417,423 ****
>    @defun line-number-at-pos &optional pos
>    @cindex line number
>    This function returns the line number in the current buffer
> ! corresponding the buffer position @var{pos}.  If @var{pos} is @code{nil}
>    or omitted, the current buffer position is used.
>    @end defun
> 
> --- 417,423 ----
>    @defun line-number-at-pos &optional pos
>    @cindex line number
>    This function returns the line number in the current buffer
> ! corresponding to the buffer position @var{pos}.  If @var{pos} is @code{nil}
>    or omitted, the current buffer position is used.
>    @end defun
> 
> ============================================================
> *** text.texi	Thu Jan  5 07:44:42 2006
> --- text.texi	Fri Jan  6 12:34:50 2006
> ***************
> *** 2714,2720 ****
> 
>    @defun remove-list-of-text-properties start end list-of-properties &optional object
>    Like @code{remove-text-properties} except that
> ! @var{list-of-properties} is a list property names only, not an
>    alternating list of property names and values.
>    @end defun
> 
> --- 2714,2720 ----
> 
>    @defun remove-list-of-text-properties start end list-of-properties &optional object
>    Like @code{remove-text-properties} except that
> ! @var{list-of-properties} is a list of property names only, not an
>    alternating list of property names and values.
>    @end defun
> 
> ============================================================
> 
>