"Arnd Hanses" <[EMAIL PROTECTED]> wrote:
> Those paths are absolutely fixed and must not be changed. (If you
> fiddle with them, X might even refuse to start up).
This statement is simply untrue. The only thing fixed in X is the
location of the host file for the server/clients connections.
Other X related things are set at the server start-up time and users
can easily change them. (xinitrc.cmd)
While LyX on OS/2, by default, considers the system directory is
$(X11ROOT)/XFree86/lib/X11/lyx/
which is *my* (not Holger Veit's) decision. UNIX applications have
tendency to hard code default directories
-DFOO_BAR_PATH=\"$(pkgdatadir)/foo/bar\"
into the binary and I thought
+ Even though the distinction between the system directory and the
user directory is meaningless on OS/2, maintaining the OS/2
specific routine for the path search is costly.
+ I can't assume users have /usr/local directory. Existing and
unique (which drive?) directory is better suited for the system
directory.
If you can propose a better scheme, I'm willing to adopt.
> this may be questionable). Moreover Rexx is sooo complicated ;-) and I
Procedural REXX is simple. The only rules are
1. A sentence is either an asignment (A=B) or a command
2. If a command is not interpretable, then it will be passed to the shell
3. Everything not quoted will be expanded
4. An end of line is always an end of sentence
1. and 2. is exactly the same as shell script. Only difference is that
UNIX shells in general have very limited fixed sets of internal commands
like cd, for, do, etc. While REXX interpreter have quite a few built-in
commands and have a command to load further commands from dynamic libraries.
As for 3., a shell only expands $whatever
4. is a severe limitation and have to be worked around even if variables
in REXX can contain newline character or even full binary data.
Regards,
SMiyata
