This works for my purpose. Tnx !
Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se
> Am 07.02.2019 um 13:52 schrieb Michael Lueck :
>
> Greetings ooRexx'ers,
>
> Rick McGuire wrote:
>> The path in SysSearchPath() is the name of an environment variable, not a
>> string containing
Greetings ooRexx'ers,
Rick McGuire wrote:
The path in SysSearchPath() is the name of an environment variable, not a string containing the path. You could set an environment variable with that path and use SysSearchPath, but that's a bit silly
since you are just checking for the existence of a
On 07.02.2019 12:25, P.O. Jonsson wrote:
> Thanks for clarifying.
>
> Maybe you (or someone else) can help me with another issue: I am trying to
> locate the build
> directory on Mac in FileUtils.cls. On the jenkins slave the build is located
> in:
>
>
The path in SysSearchPath() is the name of an environment variable, not a
string containing the path. You could set an environment variable with that
path and use SysSearchPath, but that's a bit silly since you are just
checking for the existence of a single file in a specific location, not
Thanks for clarifying.
Maybe you (or someone else) can help me with another issue: I am trying to
locate the build directory on Mac in FileUtils.cls. On the jenkins slave the
build is located in:
/Users/jenkins/workspace/ooRexx-macOS1014-build/oorexxBuild
And in my clone installation:
Ok for MAC then but on Windows this does not occur, two backslashes are still
present in f.1. in my example. So at least SysFileTree works differently in
this aspect.
I can live with this, no problem, I just found it weird to have my input
„corrected“ rather than being told I did a mistake.
Before the search, the name gets canonicalized. Things like double slashes
and ".", and ".." directories get fixed up to get the fully resolved name
before processing the search.
Rick
On Thu, Feb 7, 2019 at 5:36 AM P.O. Jonsson wrote:
> The fact that is „works“ is not a proof of it being
Dear P.O
Having extra separators does not make a path invalid
Just try with playing around with ls
Just checked
ls opt/ooRexx/bin///rexx
ls opt/ooRexx/bin/
E
> On 7 Feb 2019, at 11:09, P.O. Jonsson wrote:
>
> Dear Developers,
>
> When working on modifying
Dear Developers,When working on modifying FileUtils.cls to work also for macOS/Darwin I used (by mistake, certainly) SysFileTree() with an invalid path and was astonished to see that it nevertheless produced a valid result. Is this intended?This is what I intended to do:installDir =
>
> REX0634E: Error 40.900: SysFileTree() argument 1 must be less than 255
> characters in length
I don't believe this restriction makes sense - please open a request for
enhancement (a bug report won't do, since we explicitly documented this
behavior)
Thanks!
Hello Erich thanks for checking. Here is the exact error message for both cases
(one at the time, the program breaks at this statement)
For dirs
*-* Compiled routine "SYSFILETREE".
7 *-* res = SysFileTree(SourceDir || slash || "*","dir","DO")
REX0040E: Error 40 running
>
> got the error message that the path was to long, and that it can only be
> 255 characters long on Unix
>
Hi P.O.
what's the exact error message?
what commands are you using to back "up downwards" (shell? Rexx?)
the maximum path length on Unix typically is not 255, rather much longer
"say
I have a related question that someone might have the answer to,
While backing up everything from the root directory downwards on the Mac I
quickly got the error message that the path was to long, and that it can only
be 255 characters long on Unix like systems (like the Mac). This is a serious
Dear all,
Please close this item, I can answer my own question now. Sorry for wasting
bandwidth.
While working on the Mac I realized that the system volume is not indeed a
volume but just a symbolic link to the root directory (/), hence the
explanation that SysFileTree() behaves differently
Dear Developers,In addition to what I wrote below I realized that the behavior is different depending on if the volume is a system volume (as in the case below) or another volume (separate disk or mounted volume on a NAS on the network). In the first case the behavior is as below, in the second
Dear Developers,
I wanted to move (a large number of) files between two volumes on the Mac but
stumbled on something I did not expect. Here a short example code
SourceDir = '/volumes/SSD/users/po/data/oorexxsvn'
--SourceDir = 'C:\Users\PO\Tracing‘ /* Win */
say 'SourceDir' SourceDir
16 matches
Mail list logo
