Testing build #239

[rejetto]

download @www.dovedove.it/hfs/hfs239.exe (temporaly link without bug below) hfs.webhop.org/hfs239.exe

what's new
+ {.load|XXX|from=|to=|size=.}
+ in template and scripting "\p" is replaced by "|", being the latter a special symbol
+ new template macro: no pipe, filepath
- auto loading at start a VFS that was deleted, was erroneously warning of file corruption
- {.exec.} broken in build #232 [link]
- at [upload completed] time, the uploaded file was still locked [link]
- {.get|uri.} broken in build #238 [link]

[Mars]

There is a possible bug with lines in blue

    if pars.Count > 0 then
      begin
      p:=pars[pars.count-1];
      if ansiEndsText('/'+name, p) then
        begin
        setLength(p, length(p)-length(name)-1);
        pars[pars.count-1]:=p;
        end;
      end;

    for i:=0 to pars.count-1 do
      pars:=xtpl(pars, ['\p','|']);
    // handle aliases
    if assigned(md.aliases) then
      begin
      s:=md.aliases.values[name];
      if s > '' then
        begin
        call(MARKER_OPEN+s+MARKER_CLOSE, 0);
        exit;
        end;
      end;

I give just an example:

{.copy|c:\private folder\bug.txt| ....... .}

the first param is converted   'c:|rivate folder\bug.txt' ,   is it that you want?

the same problem can appear if you want to replace \t  or \n by their equivalent 

You have to use a macro to let the user make this choice

{.escape|text .}  {.unescape|....... .}

 Rejetto, please give us the build 240

[rejetto]

aw shit

this was to make it possible to use pipe characters.
i disabled automatic updates while i find a solution.
this is not just a bug, it must be redesigned. it will take time.

[bacter]

why not, instead of a 'strange' conversion-function (\p -> |), use a macro of type {.asc|nn.} ?

-> {.asc|124.} = |

[Mars]

why not, instead of a 'strange' conversion-function (\p -> |), use a macro of type {.asc|nn.} ?

-> {.asc|124.} = |

I have a solution which consists in putting the | between two %, as it: %|% ,as in variables, but which takes into account the fact that certain macro are quoted with {: :} and  do not to be modified

which  envisages rejetto is well beyond a simple setting-up of a character by using a macro or a variable.

have a look at:
http://www.rejetto.com/forum/index.php?topic=7012.0

[rejetto]

why not, instead of a 'strange' conversion-function (\p -> |), use a macro of type {.asc|nn.} ?
-> {.asc|124.} = |

this won't solve it because of the way the parser works.
it's a very simple parser.