| 1. |
Solve : The handle could not be duplicated during redirection of handle 1? |
|
Answer» So i'm trying to WRITE a batch file that will write "0| | |#start" into a file called &%plist%.list where %plist% is a previous input. Why do you want to use an ampersand for the beginning of the file name? Indeed. The ampersand is not called a "poison character" for nothing. Filenames with an ampersand (or a caret) are parsed OK when typed from the command prompt but if you try to drag-and-drop such files they need at least one space, otherwise you will find out about a long-standing bug in Windows drag and drop functionality. If a file path contains at least one space, then Windows automatically encloses the path in quotes so that it gets parsed properly. Windows should do the same thing if the file path contains & or ^, but it does not. This is true up to and including Windows 8. Also such filenames make batch processing more COMPLICATED and are usually avoided by experienced batch script writers. I was using it for a sorting mechanistic, instead of jumping in and out of folders all the time, but any character past $ on the number line will do. ($ are my batch files.) Btw: I didn't know about the & and the command line stuff, Thanks.Quote from: Lemonilla on October 14, 2012, 08:23:59 AM any character past $ on the number line will do. ($ are my batch files.) A lot of people use the underscore character _ |
|