From: <Pau...@ho...> - 2001-02-08 05:32:10
|
On Thursday, February 8, 2001, at 12:12 AM, I wrote: > =20 > Found the problem, sort of. I was calling the place with all my report = programs=20 > .../Programs and the place for report program output .../Reports. = Although the=20 > environment variable LLDATABASES is recognized, LLPROGRAMS seems to be = somehow fixed=20 > to be .../Reports and all report program output appears in the same = directory. If I=20 > rename the place I keep report programs from .../Programs to = .../Reports and set the=20 > environment variable LLPROGRAMS to .../Reports then my report programs = are found.=20 > Setting LLREPORTS seems to have no effect.=20 > =20 > Please clarify. What is the intended behavior?=20 > =20 Pardon the oversight. I was running the program from my .../Reports = directory so the actual behavior was that report programs were being = found and the report outputs were being written only in the local = directory (which is why it only worked when set to .../Reports). Now it = seems that both LLPROGRAMS and LLREPORTS are ignored but LLDATABASES is = recognized regardless of the current working directory. Is this a known issue? --Paul |
From: John F. C. <JCHBN@CUVMB.CC.COLUMBIA.EDU> - 2001-02-08 06:23:42
|
Paul wrote: > seems that both LLPROGRAMS and LLREPORTS are ignored As of two weeks ago, the logic for LLPROGRAMS was working as designed. The environment variable LLPROGRAMS is parsed as a list of directories separated by colons, and LL searches each directory in turn (as well as the current directory) for report programs to run. It doesn't matter what the directories are called -- just whether or not they are in the list. I haven't verified that LLREPORTS is also working, but I assume it is. > but LLDATABASES is > recognized regardless of the current working directory. Not sure what you mean by "regardless" in this context. If you have two versions of a certain database, one in the current directory and one in a directory listed in LLDATABASES, LL will find the one via LLDATABASES. However, if you have only one version, and it's in the current directory, LL will still find it, even if "." isn't specified in LLDATABASES. In other words, there is *some* regard for the current directory. The documentation doesn't actually describe this latter feature, but, if you think about it, you realize that it *has* to be so, since the current directory is where LL will create a new database if it doesn't find an old one. (There is an as-yet-undocumented variable LLNEWDBDIR which, as of two weeks ago, was still not working as it ought, so I won't go into the added complexity that it entails.) John Chandler |
From: <Pau...@ho...> - 2001-02-08 15:10:36
|
On Thursday, February 8, 2001, at 02:13 AM, prapp wrote: > It was a bug in my lloptions code.=20 > I just fixed it (at least it seems I fixed the existing bug - =20 > what other bugs exist remain to be seen...)=20 > =20 > =20 > =20 The three main environment variables seem to work now (others not tested = yet). Thanks. |