- Jul
- 530
- 10
For the life of me.... I was trying to figure out how having my alises loaded was creating a failure with %@EXECSTR[-2,dirhistory] which returns the 2nd to last folders you were in.
It turns out that me aliasing tail to `call tail.bat` breaks EXECSTR's functionality
Is the implication here that EXECSTR is somehow using tail??
Or an internal tail command which needs an asterisk before it?
Or that we can't realias our tail command?
[History: I have compiled non-cygwin EXEs for lots of unix commands, as such, certain unix command are aliased to call a batfile which detects whether i have cygwin or not and uses the cygwin version if i have cygwin present, and an alternate version if i don't. I've used this for cat/du/fiff/head/uniq/tail/wget and sometimes grep since the 1990s]
Screenshot of me figuring out the problem:
It turns out that me aliasing tail to `call tail.bat` breaks EXECSTR's functionality
Is the implication here that EXECSTR is somehow using tail??
Or an internal tail command which needs an asterisk before it?
Or that we can't realias our tail command?
[History: I have compiled non-cygwin EXEs for lots of unix commands, as such, certain unix command are aliased to call a batfile which detects whether i have cygwin or not and uses the cygwin version if i have cygwin present, and an alternate version if i don't. I've used this for cat/du/fiff/head/uniq/tail/wget and sometimes grep since the 1990s]
Screenshot of me figuring out the problem:
Attachments
Last edited: