Re: Documentation of 'output'

Robert Funnell <[email protected]> writes:

> I'll explain why I hadn't found that, in case there is someone else with the
> same affliction.

Thanks!  Yes, HyperDoc's behaviour is a little "unusual" given todays
standards.  Unfortunately, it seems that it's not really trivial to modify.
I'd still advise you to use it, since it is a great source of information.
Note that various flavours of axiom provide versions of HyperDoc to different
degrees of robustness.  Thus, if your HyperDoc crashes, ask again.

There is one other command I use frequently, namely, if I do not know at all
where I should be looking:

    )what things somethingiamlookingfor

or, shorther

    )wh th somethingiamlookingfor

(in the axiom console, that is)

It does a case-insensitive search for all operations / domains / packages /
categories for somethingiamlookingfor.  Thus, if I forgot how to spell the
binomial coefficient (LaTeX likes binom, mathematica Binomial, ...) I just ask

    )wh th bino

or so.

If you are interested in how things are actually programmed, maybe you like to
install 

http://wiki.axiom-developer.org/SPADEDIT

(click on "tangle" and save the result in

/axiom/target/i686-pc-linux/lib/SPADEDIT

(on some flavours of axiom, the path may look a little different, but I forgot
the details.  I think you'd have to replace target/i686-pc-linux with
mnt/linux)

Then you have to adapt it to your needs, i.e., replace

    gnuclient

with the name of your editor of choice.

($number contains the line-number to jump to.)

Finally make it executable.  Then, in HyperDoc

    click browse - enter INT - click constructors - click INT.spad

should open the source file at the right place.


Martin