How can I determine if the current path is a drive or a directory?

[EctoOne]

Is there any way to determine whether the current path is a directory or the root of a drive?

I need to set a path as a variable to set a target for copy operations.
I tried using CD but the end of output is different if it's a drive or a directory.
It is either

DRIVE: or DRIVE:DIRECTORY

And when I use something like this:

Set TARGET 'CD' 
Copy SOMEFILE to ${TARGET}NEWFILE

It works when the path is a drive but not when it's a directory. Then the new file ends up as

DRIVE:DIRECTORYNEWFILE

or whatever.
And I can't do ${TARGET}/NEWFILE because then it won't work when it's a drive.

To add more info, yes I need NEWFILE because I need to rename some files.
And I hope this would be possible to fix with just shell scripting. No additional software or arexx.

[malko]

Depending on your OS version, this can be an idea that need a bit of adaptation : https://eab.abime.net/showthread.php?t=108682 ?

[EctoOne]

Thanks, using INFO to determine what the current path is works. Don't know how safe this is, but I came up with this:

SET CWD `CD`
INFO >T:eoCWD ${CWD}
SEARCH >NIL: FROM T:eoCWD SEARCH Unit QUIET
IF WARN ; Directory
    SETENV eoTARGET "${CWD}/"
ELSE ; Drive
    SETENV eoTARGET "${CWD}"
ENDIF
DELETE >NIL: T:eoCWD

Whenever the current path is a directory, there is no output from INFO which means the string "Unit" can not be found in the temp file. This will add the / to the CD output.
Using "Unit" as search string might not be the best way, but since I'm not parsing any arguments, I couldn't use a more unique string. Unit is one of the strings that comes up in the output of INFO. And since there is no output if it's a directory, I don't think there will be any problem.

[malko]

[thomas]

[QUOTE=EctoOne;1566047]I
And when I use something like this:

Set TARGET 'CD' 
Copy SOMEFILE to ${TARGET}NEWFILE

You could do it like this:

assign target: ""
copy somefile to target:newfile
assign target:

The name target: could be made unique by adding the process number to it. But this only works if the script has arguments:

.key dummy
assign target<$$>: ""
copy somefile to target<$$>:newfile
assign target<$$>:

Edit: you probably only used the current directory for the example, but if the target is the current directory, you don't need to supply a target path at all you could just do

copy somefile newfile

[EctoOne]

Thanks thomas, I normally try to avoid making assigns but your solution is so simple that I might use it. Because it also makes it easier to access sub dirs or at least it's better to read.

[freakofnature]

A short version to check for directory or disk

cd >ram:test
search >nil: ram:test #?:[a-z,0-9] pattern
if warn
echo "is drive"
endif

have fun!

[thomas]

The first echo should probably be cd, shouldn't it?

[freakofnature]

It should!
Corrected, thanks Thomas!

[EctoOne]

Wow, I didn't know that the Amiga had the support for this type of pattern matching.

[EctoOne]

Found another solution using ECHO instead of parsing a file and thought it might be worth sharing it.

The short version would be this:

SET cwd "`CD`"
IF "`ECHO "${cwd}" LEN 1`" EQ ":"
  ECHO "is drive"
ENDIF

A longer version using RequestFile to set a target is this:

SET eoTARGET `REQUESTFILE SYS: TITLE "Select install drive" DRAWERSONLY`
IF NOT "`ECHO "${eoTARGET}" LEN 1`" EQ ":"
  SET eoTARGET "${eoTARGET}/"
ENDIF
ECHO "${eoTARGET}"

It basically adds a / at the end of the selected path if it's not the root of a drive. Which makes ${eoTARGET} a complete path and can be used for file operations no matter what the real destination is.

[freakofnature]

Nice try.

echo $var len 1 is unreliable on AOS3.0 to 3.9, as it fails on path names containing <space>, like "Ram Disk:". Returning string then is "m :", every last char taken from all parts.
It works on 3.2 as well as on older os with shell replacement like zshell, but not vinced.

Brackets are used to access parsed arguments. You can safely omit them on local vars.

[EctoOne]

Huh, didn't notice that because I have a line in my user-startup that relabels my ram disk to ram. Wouldn't it be possible to wrap it in additional quotes? I will look into that.

I know about the brackets but I'm so used to them from bash scripting, also don't you need them anyway if you want to directly add something? Like in my second example where I add the /:

SET eoTARGET "${eoTARGET}/"

At least on Linux this is required if I remember correctly because it wouldn't recognize the variable otherwise. Never really tried it without brackets for Amiga scripts.

Edit: I can't reproduce the behavior you described. It works fine on my regular installation and even when I run the script using just a Workbench 3.1 disk.