Re: [Axiom-developer] Re: Patch for SPADEDIT

[Gabriel Dos Reis]

Ralf Hemmecke <address@hidden> writes:

| > | > There is yet another issue: It seems that latex -source-specials puts
| > | > the absolute path of the original file into the dvi. I guess that at
| > | > least kdvi won't mind for forward search (i.e., when clicking on
| > | > INT.spad in HyperDoc the correct line will appear),
| > | | I don't quite understand. If you want to jump from INT.spad to
| > the
| > | corresponding line in the .dvi file then the line information should be
| > | in INT.spad. Note that INT.spad.pamphlet is the source.
| > My inclination would be: just fire up $EDITOR on the _installed_
| > source (or if $EDITOR is not set, fire up vi).
| 
| Well, as you know there is no generic way to tell $EDITOR to place the
| cursor in line N of file F. If you go the same way as kdvi or xdvi
| then the target editor has to be configured (in kdvi/xdvi) together
| with the command line options that treat the line number and the
| filename.

If you want to fire up kdvi, you have to test for it in configure.
Similarly for xdvi.  If you want to make it an absolute requirement,
you may upset people.  You can at configure time detect what tools
are available and generate the corresponding editor script.  

-- Gaby