Mercurial > emacs
changeset 71642:fa9d190c602e
(Coding Conventions): Cleanup last change.
| author | Richard M. Stallman <rms@gnu.org> |
|---|---|
| date | Wed, 05 Jul 2006 17:04:09 +0000 |
| parents | 6edfaf0b0ec6 |
| children | e712aec3ce09 |
| files | lispref/tips.texi |
| diffstat | 1 files changed, 7 insertions(+), 7 deletions(-) [+] |
line wrap: on
line diff
--- a/lispref/tips.texi Wed Jul 05 17:03:06 2006 +0000 +++ b/lispref/tips.texi Wed Jul 05 17:04:09 2006 +0000 @@ -177,9 +177,9 @@ Redefining (or advising) an Emacs primitive is a bad idea. It may do the right thing for a particular program, but there is no telling what other programs might break as a result. In any case, it is a problem -for debugging, because the two advised function doesn't do what its -source code says it does. If the programmer investigating the problem -is unaware that there is advice on the function, the experience can be +for debugging, because the advised function doesn't do what its source +code says it does. If the programmer investigating the problem is +unaware that there is advice on the function, the experience can be very frustrating. We hope to remove all the places in Emacs that advise primitives. @@ -192,10 +192,10 @@ @item Likewise, avoid using @code{eval-after-load} (@pxref{Hooks for Loading}) in libraries and packages. This feature is meant for -personal customizations; using it in a Lisp program is unclean because -it modifies the behavior of another Lisp file in an invisible way. -This is an obstacle for debugging, much like advising a function in -the other package. +personal customizations; using it in a Lisp program is unclean, +because it modifies the behavior of another Lisp file in a way that's +not visible in that file. This is an obstacle for debugging, much +like advising a function in the other package. @item If a file does replace any of the functions or library programs of