in reply to Re^3: Restarting a Perl script on Windows 10
in thread Restarting a Perl script on Windows 10

If all three of those also produce persistent extra command windows... the only idea I have at this point is "get a better operating system" ... or maybe run your program on a better operating system (on another computer, possibly a VM) and an X server on Windows for display? It has been some years; the last time I did that I was using a MinGW (I think?) X11 build on Windows XP.

  • Comment on Re^4: Restarting a Perl script on Windows 10

Replies are listed 'Best First'.
Re^5: Restarting a Perl script on Windows 10
by Anonymous Monk on Sep 24, 2019 at 08:18 UTC
    More argument from ignorance. Why even bother?

      Explain how offering a suggestion to stop using Microsoft products after Microsoft changed the system's behavior out from under perl is an argument from ignorance.

      Or are you just a troll?

      Update: No more troll snacks for you.

        Explain how offering a suggestion to stop using Microsoft products after Microsoft changed the system's behavior out from under perl is an argument from ignorance.

        Explain how its anything other than trolling the OP?

        Oh noes, I dont know how to help the OP unlock a drawer, surely the answer is to change buildings, cause thats how you solve a locked drawer