On Thu, Nov 26, 2020 at 11:10 PM Tomas Hajny via fpc-devel <fpc-devel@lists.freepascal.org> wrote:
> Typing 'break.exe' in cmd.exe _does_ make a difference here (it executes > as expected unlike when typing just 'break'). And obviously running > break.exe using some other 'shell' (e.g. your preferred OFM ;-) ) works > as well. Well, at my machine it did not. I also called it from a batchfile (as break.exe) to see if I could catch the errorlevel (I let it crash with a division by zero). The errorlevel is set, but absolutely no output to screen or pipe. -- Bart _______________________________________________ fpc-devel maillist - fpc-devel@lists.freepascal.org https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
