While working on FDI, a while back I noticed something interesting. Either FreeCOM pipes or it’s set /p command (or both) are flakey. I think it is related to set /p.
I’ve worked around this issue in FDI. But, figured I would share what I have discovered. Take the following command: cd | set /p PWD= Sometimes it works, sometimes it doesn’t. A workaround would be: :TryAgain cd | set /p PWD= if “%PWD%” == “” goto TryAgain Why do I think it is set /p? When used at the tail of a pipe, if the set /p does not receive any input, FreeCOM will basically crash. So, it would appear that it receives the pipe and just fails to set the environment variable. A work around becomes more tricky when the pipe could return an empty string. But, like I have said. I have worked around this issue in FDI. Just thought I would share, Jerome ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
