Steve, many thanks for testing the script and commenting.

        [email protected]

wrote:

> I've tried it and it seems to have essentially worked as advertised.  I
> also ran the command to link xved with motif and xved changed to having
> a scrollbar, which I think indicates success.

Yes. It also acquires menu buttons.

There are some strange XVed behaviours e.g. some output.p files being
created mostly off screen, but I haven't tried investigating. That's not
new in this system.

> A minor point:  the
> INSTRUCTIONS.txt file says "The poplog_base directory includes a file
> named USEPOP".  However my directory doesn't have a USEPOP file, but
> rather a mk-USEPOP file, which, if sourced, creates the USEPOP file.

Ah a bit of the .csh version of the file that created and used the file
wasn't copied over. Fixed now.

> This seems an unnecessary layer of complication.  The INSTRUCTIONS.txt
> file says:
>
>      If you use sh or bash run this command IN THE poplog_base DIRECTORY:
>
>          export usepop=`cat USEPOP`

The point was intended to be that the USEPOP file could be copied anywhere
and then used in that way, but on reflection we can expect users to store
the path name of poplog_base. I'll get rid of it later, and change the
documentation that explains how to use the USEPOP file.

> In agreement with Waldek's remark yesterday, I think it would be a good
> idea to remove out of date news files from the docs.bz2 tarball.

I agree: I've rebuilt the docs tarball with older news files removed.

While making those changes I also increased the size of the parse tree
window in the rc_blocks demo so that all reasonable parses will be fully
visible. Calculating the required size for any given parse tree would be
nasty, and font dependent. I think that when the demo was first created
1280x1024 screens were commonplace. Now they are mostly bigger, except on
small laptops (like mine: 1366x768) but the parse tree window can be moved
to view different parts of a large parse tree.

Anyhow, I regard my current installation scripts as a stop-gap until we can
provide scripts that make it easy to download an up to date tarball from
the github site and the birmingham packages and documentation tar-balls
(which may need to acquire new contents in the near future), and combine
them.

At the moment I have an oppressive backlog of other work to deal with, so I
don't plan to do more on Poplog for a while, except test a new version from
github after we've been told how to fetch it.

Aaron

Reply via email to