re: Re: FreeCOM feature review: ALIAS

Hi, I think your answer basically means "already works".
I did not ask for aliases with spaces left of the =, do not worry about that.

> ALIAS /B go=locate %%1 /d+ /g /n

Ah, so you got special %%1 variables and so on :-).
Alas, the /B switch is not documented in ALIAS /? ...
This is probably related to not being implemented yet:
alias /b ohce=echo %%2 %%1
gives "invalid switch" >:->. However, your suggested syntax is a good idea!

BUT I would propose that all %n arguments with %n not explicitly described
in the alias to be automatically appended anyway:
ALIAS /B foo=bar %%2 /baz
would then be interpreted as:
ALIAS /B foo=bar %%2 /baz %%1 %%3 %%4 %%5 %%6 %%7 %%8 %%9
You are right saying that ALIAS and ALIAS /B differ fundamentally, but
I think BOTH should exist. The current no-/B version is quite useful as well.

Does FreeCOM have %3& and %# ???

If you have 4start and 4end scripts, I could put "call fdalias.bat" in them,
so I would not need an ".aliases" autoloader anymore. Maybe I misunderstand
your 4start/4end concept.




About inheritance: Normally, a FreeCOM instance is very likely to be
spawned from something else than FreeCOM (or be the global instance).
So you will have to explain how you solve the "FreeCOM forms an inpermeable
border in the PSP process tree" problem that my COUNT3 tool has troubles
with. Would be nice for me to know how to pass this border anyway! As said,
I have a batch file which calls a program which calls FreeCOM /c otherbatchfile
and otherbatchfile must be able to modify the environment of the first batch
file (or at least the program). But I never get further than the called
FreeCOM when following the PSP parent chain :-(.

Eric