Steve,
I've lost track of what has been going on becaues of other pressures
distracting me.
> I'm hoping that someone who understands X will take this up.
I think there have been fragments of information and it might help if you
provide a summary of what the problem was, what you've found, what you
think should be done about it and what you'd like people to do with the
attachments you've circulated.
In my case, if I have to work that sort of thing out I'll just leave it
till I'm under less pressure.
> I've done some preliminary poking around and so far haven't even found
> where xved processes its command line arguments.
I seem to recall that in the code for creating a new saved image there
needs to be a specification of what sort of command line processing happens
when the saved image is run.
So if you run pop11 (= basepop11 +startup{.psv})
the command line processing is different from what's available if you
run xved
= pop11 +xved.psv
= basepop +startup +xved
The mk... files for creating standard saved images are in the $popcom
directory =
$usepop/pop/com/
$usepop/pop/com/mk*
There are quite a lot of them, some concerned with creating startup files
for particular machines (e.g. sun workstation, tvi screens, v55 screens,
and possibly others).
Users can also do things in $poplib/init.p and $poplib/vedinit.p etc.
where $poplib is specified by the user, but defaults to part of the poplog
directory tree. I forget where!
There's probably documentation about this (even some written by me over 20
years ago) but I've forgotten where it is and what's in it.
I have to catch up with other things ... sorry.
Aaron
