The hyperdoc and )show commands associate the source file of a package with abbreviation xxx to xxx.spad. This is not correct and sometimes the xxx is not even close to the correct file name. Please note that one spad file may contain many domains and packages. So most clicks in hyperdoc on the source file results in file not found and it is a guessing game what the right file is.

An example is SOLVETRA package where the spad file is transsolve.spad; another is EF where the file is elemntry.spad. The NAG version is correct, so something in the OpenSource? version is responsible for the change.

Category: Axiom Compiler => building Axiom from source

The problem to which William is referring is caused by the way Tim has re-organized the original .spad source files into .spad.pamphlet files. The mapping is many-to- one where there used to be 1000+ .spad files there are now only 300+ .spad.pamphlet files. The new OpenSource? makefile extracts the individual *.spad files as intermediate files as needed by the rest of the build, but these are not the ones passed on to the mnt release directory. Instead the current makefile extracts the merged .spad.pamphlet files and calls them .spad files in the mnt directory, but these correspond to the 300+ .spad.pamphlet files not the 1000+ original .spad files. I agree that the fact that these appear with the suffix ".spad" is confusing because the names because these are not the original *.spad files.

I think one reason that Tim may have done that was to keep these source files in sync with the corresponding *.dvi documentation files - that is a good thing. But unfortunately it breaks Axiom's original method of referring to the appropriate source.

Perhaps the *.spad files extracted as intermediate files could just be copied into the mnt directory instead of the re-packaged versions. That would at least make Axim work the way it used to. But in the new system of code+documentation in pamphlet files really one is not supposed to be editing the *.spad files directly, rather it is the pamphlet file that is should to be changed - both code and associated documentation.

So I suppose really Axiom should be supplying the new *.spad.pamphlet file names. This might be a little difficult since currently Axiom itself does not understand the mapping of spad to pamphlet files. I think that something would have to be changed in the Axiom database files.

Regards, Bill Page.

The searches should allow use wild card character * also be case insensitive. This is not the case in the open source version (something broken?), making it very unusable. Should be a high priority to fix since it is close to impossible for newcomers to program in Axiom without a fully working hyperdoc. Why spent time discussing about new GUI when it is perhaps simpler to fix these?

Category: building Axiom from source => Axiom User Interface

Save the following as $AXIOM/lib/SPADEDIT and make it executable, and replace the call to emacs by your favorite text editor. In fact, maybe one should change the code to call the dvi file or at least the pamphlet:

  #! /bin/bash

  ## get the filename   
  f=$(basename $1 .spad)

  ## get the file and the line number. We can assume that grep produces only one
  ## answer, I guess.
  ## (replace $AXIOM/src/algebra/* by the directory containing pamphlets if you 
  ## prefer them)
  h=$(grep -n ")abb.* $f " $AXIOM/src/algebra/*)

  ## get the filename
  name=${h%%:*}

  ## get the number
  number1=${h#*:}
  number=${number1%:*}

  ## start emacs
  emacs +$number $name

Status: open => fix proposed

Thanks Martin. I think your approach to solving (or at least working around) this problem is very innovative. I definitely agree that it should be included in the Axiom distribution.

In the longer term I still think that we need a more integrated support for literate programming in Axiom, but as a stopgap I think this is great!

Here is a pamphlet for a fix that also works for #5.

SPADEDIT.pamphlet

Martin

I´m new to Axiom (Windows version), and I´ve also this problem with )edit filename.input. So what exactly should I do with this SPADEDIT.pamphlet file to solve this problem? A few postings up I read: "Save the following as $AXIOM/lib/SPADEDIT and make it executable". How can I make it executable?

Sorry for my stupid questions, but as I said I´m still a newbie in Axiom, and just want to try (and use) it like other CAS.

Franz.

Status: fix proposed => closed

Fixed by 20071206.01.tpd.patch by changes to daase.lisp.pamphlet

Status: closed => fix proposed