[Emacs-diffs] Changes to emacs/lispref/tips.texi

[Juanma Barranquero]

Index: emacs/lispref/tips.texi
diff -c emacs/lispref/tips.texi:1.43 emacs/lispref/tips.texi:1.44
*** emacs/lispref/tips.texi:1.43        Mon Apr 22 03:52:50 2002
--- emacs/lispref/tips.texi     Tue Feb  4 09:47:54 2003
***************
*** 1,7 ****
  @c -*-texinfo-*-
  @c This is part of the GNU Emacs Lisp Reference Manual.
  @c Copyright (C) 1990, 1991, 1992, 1993, 1995, 1998, 1999
! @c   Free Software Foundation, Inc. 
  @c See the file elisp.texi for copying conditions.
  @setfilename ../info/tips
  @node Tips, GNU Emacs Internals, GPL, Top
--- 1,7 ----
  @c -*-texinfo-*-
  @c This is part of the GNU Emacs Lisp Reference Manual.
  @c Copyright (C) 1990, 1991, 1992, 1993, 1995, 1998, 1999
! @c   Free Software Foundation, Inc.
  @c See the file elisp.texi for copying conditions.
  @setfilename ../info/tips
  @node Tips, GNU Emacs Internals, GPL, Top
***************
*** 435,441 ****
  search functions can be used.
  
  @item
! Certain built-in functions are handled specially in byte-compiled code, 
  avoiding the need for an ordinary function call.  It is a good idea to
  use these functions rather than alternatives.  To see whether a function
  is handled specially by the compiler, examine its @code{byte-compile}
--- 435,441 ----
  search functions can be used.
  
  @item
! Certain built-in functions are handled specially in byte-compiled code,
  avoiding the need for an ordinary function call.  It is a good idea to
  use these functions rather than alternatives.  To see whether a function
  is handled specially by the compiler, examine its @code{byte-compile}
***************
*** 537,543 ****
  
  @item
  Do not start or end a documentation string with whitespace.
!  
  @item
  @strong{Do not} indent subsequent lines of a documentation string so
  that the text is lined up in the source code with the text of the first
--- 537,543 ----
  
  @item
  Do not start or end a documentation string with whitespace.
! 
  @item
  @strong{Do not} indent subsequent lines of a documentation string so
  that the text is lined up in the source code with the text of the first