Need to extract batch of .lha archives into folders

[emufan]

every heard of lhasa?
current version on aminet, but a new version is in the making.

the nice feature of lhasa, it does create a configurable folder, where it does extract the archive:

$ lhasa.exe -ew=new_folder Anim2gif.lha
new_folder/Anim2gif.info        - Melted   :  o
new_folder/Anim2gif/An2gif      - Melted   :  o
...

so you may configure DOpus with the variable of the src-file-name as new destination folder.
maybe it's somehow usefull.

[idrougge]

I wonder if it would make sense to define .BRA and .KET as something else than < and >.

[Foebane]

Updated script:

.KEY SRC,DST
.DEF SRC "Downloads:"
.DEF DST "RetroStuff:"
LIST <SRC> PAT=#?.lha LFORMAT="LhA x *"%P%N*" *"<DST>%M/*"" >"RAM:Downloads.txt"
LIST <SRC> PAT=#?.lzx LFORMAT="LZX x *"%P%N*" *"<DST>%M/*"" >>"RAM:Downloads.txt"
LIST <SRC> PAT=#?.zip LFORMAT="UnZip *"%P%N*" -d *"<DST>%M*"" >>"RAM:Downloads.txt"
EXECUTE >NIL: "RAM:Downloads.txt"

[Foebane]

Originally Posted by jPV

Maybe because it has parenthesis in its name? They are special characters in AmigaDOS, so I would advice not to use them in file names no matter if it's the reason here or not. By using them you'll end up with trouble sooner or later anyway.. especially if handling such files from scripts.


Here's what Amiga manuals tell:

Colons ( and slashes (/) are reserved and cannot be used in file or directory names. Semicolons (, asterisks (*), parentheses (()), question marks (?), back apostrophes (`), number or pund signs (#), square brackets ([]), angle brackets (<>), tildes (~), vertical bars (|), dollar signs ($), double quotation marks ("), and percent signs (%) are not reserved; however, we recommend that you do not use these characters in your file or directory names because they have special meaning in AmigaDOS.

This is rather late to the party, but are "at signs" (@) also on this list?

[DamienD]

I would avoid them in filenames Foebane...

[Foebane]

Originally Posted by DamienD

I would avoid them in filenames Foebane...

Gordon Bennett, what IS allowed, then? Looks like only alphanumeric and mixed case to me!

[jPV]

Originally Posted by Foebane

Gordon Bennett, what IS allowed, then? Looks like only alphanumeric and mixed case to me!

@ is fine on Amiga AFAIK, and there are many other characters besides the listed ones which do work too, but IMHO it's best to avoid any special characters and keep it simple You never know when you have to copy files to other systems and what could happen there. Keep it plain and don't even use spaces and you're on safer side

[idrougge]

Anything but ~ # " ? or any kind of parentheses/brackets is fine.

[meynaf]

You can use every possible character except ":" and "/".
Some others can cause problems under special circumstances, such as command-line parsing, pattern-matching, or for use on pc filesystems.

If you really really really want to be safe, use only caps and 8.3

[Foebane]

I just ran my usual script (the subject of this thread) on a whole bunch of files with @ in the filenames and I had no problems, and I've read that if there were going to be problems, they would've occurred during this process. But none, so it's fine.

[Foebane]

Script update:

.KEY SRC,DST,TXT
.DEF SRC "Downloads:"
.DEF DST "DemoZone:"
.DEF TXT "RAM:Downloads.txt"
LIST <SRC> PAT=#?.exe LFORMAT="COPY *"%P%N*" TO <DST>" ><TXT>
LIST <SRC> PAT=#?.lha LFORMAT="LhA x *"%P%N*" *"<DST>%M/*"" >><TXT>
LIST <SRC> PAT=#?.lzx LFORMAT="LZX x *"%P%N*" *"<DST>%M/*"" >><TXT>
LIST <SRC> PAT=#?.zip LFORMAT="UnZip *"%P%N*" -d *"<DST>%M*"" >><TXT>
EXECUTE >NIL: <TXT>

This time, single downloaded .exe files will also be copied.

[Foebane]

Latest update:

.KEY SRC,DST,TXT
.DEF SRC "Downloads:"
.DEF DST "DemoZone:"
.DEF TXT "RAM:Downloads.txt"
LIST <SRC> PAT="2 #?.exe" LFORMAT="COPY *"%P%N*" TO <DST>" ><TXT>
LIST <SRC> PAT="4 #?.exe" LFORMAT="COPY *"%P%N*" TO <DST>" >><TXT>
LIST <SRC> PAT="#?.lha" LFORMAT="LhA x *"%P%N*" *"<DST>%M/*"" >><TXT>
LIST <SRC> PAT="#?.lzx" LFORMAT="LZX x *"%P%N*" *"<DST>%M/*"" >><TXT>
LIST <SRC> PAT="#?.zip" LFORMAT="UnZip *"%P%N*" -d *"<DST>%M*"" >><TXT>
EXECUTE >NIL: <TXT>

[Foebane]

How can I use parameters instead of set keys like the above? The script is proving to be a bit inflexible at the moment, and I want to be able to set my own FROM and TO directories after the script name on the CLI.

How do I go about doing this, please?

[Hewitson]

What is the point of this script? Is it so hard to manually extract an archive from the CLI?

You seem to insist on making things so much more difficult for yourself than they need to be. I honestly don't get it.

[meynaf]

Originally Posted by Foebane

How can I use parameters instead of set keys like the above? The script is proving to be a bit inflexible at the moment, and I want to be able to set my own FROM and TO directories after the script name on the CLI.

How do I go about doing this, please?

Typing the script name on the CLI followed by parameters works with your script exactly like it is...
(If you don't want to have default values and have parameters being required, add /A after each parameter which doesn't have a .def entry.)

[Foebane]

Originally Posted by Hewitson

What is the point of this script? Is it so hard to manually extract an archive from the CLI?

It's to extract multiple archives, within folders with the archive names. I like occupying myself with such mini-projects. Bit late to complain about it, aren't you?

Originally Posted by meynaf

Typing the script name on the CLI followed by parameters works with your script exactly like it is...

Really? Wow, that's useful! But if I do wish to use parameters, are the quotes optional or required? Does it make any difference?

[meynaf]

Originally Posted by Foebane

Really? Wow, that's useful! But if I do wish to use parameters, are the quotes optional or required? Does it make any difference?

Which quotes ?
Do you mean command "param1" "param2" vs command param1 param2 for typing script name and parameters on the cli ?
If so, it's same as any other command, it does not matter unless there are spaces in parameters.

[jPV]

Originally Posted by Foebane

Really? Wow, that's useful! But if I do wish to use parameters, are the quotes optional or required? Does it make any difference?

Heh yeah, the whole point using .KEY is to ask parameters for the script, and .DEF is just used to have some default values if user doesn't happen to give any parameters.

If you wouldn't want an option to give parameters to the script, we wouldn't have used these .KEY and .DEF at all in the first place. We'd probably just used the SET command to set local variables.

You need quotation marks if parameters contain space characters, otherwise not needed.

So, this would work, for example, like these ways:

batchextractscript Downloads2: DemoZone2: RAM:Downloads2.txt

or giving parameter names

batchextractscript SRC=Downloads2: DST=DemoZone2: TXT=RAM:Downloads2.txt

and when giving parameter names, you can mix the order

batchextractscript TXT=RAM:Downloads2.txt SRC=Downloads2: DST=DemoZone2:

etc... and you can replace = character by space too

batchextractscript TXT RAM:Downloads2.txt SRC Downloads2: DST DemoZone2:

Amiga shell is flexible :)

Originally Posted by Hewitson

What is the point of this script? Is it so hard to manually extract an archive from the CLI?

Not an archive, but archives, maybe hundreds of them at once.

[Foebane]

I was at work when I posted earlier today, but when I came back I tried what Meynaf suggested and it worked perfectly! Thanks, Meynaf and jPV!

I actually thought that ".DEF" stood for "DEFINE" and not "DEFAULT", that was my error.