From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: lispref typos Date: Sat, 07 Jan 2006 15:26:24 +0200 Message-ID: References: <43BE99FB.7050905@gmx.at> <43BF9ACF.6030005@gmx.at> Reply-To: Eli Zaretskii NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1136643816 9766 80.91.229.2 (7 Jan 2006 14:23:36 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 7 Jan 2006 14:23:36 +0000 (UTC) Cc: nickrob@snap.net.nz, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jan 07 15:23:34 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1EvEyd-0005zw-8N for ged-emacs-devel@m.gmane.org; Sat, 07 Jan 2006 15:23:27 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EvF0S-0000mE-LO for ged-emacs-devel@m.gmane.org; Sat, 07 Jan 2006 09:25:20 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EvE7T-0005GH-NV for emacs-devel@gnu.org; Sat, 07 Jan 2006 08:28:32 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EvE7O-0005El-5m for emacs-devel@gnu.org; Sat, 07 Jan 2006 08:28:30 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EvE7M-0005E3-Tz for emacs-devel@gnu.org; Sat, 07 Jan 2006 08:28:25 -0500 Original-Received: from [192.114.186.66] (helo=romy.inter.net.il) by monty-python.gnu.org with esmtp (Exim 4.34) id 1EvE9I-0004Gq-7N for emacs-devel@gnu.org; Sat, 07 Jan 2006 08:30:24 -0500 Original-Received: from HOME-C4E4A596F7 (IGLD-84-228-137-57.inter.net.il [84.228.137.57]) by romy.inter.net.il (MOS 3.7.3-GA) with ESMTP id DIC50555 (AUTH halo1); Sat, 7 Jan 2006 15:26:22 +0200 (IST) Original-To: martin rudalics In-reply-to: <43BF9ACF.6030005@gmx.at> (message from martin rudalics on Sat, 07 Jan 2006 11:41:19 +0100) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:48817 Archived-At: > Date: Sat, 07 Jan 2006 11:41:19 +0100 > From: martin rudalics > CC: emacs-devel@gnu.org, Nick Roberts > > > 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 > > ============================================================ > >