diff options
author | Michael Albinus <michael.albinus@gmx.de> | 2018-08-27 12:51:44 +0200 |
---|---|---|
committer | Michael Albinus <michael.albinus@gmx.de> | 2018-08-27 12:51:44 +0200 |
commit | c61fbc529343194923ca11dfe10e9afb8b2546d3 (patch) | |
tree | 02ccba7f8c7917a8413d3e5e0a5928ba6a572d0f /doc | |
parent | e1370c36cef12e4ffdf4519a2eec6bb5b7727883 (diff) | |
parent | 1afd313334c93cb5b0a7a378bd635a54dc1d6a9e (diff) | |
download | emacs-c61fbc529343194923ca11dfe10e9afb8b2546d3.tar.gz emacs-c61fbc529343194923ca11dfe10e9afb8b2546d3.tar.bz2 emacs-c61fbc529343194923ca11dfe10e9afb8b2546d3.zip |
Merge branch 'master' of git.sv.gnu.org:/srv/git/emacs
Diffstat (limited to 'doc')
-rw-r--r-- | doc/emacs/trouble.texi | 10 | ||||
-rw-r--r-- | doc/misc/calc.texi | 13 |
2 files changed, 11 insertions, 12 deletions
diff --git a/doc/emacs/trouble.texi b/doc/emacs/trouble.texi index 37a73041676..bb05378f4c9 100644 --- a/doc/emacs/trouble.texi +++ b/doc/emacs/trouble.texi @@ -1162,11 +1162,11 @@ name that indicates whether it is the old version or your new changed one. @item -Write the change log entries for your changes. This is both to save us +Write the commit log entries for your changes. This is both to save us the extra work of writing them, and to help explain your changes so we can understand them. -The purpose of the change log is to show people where to find what was +The purpose of the commit log is to show people where to find what was changed. So you need to be specific about what functions you changed; in large functions, it's often helpful to indicate where within the function the change was. @@ -1177,9 +1177,9 @@ new function, all you need to say about it is that it is new. If you feel that the purpose needs explaining, it probably does---but put the explanation in comments in the code. It will be more useful there. -Please look at the change log entries of recent commits to see what -sorts of information to put in, and to learn the style that we use. Note that, -unlike some other projects, we do require change logs for +Please look at the commit log entries of recent commits to see what +sorts of information to put in, and to learn the style that we use. +Note that, unlike some other projects, we do require commit logs for documentation, i.e., Texinfo files. @xref{Change Log}, @ifset WWW_GNU_ORG diff --git a/doc/misc/calc.texi b/doc/misc/calc.texi index 98ef6daa2c1..02deee99e19 100644 --- a/doc/misc/calc.texi +++ b/doc/misc/calc.texi @@ -33275,19 +33275,18 @@ prefer them, or if you are calling these functions from regular Lisp. The functions described here are scattered throughout the various Calc component files. Note that @file{calc.el} includes @code{autoload}s -for only a few component files; when Calc wants to call an advanced -function it calls @samp{(calc-extensions)} first; this function -autoloads @file{calc-ext.el}, which in turn autoloads all the functions -in the remaining component files. +for only a few component files; to get autoloads of the more advanced +function, one needs to load @file{calc-ext.el}, which in turn +autoloads all the functions in the remaining component files. Because @code{defmath} itself uses the extensions, user-written code generally always executes with the extensions already loaded, so normally you can use any Calc function and be confident that it will be autoloaded for you when necessary. If you are doing something special, check carefully to make sure each function you are using is -from @file{calc.el} or its components, and call @samp{(calc-extensions)} -before using any function based in @file{calc-ext.el} if you can't -prove this file will already be loaded. +from @file{calc.el} or its components, and use @w{@code{(require +'calc-ext)}} before using any function based in @file{calc-ext.el} if +you can't prove this file will already be loaded. @menu * Data Type Formats:: |