irb (the interactive ruby command line) freezes and is unusable from within PowerCmd.
Try the following steps to reproduce 1) install ruby (irb comes with ruby) 2) from the command prompt type irb <enter> 3) now the commandline starts irb and looks ready: irb(main):001:0> but it's not possible to input anything at the command prompt. The prompt is completely dead, even though the little caret blinks but does not respond to anything. There is no response, regardless if I type or not.
Compare this to an ordinary dos prompt where you can input things like "2+2" etc...
I really hope you can reproduce this. I had the problem on two laptops (one Dell and one Lenovo, both with similar software)
> irb (the interactive ruby command line) freezes and is unusable from > within PowerCmd.
> Try the following steps to reproduce > 1) install ruby (irb comes with ruby) > 2) from the command prompt type irb <enter> > 3) now the commandline starts irb and looks ready: > irb(main):001:0> > but it's not possible to input anything at the command prompt. The > prompt is completely dead, even though the little caret blinks but > does not respond to anything. There is no response, regardless if I > type or not.
> Compare this to an ordinary dos prompt where you can input things like > "2+2" etc...
> I really hope you can reproduce this. I had the problem on two laptops > (one Dell and one Lenovo, both with similar software)
On Jun 5, 3:26 pm, "Paul C." <power...@gmail.com> wrote:
> Yes. I can reproduce this defect. The defect is related to the core of > PowerCmd. It's not easy to fix. But I'll try.
Sounds good, Paul. I could probably also find other programs that cause the same bug. So I hope you can fix it so that nobody will suffer from not having to use PowerCmd.
> On Jun 5, 3:26 pm, "Paul C." <power...@gmail.com> wrote:
> > Yes. I can reproduce this defect. The defect is related to the core of > > PowerCmd. It's not easy to fix. But I'll try.
> Sounds good, Paul. I could probably also find other programs that > cause the same bug. So I hope you can fix it so that nobody will > suffer from not having to use PowerCmd.