|Keep It Simple, Stupid|
The examples you link to instruct you to open a command prompt, you have [executed] this in a power shell session, not a command prompt.
I repeated and found the command prompt that opened as admin. The commands accepted the syntax, but it did not seem to change the behavior of windows when a .pl file was thereafter double-clicked on. In settings, I changed the default app to open to be notepad++, which is probably the best outcome anyways. They don't want to let you open files with programs that you have rolled yourself but that it fit into the app world. I felt very uncomfortable in both the power shell and the admin shell. If it's not a one and done, then I don't want to do it again.I find it simpler, more productive and more portable just to open up a a command prompt and run the programs from there, after the initial setup.
Indeed, what I *really, really* miss is the ability in ubuntu to right click and "open terminal here." Right now, I *can* get a terminal to open on right-click, but it's the bash terminal from Git, and it's a whole different animal than a dos terminal. I really feel like I crawl around with dos. It's one of the reasons that I find myself always returning to 'nix systems. I heard about a Raspberry Pi at a social event this weekend and can't wait to get one.
I would like to thank everyone for taking the time to address these implementation-specific issues. Speaking only for me, I wouldn't understand anything about contemporary Windows without perl. Here is my latest startup script,
This is probably good enough for now.
In reply to Re^4: [implementation specific to windows] writing a proper batch file for terminal start-up