Re^2: path for perl

 Main question is still answered. When "path=C:\perl\bin" is already s
+et in the environment variable, why do I get such an error. Why do I 
+need to set other path as asked in the post

Here is the error I get
C:\perlfiles>perldoc perldoc
Can't spawn "cmd.exe": No such file or directory at C:/Perl/lib/Pod/Pe
+rldoc.pm l
ine 1515.
Can't spawn "cmd.exe": No such file or directory at C:/Perl/lib/Pod/Pe
+rldoc.pm l
ine 1515.
Can't spawn "cmd.exe": No such file or directory at C:/Perl/lib/Pod/Pe
+rldoc.pm l
ine 1515.
[download]

Comment on Re^2: path for perl Download Code

Replies are listed 'Best First'.
Re^3: path for perl by Lawliet (Curate) on Feb 20, 2009 at 01:37 UTC
Just an Off Topic note about readability: `<p></p>` are for paragraphs (text), `<c></c>` tags are for code/error reporting. When you surround your whole node in `<c></c>` tags the paragraph portions become harder to read. And you didn't even know bears could type.	[reply] [d/l] [select]
Re^3: path for perl by jethro (Monsignor) on Feb 20, 2009 at 02:31 UTC
You get that error because the perldoc script uses the 'more' command of the DOS command line shell (cmd.exe) to show you the perldoc. So cmd.exe has to be in the PATH too as well as any other program perldoc might need. I don't know much about perl or shells on windows, but you might check if PATH (or path) already has a nice collection of paths before you overwrite it with 'path=...', so you might check that and just add the perl path to it instead of overwriting	[reply]
Re^3: path for perl by ikegami (Patriarch) on Feb 20, 2009 at 06:33 UTC
Something's very wrong if `cmd.exe` isn't in the `PATH`. It should be in `%windir%\system32`. Either the `PATH` in effect isn't what you think it is, or your Windows install is broken.	[reply] [d/l] [select]
Re^3: path for perl by Bloodnok (Vicar) on Feb 20, 2009 at 01:18 UTC
Try using the file search in Windoze Explorer (or as I know it, Exploder:-) to search for `cmd.exe` - having found it, add the directory in which it's located to the path - probably somewhere near the front. .oO(It [`cmd.exe`] might even 'live' in `%windir%\system`...) A user level that continues to overstate my experience :-))	[reply] [d/l] [select]