XYplorer Beta Club

admin wrote:

Stefan wrote:I think, if an defined placeholder is not used while executing an alias
then the placeholder should be dropped instead used as output.

Code: Select all

        Resolved alias:
          ::echo 'Hello, Don! It's !';      

I don't agree for 2 reasons:
1) The placeholder might be not meant to be placeholder but part of the hard input. Not likely but possible.
2) It would be more work for me to remove unknown placeholders. Needs to scan the string for "<@[number]>".

myAlias=::run <@1> <@2> <@3> <@4> <@5> <@6>
CMD:     myTool.exe  <curitem> /para /para2
Result:   myTool.exe  C:\Temp\file.ext /para /para2  <@5> <@6>

admin wrote:

Stefan wrote:While playing around i have found an problem by using an dot with my "@send" alias (have tried several kind of quoting)

Try this, else the dot in "Dr. Don" is seen by copytext as concatenator:

Code: Select all

send=::copytext "File <curname> send at <date> to " . '<@1>';

send=::copytext "File " . quote("<curname>") . " send at <date> to " .  '<@1>';

Stefan wrote:OK, i was just wondering if one would define an alias like

Code: Select all

myAlias=::run <@1> <@2> <@3> <@4> <@5> <@6>
CMD:     myTool.exe  <curitem> /para /para2
Result:   myTool.exe  C:\Temp\file.ext /para /para2  <@5> <@6>

I can imaging that those "<" ">" signs could lead to unwanted results? (don't want to test this right now)

admin wrote:

Stefan wrote:OK, i was just wondering if one would define an alias like

Code: Select all

myAlias=::run <@1> <@2> <@3> <@4> <@5> <@6>
CMD:     myTool.exe  <curitem> /para /para2
Result:   myTool.exe  C:\Temp\file.ext /para /para2  <@5> <@6>

I can imaging that those "<" ">" signs could lead to unwanted results? (don't want to test this right now)

Yes, may be. Or even probably. Not 100% sure yet.

"<@1>" Like ('<'.'@1>')

TheQwerty wrote:As I said earlier I'm not opposed to XY stripping unused <@#> out, and really Don, I think you could make this easier by capping it to 9 placeholders - it's nice that it supports at least 1000 but it's a bit overkill. If the user needs more maybe they should consider splitting the input themselves.

TheQwerty wrote:Okay Don, these parametrized aliases are incredibly awesome!

However , I have one more, and hopefully last, request:

Code: Select all

<@#[OmittedValue]>

Thus, instead of XY removing unused placeholders this would replace them with the specified OmittedValue.

A small example that just maps the scripting command SelFilter to an alias @s. If I do not want the same defaults as SelFilter's omitted defaults then I need to test the placeholders and may end up with something like:

Code: Select all

@s=::SelFilter("<@1>","<@2>"?"<@2>":"f","<@3>"?"<@3>":"Name","<@4>"?"<@4>":"0");

but with this proposal that could be reduced to:

Code: Select all

@s=::SelFilter("<@1>","<@2 f>", "<@3 Name>", "<@4 0>");

which I think we can all agree is a huge improvement in legibility.

@s=::SelFilter("<@1 <@2>>","<@2 <@1>>");

admin wrote:Yup, makes sense. But the parsing then becomes difficult if not a can of worms. Needs a little thinking...

Imagine you do evil things like this:

Code: Select all

@s=::SelFilter("<@1 <@2>>","<@2 <@1>>");

::echo("<get Tree <curpath><crlf>>");

"One","<@2 One>"

"One","One"

@test=::Echo("<@0><@1><@2>");

admin wrote:k I sorted it out. Check out next beta...

TheQwerty wrote:

admin wrote:k I sorted it out. Check out next beta...

Looks good to me; this just got awesome!