(2) -> )abbr domain XYZ
domain must be followed by an alternating list of abbreviation(s)
and name(s). Issue )abbrev? for more information.
(2) -> )abbrev?
Your argument list is not valid.
fricas
(1) -> )abbr domain XYZ
fricas
Compiling FriCAS source code from file
/var/lib/zope2.10/instance/axiom-wiki/var/LatexWiki/1207635563524016205-25px.001.spad
using old system compiler.
domain must be followed by an alternating list of abbreviation(s)
and name(s). Issue )abbrev ? for more information.fricas
)abbrev?
fricas
Compiling FriCAS source code from file
/var/lib/zope2.10/instance/axiom-wiki/var/LatexWiki/3012310849326617788-25px.002.spad
using old system compiler.
Your argument list is not valid.The error on the above is the missing space.
However, as shown below, )abbrev ? seems really not to have documentation, but )help ? had, and is not working in this version of Axiom.
fricas
)what commands
---------------- System Commands for User Level: compiler -----------------
abbreviations cd clear close
compile copyright credits display
edit frame help history
library load ltrace nopiles
piles pquit quit read
set show spool summary
synonym system trace undo
what version
For more information about individual commands, use the )help system
command followed by the command name or the command name followed
by a question mark. Some commands (such as )lisp ) may require
the )help lisp format. For example, issue )help help or )help ?
to find out more about the help command itself.
fricas
)help abbreviations
====================================================================
A.2. )abbreviation
====================================================================
User Level Required: compiler
Command Syntax:
- )abbreviation query [nameOrAbbrev]
- )abbreviation category abbrev fullname [)quiet]
- )abbreviation domain abbrev fullname [)quiet]
- )abbreviation package abbrev fullname [)quiet]
- )abbreviation remove nameOrAbbrev
Command Description:
This command is used to query, set and remove abbreviations for category,
domain and package constructors. Every constructor must have a unique
abbreviation. This abbreviation is part of the name of the subdirectory under
which the components of the compiled constructor are stored. Furthermore, by
issuing this command you let the system know what file to load automatically
if you use a new constructor. Abbreviations must start with a letter and then
be followed by up to seven letters or digits. Any letters appearing in the
abbreviation must be in uppercase.
When used with the query argument, this command may be used to list the name
associated with a particular abbreviation or the abbreviation for a
constructor. If no abbreviation or name is given, the names and corresponding
abbreviations for all constructors are listed.
The following shows the abbreviation for the constructor List:
fricas
)abbreviation query List
The following shows the constructor name corresponding to the abbreviation
NNI:
fricas
)abbreviation query NNI
The following lists all constructor names and their abbreviations.
fricas
)abbreviation query
To add an abbreviation for a constructor, use this command with category,
domain or package. The following add abbreviations to the system for a
category, domain and package, respectively:
fricas
)abbreviation domain SET Set
fricas
)abbreviation category COMPCAT ComplexCategory
fricas
)abbreviation package LIST2MAP ListToMap
If the )quiet option is used, no output is displayed from this command. You
would normally only define an abbreviation in a library source file. If this
command is issued for a constructor that has already been loaded, the
constructor will be reloaded next time it is referenced. In particular, you
can use this command to force the automatic reloading of constructors.
To remove an abbreviation, the remove argument is used. This is usually only
used to correct a previous command that set an abbreviation for a constructor
name. If, in fact, the abbreviation does exist, you are prompted for
confirmation of the removal request. Either of the following commands will
remove the abbreviation VECTOR2 and the constructor name VectorFunctions2
from the system:
fricas
)abbreviation remove VECTOR2
fricas
)abbreviation remove VectorFunctions2
Also See:
o )compile
fricas
)abbreviations ?
====================================================================
A.2. )abbreviation
====================================================================
User Level Required: compiler
Command Syntax:
- )abbreviation query [nameOrAbbrev]
- )abbreviation category abbrev fullname [)quiet]
- )abbreviation domain abbrev fullname [)quiet]
- )abbreviation package abbrev fullname [)quiet]
- )abbreviation remove nameOrAbbrev
Command Description:
This command is used to query, set and remove abbreviations for category,
domain and package constructors. Every constructor must have a unique
abbreviation. This abbreviation is part of the name of the subdirectory under
which the components of the compiled constructor are stored. Furthermore, by
issuing this command you let the system know what file to load automatically
if you use a new constructor. Abbreviations must start with a letter and then
be followed by up to seven letters or digits. Any letters appearing in the
abbreviation must be in uppercase.
When used with the query argument, this command may be used to list the name
associated with a particular abbreviation or the abbreviation for a
constructor. If no abbreviation or name is given, the names and corresponding
abbreviations for all constructors are listed.
The following shows the abbreviation for the constructor List:
fricas
)abbreviation query List
The following shows the constructor name corresponding to the abbreviation
NNI:
fricas
)abbreviation query NNI
The following lists all constructor names and their abbreviations.
fricas
)abbreviation query
To add an abbreviation for a constructor, use this command with category,
domain or package. The following add abbreviations to the system for a
category, domain and package, respectively:
fricas
)abbreviation domain SET Set
fricas
)abbreviation category COMPCAT ComplexCategory
fricas
)abbreviation package LIST2MAP ListToMap
If the )quiet option is used, no output is displayed from this command. You
would normally only define an abbreviation in a library source file. If this
command is issued for a constructor that has already been loaded, the
constructor will be reloaded next time it is referenced. In particular, you
can use this command to force the automatic reloading of constructors.
To remove an abbreviation, the remove argument is used. This is usually only
used to correct a previous command that set an abbreviation for a constructor
name. If, in fact, the abbreviation does exist, you are prompted for
confirmation of the removal request. Either of the following commands will
remove the abbreviation VECTOR2 and the constructor name VectorFunctions2
from the system:
fricas
)abbreviation remove VECTOR2
fricas
)abbreviation remove VectorFunctions2
Also See:
o )compile
fricas
)help help
====================================================================
A.12. )help
====================================================================
User Level Required: interpreter
Command Syntax:
- )help
- )help commandName
- )help syntax
Command Description:
This command displays help information about system commands. If you issue
fricas
)help help
then this very text will be shown. You can also give the name of a system
command to display information about it. For example,
fricas
)help clear
will display the description of the )clear system command.
The command
fricas
)help syntax
will give further information about the FriCAS language syntax.
All this material is available in the FriCAS User Guide and in HyperDoc. In
HyperDoc, choose the Commands item from the Reference menu.
====================================================================
A.1. Introduction
====================================================================
System commands are used to perform FriCAS environment management. Among the
commands are those that display what has been defined or computed, set up
multiple logical FriCAS environments (frames), clear definitions, read files
of expressions and commands, show what functions are available, and terminate
FriCAS.
Some commands are restricted: the commands
fricas
)set userlevel interpreter
fricas
)set userlevel compiler
fricas
)set userlevel development
set the user-access level to the three possible choices. All commands are
available at development level and the fewest are available at interpreter
level. The default user-level is interpreter. In addition to the )set command
(discussed in description of command )set ) you can use the HyperDoc settings
facility to change the user-level. Click on [Settings] to immediately go to
the settings facility.
Each command listing begins with one or more syntax pattern descriptions plus
examples of related commands. The syntax descriptions are intended to be easy
to read and do not necessarily represent the most compact way of specifying
all possible arguments and options; the descriptions may occasionally be
redundant.
All system commands begin with a right parenthesis which should be in the
first available column of the input line (that is, immediately after the
input prompt, if any). System commands may be issued directly to FriCAS or be
included in .input files.
A system command argument is a word that directly follows the command name
and is not followed or preceded by a right parenthesis. A system command
option follows the system command and is directly preceded by a right
parenthesis. Options may have arguments: they directly follow the option.
This example may make it easier to remember what is an option and what is an
argument:
)syscmd arg1 arg2 )opt1 opt1arg1 opt1arg2 )opt2 opt2arg1 ...
In the system command descriptions, optional arguments and options are
enclosed in brackets (``['' and ``]''). If an argument or option name is in
italics, it is meant to be a variable and must have some actual value
substituted for it when the system command call is made. For example, the
syntax pattern description
fricas
)read fileName [)quietly]
would imply that you must provide an actual file name for fileName but need
not use the )quietly option. Thus
fricas
)read matrix.input
is a valid instance of the above pattern.
System command names and options may be abbreviated and may be in upper or
lower case. The case of actual arguments may be significant, depending on the
particular situation (such as in file names). System command names and
options may be abbreviated to the minimum number of starting letters so that
the name or option is unique. Thus
fricas
)s Integer
is not a valid abbreviation for the )set command, because both )set and )show
begin with the letter ``s''. Typically, two or three letters are sufficient
for disambiguating names. In our descriptions of the commands, we have used
no abbreviations for either command names or options.
In some syntax descriptions we use a vertical line ``|'' to indicate that you
must specify one of the listed choices. For example, in
fricas
)set output fortran on | off
only on and off are acceptable words for following boot. We also sometimes
use ``...'' to indicate that additional arguments or options of the listed
form are allowed. Finally, in the syntax descriptions we may also list the
syntax of related commands.
fricas
)help ?
====================================================================
A.12. )help
====================================================================
User Level Required: interpreter
Command Syntax:
- )help
- )help commandName
- )help syntax
Command Description:
This command displays help information about system commands. If you issue
fricas
)help help
then this very text will be shown. You can also give the name of a system
command to display information about it. For example,
fricas
)help clear
will display the description of the )clear system command.
The command
fricas
)help syntax
will give further information about the FriCAS language syntax.
All this material is available in the FriCAS User Guide and in HyperDoc. In
HyperDoc, choose the Commands item from the Reference menu.
====================================================================
A.1. Introduction
====================================================================
System commands are used to perform FriCAS environment management. Among the
commands are those that display what has been defined or computed, set up
multiple logical FriCAS environments (frames), clear definitions, read files
of expressions and commands, show what functions are available, and terminate
FriCAS.
Some commands are restricted: the commands
fricas
)set userlevel interpreter
fricas
)set userlevel compiler
fricas
)set userlevel development
set the user-access level to the three possible choices. All commands are
available at development level and the fewest are available at interpreter
level. The default user-level is interpreter. In addition to the )set command
(discussed in description of command )set ) you can use the HyperDoc settings
facility to change the user-level. Click on [Settings] to immediately go to
the settings facility.
Each command listing begins with one or more syntax pattern descriptions plus
examples of related commands. The syntax descriptions are intended to be easy
to read and do not necessarily represent the most compact way of specifying
all possible arguments and options; the descriptions may occasionally be
redundant.
All system commands begin with a right parenthesis which should be in the
first available column of the input line (that is, immediately after the
input prompt, if any). System commands may be issued directly to FriCAS or be
included in .input files.
A system command argument is a word that directly follows the command name
and is not followed or preceded by a right parenthesis. A system command
option follows the system command and is directly preceded by a right
parenthesis. Options may have arguments: they directly follow the option.
This example may make it easier to remember what is an option and what is an
argument:
)syscmd arg1 arg2 )opt1 opt1arg1 opt1arg2 )opt2 opt2arg1 ...
In the system command descriptions, optional arguments and options are
enclosed in brackets (``['' and ``]''). If an argument or option name is in
italics, it is meant to be a variable and must have some actual value
substituted for it when the system command call is made. For example, the
syntax pattern description
fricas
)read fileName [)quietly]
would imply that you must provide an actual file name for fileName but need
not use the )quietly option. Thus
fricas
)read matrix.input
is a valid instance of the above pattern.
System command names and options may be abbreviated and may be in upper or
lower case. The case of actual arguments may be significant, depending on the
particular situation (such as in file names). System command names and
options may be abbreviated to the minimum number of starting letters so that
the name or option is unique. Thus
fricas
)s Integer
is not a valid abbreviation for the )set command, because both )set and )show
begin with the letter ``s''. Typically, two or three letters are sufficient
for disambiguating names. In our descriptions of the commands, we have used
no abbreviations for either command names or options.
In some syntax descriptions we use a vertical line ``|'' to indicate that you
must specify one of the listed choices. For example, in
fricas
)set output fortran on | off
only on and off are acceptable words for following boot. We also sometimes
use ``...'' to indicate that additional arguments or options of the listed
form are allowed. Finally, in the syntax descriptions we may also list the
syntax of related commands.
Comparing this with the NAG version, )what commands, )help abbreviations, and )abbreviations ? behave the same, but )help help and )help ? both print out about three pages of information, including two Sections A.12. )help, and A.1. Introduction from the "on-line version of the book". So there probably wasn't any documentation on )abbreviations to begin with. But )help ? should have worked.
Status: open => fix proposed
this is due to missing help files. In Axiom, help files are installed now, in FriCAS they are used when installed, but must be installed manually.
Status: fix proposed => fixed somewhere
no patch available