http://www.xs4all.nl/~apinkus/backups/
Adding a directory requires adding the directory name to various places also, in configure scripts etcerera.
CVS uses a diff-like scheme for merging differences: it looks at two text files, determines the different lines, and merges accordingly. It discovers the changes you made by looking at the version you checked out last and the version you have now, to discover which lines changed (it maintains an automatic version number for each file).
If the version of a file on your system and the version in the cvs repository has a line that has been changed by both you and some one else, the cvs repository will obviously not know what to do with that, and it will signal a 'collision' which you will have to solve by hand (don't worry, this rarely happens). More on that later.
In commands to be described in this document are in short:
To check out Yacas as anonymous user, type:
cvs -d:pserver:anonymous@cvs.yacas. sourceforge.net:/cvsroot/yacas login cvs -z3 -d:pserver:anonymous@cvs.yacas. sourceforge.net:/cvsroot/yacas co yacas |
To check out as a maintainer, type:
export CVS_RSH=ssh1 |
This will tell CVS to use ssh1 for communication. Then, in order to get yacas, type
cvs -d:ext:loginname@cvs.yacas.sourceforge. net:/cvsroot/yacas co yacas |
where loginname is your name on the sourceforge system. This then creates a directory yacas/ with the full most recent distribution. You need to enter your password there, but other than that, that's it!
Those lines typed above are long and intimidating, but it is also the last time you need to type them. From now on, if you want to do anything with cvs, just go into the yacas/ directory you just checked out, and type the cvs command without the -d... flag. This flag just tells cvs where to find the repository. But future cvs commands will know where to find them, which is why you don't need that flag.
cvs update -d |
on the command line in the yacas directory, and that should essentially download the latest version for you in that directory (just the changes). The -d option here states that you are also interested in new directories that were added to the repository. Oddly enough, cvs will only get you changed and added files, not added directories, by default.
A command
cvs -q update -d |
will print messages only about changed files.
cvs add [list of file names of ascii text files]
which adds ascii text files. If you added binary files (GIF images in the documentation directory, or something like that), you can add it with
cvs add -kb [list of file names of binary files]
In case files need to be removed, there are two options:
There seems to be no easy way to rename or move files; you would have to remove them at their old location and add them at a new location.
Now, when finished with that, you might want to 'commit' all changes with
cvs commit |
If the commit succeeds, an email is sent out to the maintainers, who can then scan the diff files for changes, to see if they agree with the changes, and perhaps fix mistakes made (if any).
If there is a collision, the commit fails (it will tell you so). In case of a collision, you need to invoke cvs update twice. The cvs update outputs a list of file names with a character in front of them. The important ones are the files with a 'C' before them. They have a collision. You can go into the file, and see the collision, which the cvs system conveniently marks as:
<<<<<< old version =========== new version >>>>>> |
You can edit the file by merging the two versions by hand. This happens very rarely, but it can happen. Use cvs commit afterwards to commit.
The commit and update commands can be performed in specific directories, and on specific files, if necessary, by stating them on the command line. Or you can go into a sub directory and do a cvs commit or cvs update there, if you are confident that is the only place that changed or whose changes you are interested in.
That is basically it, a quick crash course cvs. It is actually very convenient in that usually all that is needed is a cvs commit to fix small bugs. You type that in, and your version gets merged with the changes others made, and they get your changes, and you backed up your changes at the same time (all with that little command!).
You can find more information about cvs at http://cvsbook.red-bean.com/ .
The "source" form of all documentation is maintained in a special plain text format. The format is such that it is clearly readable without any processing and is easy to edit. To compile the documents, the system processes the plain text docs with a script to prepare Yacas-language files and then runs the Yacas scripts to produce the final documentation.
The source text must be formatted in a certain fashion to delimit sections, code examples, and so on, but the format is easy enough to enter in a plain text editor. Text is marked up mostly by TAB characters, spaces, and asterisks "*" at the beginning of a line. The script txt2yacasdoc.pl converts this markup into Yacas code.
There is also a utility book2txt that attempts to convert existing documentation in the Yacas format into the plain text form suitable for txt2yacasdoc.pl. After conversion, the plain text docs normally require further editing.
perl txt2yacasdoc.pl < file.txt \ > file.chapt |
In this example, file.txt contains some formatted plain text (source text) and the resulting file file.chapt will be produced in Yacas-language documentation format.
There is a single option for txt2yacasdoc:
perl txt2yacasdoc.pl -debug < file.txt \ > file.chapt |
Currently the following markup is implemented:
In> 1+2; Out> 3; |
It is necessary to separate sample code blocks from section or chapter headings when they follow them. The reason for this is that the script will assume that everything which is at least single-TAB indented (up to a separation between paragraphs) belongs to one sample code block. This makes it easier to enter multiply indented sample code: e.g. a double-TAB indentation inside a sample code block will not start a new section. For example:
While(x<0) [ x:=x+1; Write(x); ]; |
* Item * Another item |
* 0. First item * 0. Second item |
Note that item text continues until the next itemized line is given or until end of paragraph.
Nesting of enumerated or itemized environments is not yet supported.
<*http://host.net/file.html#anchor*> |
<*click here|somewebpage.html*> |
*INCLUDE ../essays/howto.chapt |
Note that the included document must be a Yacas-language file. (This will become the IncludeFile() call in the Yacas document -- an alias to Load().)
The additional elements all start with an asterisk "*" in the first position on a line, followed by an uppercase keyword. A typical reference manual subsection documenting a certain function may look like this in plain text:
*CMD PrintList --- print list with padding *STDLIB *CALL {PrintList}(list) {PrintList}(list, padding); *PARMS {list} -- a list to be printed {padding} -- (optional) a string *DESC Prints {list} and inserts the {padding} ... *E.G. In> PrintList({a,b,{c, d}}, " .. ") Out> " a .. b .. { c .. d}"; *SEE Write, WriteString |
Notes:
In a subsection there may be either one function documented or several at once: for example, it may make sense to document Sin, Cos and Tan together. In this case, all function names should be simply listed in the *CMD header, for example:
*CMD Sin, Cos, Tan --- Trigonometric ... |
In addition, there is a tag *INTRO to denote a "reference chapter introduction" corresponding to the ChapterIntro() function, *A which creates an HTML link to a manual section corresponding to AddBody(HtmlAnchor()...), *AA which creates AddAnchor(), and *HEAD which creates a small heading (Topical()). For instance,
*PARMS |
*HEAD Parameters: |
This markup should be sufficient for creating reference documentation in plaintext.
By using a command such as
book2txt.sh file.chapt |
12:51pm scriabin> book2txt.sh intro.book [editvi.ys] [gnuplot.ys] True; Out> True; Quitting... File 'intro.book.txt' was created. 12:51pm scriabin> |
In the above example, the shell commands in book2txt.sh executed the following Yacas commands,
Use("book2txt.ys"); ToFile("file.chapt.txt") Load("file.chapt"); |
Of course, it is possible that some features of Yacas documentation were not implemented in the script and in that case the resulting file must be edited by hand. But the purpose of the book2txt script is exactly this: to make a plain text source file to be edited and maintained.
Several files can be converted at once, for example:
book2txt.sh f1.chapt f2.chapt file3.book |
book2TeX.sh intro.book intro.book.tex |
latex intro.book.tex latex intro.book.tex dvips -o intro.book.ps intro.book dvi |
latex intro.book.tex pdflatex intro.book.tex |
The shell commands in book2txt.sh execute the following Yacas commands:
Use("book2TeX.ys"); ToFile("file.chapt.tex") Load("file.chapt"); |
Not all features of Yacas documentation are compatible with TeX typesetting. To prevent errors, documentation should avoid certain things. In general, it is a good idea to check the typeset appearance of documentation, since it helps detect errors.
For example, the symbols %, { }, < >, #, \, _ and & are special to TeX. They should not normally be used in plain text; it is okay to use them in "typerwriter" text or code samples -- but not in section or chapter heads, because it makes it difficult to export to TeX correctly. TeX commands may be entered but will not be correctly rendered in HTML online documentation. Sometimes fixed-font text will hang over the right edge; a workaround is to break the fixed-font text into shorter fragments or to rephrase the text.
Another concern is that code examples are typeset in a fixed-width font and may not fit into the width of the page and will be hanging over it. To avoid this, the code in the code examples should not be longer than about 44 characters.
The current implementation uses a "report" style which allows chapters, sections, subsections and includes an automatically generated table of contents. ( LaTeX is automatically run twice to produce the TOC when executing make texdocs.)
Some complicated mathematical expressions may not correctly render in TeX. This is because Yacas uses its internal function TeXForm() to transform Yacas expressions to TeX. Mathematical expressions are entered in the plain text documentation source using Yacas syntax, then transformed to a special non-evaluating call TeXMath() in the Yacas-language documentation, which formats into HTML using a Write() call or into TeX using a TeXForm() call, as necessary. Testing should be performed on documentation before releasing it.
The debug version has to be built independently from the 'normal' version of Yacas.
cd src/ make clean make -f makefile.debug |
Note the object files generated are not suited for the normal Yacas executable. To rebuild the normal version a make clean is required.
The file makefile.debug was written to compile under Linux, but should work on other platforms with little tweaks.
After the build the debug files can be found in the src/ directory.
To invoke the debugger, type
./yacasdebug --rootdir ../scripts/ |
The Yacas debugger assumes the current directory for scripts, so the --rootdir command line option is required.
Yacasdebug:
The libyacasdebug.a library is used by proteusdebugger, a graphical front-end for debugging which is in development still also.
Future versions will have the ability to step through code and to watch local and global variables while executing, modifying them on the fly.