FIXED: Terminal: executables are not always executed

Report issues, odd behaviors or submit a detailed bug report.
Post Reply
User avatar
pjj
Posts: 1936
Joined: 13 Oct 2009 13:48
Location: Kraków, Poland

FIXED: Terminal: executables are not always executed

Post by pjj »

1) When I write anything, that is not recognized as a name of an executable or batch script in the current directory, I get this message:
Executable or batch file
Command prompt is lost.

2) When I try to execute a real executable, but not in the current directory, I get the same response. Command prompt is lost.

3) I need to go to the directory and only then I can execute my executable -- the last part of the animation below (gray rectangle) shows a part of its screen; btw this executable is RIOT, Radical Image Optimization Tool, superb freeware program (once plugin to IrfanView), the best one I know for manual control over the PNG/JPG/GIF optimization process (only static files).
terminal-executables.gif
terminal-executables.gif (168.59 KiB) Viewed 935 times
Alium tibi quaere fratrem; hic, quem tuum putas, meus est. Titus Flāvius Caesar Vespasiānus Augustus

User avatar
Rickard Johansson
Site Admin
Posts: 6168
Joined: 19 Jul 2006 14:29

Re: Terminal: executables are not always executed

Post by Rickard Johansson »

Fixed in next release (v5.20). Thanks!

Post Reply