diff options
| author | Paul Eggert <eggert@twinsun.com> | 2002-08-16 06:29:40 +0000 |
|---|---|---|
| committer | Paul Eggert <eggert@twinsun.com> | 2002-08-16 06:29:40 +0000 |
| commit | 28665d46c3222733ba0e024f21d39be2d88087d4 (patch) | |
| tree | aa38cf4ccf348815dea5935b3cf31ab0cc6604c4 /man/idlwave.texi | |
| parent | a4581dd3c9fde04e873b07147fa2eac9cc0c81db (diff) | |
| download | emacs-28665d46c3222733ba0e024f21d39be2d88087d4.tar.gz | |
Minor spelling and grammar corrections.
Diffstat (limited to 'man/idlwave.texi')
| -rw-r--r-- | man/idlwave.texi | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/man/idlwave.texi b/man/idlwave.texi index 9e04d43b012..a087e3e0778 100644 --- a/man/idlwave.texi +++ b/man/idlwave.texi @@ -1084,7 +1084,7 @@ When you ask for routine information about an object method, and the method exists in several classes, IDLWAVE queries for the class of the object, unless the class is already known through a text property on the @samp{->} operator (@pxref{Object Method Completion and Class -Ambiguity}), or by having been explicity included in the call +Ambiguity}), or by having been explicitly included in the call (e.g. @code{a->myclass::Foo}). @cindex Calling sequences @@ -1594,7 +1594,7 @@ entire class inheritance chain. This is often referred to as @emph{chaining}, and is characterized by chained method calls like @w{@code{self->MySuperClass::SetProperty,_EXTRA=e}}. -IDLWAVE can accomodate this special synergy between class and keyword +IDLWAVE can accommodate this special synergy between class and keyword inheritance: if @code{_EXTRA} or @code{_REF_EXTRA} are detected among a method's keyword parameters, all keywords of superclass versions of the method being considered are included in completion. The completion @@ -2053,7 +2053,7 @@ expansion. @cindex Modification timestamp @cindex Header, for file documentation @cindex Timestamp, in doc header. -@cindex Changelog, in doc header. +@cindex ChangeLog, in doc header. @kindex C-c C-h @kindex C-c C-m @@ -2627,7 +2627,7 @@ execution is stopped in a buffer due to a triggered breakpoint or error, or while composing a long command in the IDLWAVE shell. In the latter case, the command is sent to the shell and its output is visible, but point remains unmoved in the command being composed --- you can inspect -the contituents of a command you're building without interrupting the +the constituents of a command you're building without interrupting the process of building it! You can even print arbitrary expressions from older input or output further up in the shell window --- any expression, variable, number, or function you see can be examined. |