On Wed, Feb 6, 2013 at 12:47 PM, Alan Gauld wrote:
> so "the DOS prompt" is both traditional and sufficiently specific making it
> the most easily understandable of the likely terms.
"DOS prompt" is a common idiom, but it bears mentioning now and then
that the OS is NT [1], not DOS. That's all; I
On 06/02/13 10:58, eryksun wrote:
and pedantic comment about the habit of saying "DOS prompt". The cmd
shell is a Win32 console application, unlike DOS command.com.
Yes, but the problem is that Windows now has so many command prompts
(cscript, cmd, power shell etc) that "the Windows prompt"
On Tue, Feb 5, 2013 at 6:44 PM, 3n2 Solutions <3n2soluti...@gmail.com> wrote:
>
> I want to automate the following manual process from DOS promp:
I agree with Peter's answer. I'd just like to add a generally useless
and pedantic comment about the habit of saying "DOS prompt". The cmd
shell is a Wi
3n2 Solutions wrote:
> Hello,
>
> I want to automate the following manual process from DOS promp:
>
> c:/scripts/perl>perl fix.pl base.gtx >base.txt
>
> Here is my python script:
>
> path="c:/scripts/perl/"
> subprocess.call(['perl','fix.pl','base.gtx >base.txt',path])
>
> I also tried this a
On 05/02/13 23:44, 3n2 Solutions wrote:
I want to automate the following manual process from DOS promp:
c:/scripts/perl>perl fix.pl base.gtx >base.txt
Use a DOS batch file, that's what they are there for.
If you are not doing any other processing Python is inefficient and
overkill for this
