Mercurial > emacs
comparison lispref/tips.texi @ 49600:23a1cea22d13
Trailing whitespace deleted.
author | Juanma Barranquero <lekktu@gmail.com> |
---|---|
date | Tue, 04 Feb 2003 14:56:31 +0000 |
parents | d49f5ed1a977 |
children | 10a8aba3dfc7 d7ddb3e565de |
comparison
equal
deleted
inserted
replaced
49599:5ade352e8d1c | 49600:23a1cea22d13 |
---|---|
1 @c -*-texinfo-*- | 1 @c -*-texinfo-*- |
2 @c This is part of the GNU Emacs Lisp Reference Manual. | 2 @c This is part of the GNU Emacs Lisp Reference Manual. |
3 @c Copyright (C) 1990, 1991, 1992, 1993, 1995, 1998, 1999 | 3 @c Copyright (C) 1990, 1991, 1992, 1993, 1995, 1998, 1999 |
4 @c Free Software Foundation, Inc. | 4 @c Free Software Foundation, Inc. |
5 @c See the file elisp.texi for copying conditions. | 5 @c See the file elisp.texi for copying conditions. |
6 @setfilename ../info/tips | 6 @setfilename ../info/tips |
7 @node Tips, GNU Emacs Internals, GPL, Top | 7 @node Tips, GNU Emacs Internals, GPL, Top |
8 @appendix Tips and Conventions | 8 @appendix Tips and Conventions |
9 @cindex tips | 9 @cindex tips |
433 @code{assq}, or @code{assoc} is even faster than explicit iteration. It | 433 @code{assq}, or @code{assoc} is even faster than explicit iteration. It |
434 can be worth rearranging a data structure so that one of these primitive | 434 can be worth rearranging a data structure so that one of these primitive |
435 search functions can be used. | 435 search functions can be used. |
436 | 436 |
437 @item | 437 @item |
438 Certain built-in functions are handled specially in byte-compiled code, | 438 Certain built-in functions are handled specially in byte-compiled code, |
439 avoiding the need for an ordinary function call. It is a good idea to | 439 avoiding the need for an ordinary function call. It is a good idea to |
440 use these functions rather than alternatives. To see whether a function | 440 use these functions rather than alternatives. To see whether a function |
441 is handled specially by the compiler, examine its @code{byte-compile} | 441 is handled specially by the compiler, examine its @code{byte-compile} |
442 property. If the property is non-@code{nil}, then the function is | 442 property. If the property is non-@code{nil}, then the function is |
443 handled specially. | 443 handled specially. |
535 In Dired, visit the file or directory named on this line. | 535 In Dired, visit the file or directory named on this line. |
536 @end example | 536 @end example |
537 | 537 |
538 @item | 538 @item |
539 Do not start or end a documentation string with whitespace. | 539 Do not start or end a documentation string with whitespace. |
540 | 540 |
541 @item | 541 @item |
542 @strong{Do not} indent subsequent lines of a documentation string so | 542 @strong{Do not} indent subsequent lines of a documentation string so |
543 that the text is lined up in the source code with the text of the first | 543 that the text is lined up in the source code with the text of the first |
544 line. This looks nice in the source code, but looks bizarre when users | 544 line. This looks nice in the source code, but looks bizarre when users |
545 view the documentation. Remember that the indentation before the | 545 view the documentation. Remember that the indentation before the |