Embedding command line parameters

[HarryR]

In an attempt to get rid of the ugly 7zip and find something else that can join .001 files, I am trying to use a little utility call FFSJ, which I found at http://www.jaist.ac.jp/~hoangle/filesj/

As part of trying to make a totally portable flashdrive, I am trying to get XYPlorer to use FFSJ in command-line mode when I double-click a file with the extension .001.

The FFSJ site gives the command-line example of :
FFSJ.exe "-Task=Join" "-Input=c:\test\SP\LargeFile.dat.001"

I've been trying to do this with XYPlorer's portable file associations or scripts, but I can't see a way to get XY to pass the name of the file I click on into the command. I've tried replacing c:\test\SP\LargeFile.dat.001 with %1, but XY isn't having it.

Can anyone suggest a way to do this ?

[serendipity]

Select your .001 file and try this:

Code: Select all

run """Path to FFSJ.exe"" -Task=Join -Input=""<curitem>""";

Edit: Oh, you asked for POM, in which case it would be this:

Code: Select all

"Join files" 001>::run """Path to FFSJ.exe"" -Task=Join -Input=""<curitem>""";

[HarryR]

Excellent, that's done it. Many thanks, serendipity.

[HarryR]

Whoops, one further question: it's working with the Portable File Association :

+001>::run "L:\Apps\Portable\FastFileSplitterJoiner\FFSJ.exe" "-Task=Join" "-Input=<curitem>"

but when I try to replace the L: with ?:, it can't handle it.

Is there any way to make this sort of script drive letter-neutral ?

[serendipity]

Whoops, one further question: it's working with the Portable File Association :

+001>::run "L:\Apps\Portable\FastFileSplitterJoiner\FFSJ.exe" "-Task=Join" "-Input=<curitem>"

but when I try to replace the L: with ?:, it can't handle it.

Is there any way to make this sort of script drive letter-neutral ?

Ok seems like run does not support ?:, maybe try openwith instead, like this:

Code: Select all

::openwith "?:\Apps\Portable\FastFileSplitterJoiner\FFSJ.exe" "-Task=Join" "-Input=<curitem>"

[admin]

Whoops, one further question: it's working with the Portable File Association :

+001>::run "L:\Apps\Portable\FastFileSplitterJoiner\FFSJ.exe" "-Task=Join" "-Input=<curitem>"

but when I try to replace the L: with ?:, it can't handle it.

Is there any way to make this sort of script drive letter-neutral ?

Ok seems like run does not support ?:, maybe try openwith instead, like this:

Code: Select all

::openwith "?:\Apps\Portable\FastFileSplitterJoiner\FFSJ.exe" "-Task=Join" "-Input=<curitem>"

It might be useful to add a function to scripting that resolves a portable or relative path. Not sure how to call it. Any ideas?

[HarryR]

Perfect - thanks again, serendipity.

[HarryR]

It might be useful to add a function to scripting that resolves a portable or relative path. Not sure how to call it. Any ideas?

I'm not quite clear what you mean. Would such a function do more than the "?:" we refer to above ?

[serendipity]

It might be useful to add a function to scripting that resolves a portable or relative path. Not sure how to call it. Any ideas?

I'm not quite clear what you mean. Would such a function do more than the "?:" we refer to above ?

He means a new command to resolve any ?: to actual path like c:.
@Don: may be Showpath? ResolvePath?

[TheQwerty]

It might be useful to add a function to scripting that resolves a portable or relative path. Not sure how to call it. Any ideas?

If you want one for each direction: abs2rel and rel2abs.
If you want one with a switch: ResolvePath.

Could also be useful if there were a command or xy-var to retrieve the drive letter based on the volume label or serial number.

[admin]

It might be useful to add a function to scripting that resolves a portable or relative path. Not sure how to call it. Any ideas?

I'm not quite clear what you mean. Would such a function do more than the "?:" we refer to above ?

You could do something like this (air code obviously, not sure about that FFSJ syntax):

Code: Select all

+001>::run resolvepath("?:\Apps\Portable\FastFileSplitterJoiner\FFSJ.exe") . " " . quote("-Task=Join") . " " . quote("-Input=<curitem>")

[Stefan]

It might be useful to add a function to scripting that resolves a portable or relative path.
Not sure how to call it. Any ideas?

And i think <xydrive> is missing from XYplorer Native Variables.

<xydrive> current drive letter XY runs from right now.

[admin]

It might be useful to add a function to scripting that resolves a portable or relative path.
Not sure how to call it. Any ideas?

And i think <xydrive> is missing from XYplorer Native Variables.

<xydrive> current drive letter XY runs from right now.

Yes, that would help in the OP's case. Will add it.

[RalphM]

And could <xydrive> then be usable in the TitleBarTemplate as well, please?

[admin]

And could <xydrive> then be usable in the TitleBarTemplate as well, please?

Why?

Actually I could make the make the titlebar fully XY-var aware. Would that be interesting?