Re: piping / redirecting into a vbs script ?
Frank Slootweg <[email protected]>
| Newsgroups | alt.comp.os.windows-xp,alt.windows7.general |
|---|---|
| Organization | NOYB |
| Message-ID | <[email protected]> |
R.Wieser <[email protected]> wrote: > Frank, > > >> > My guess was/is that the 'command interpreter' (Rudy doesn't say > >> > how he invokes his commands) > >> > >> I didn't ? > >> > >> [quote first post] > >> I tried to redirect some commandline output into a vbscript > >> [/quote] > >> > >> Besides that, the "echo hello | ..." and "... < data.txt" should have > >> been dead give-aways. > > > > As you didn't specifically say you invoked from cmd.exe, I said > > 'command interpreter', i.e. the general term. That's all. > > (I quoted everything. Otherwise you will just complain I snipped important > stuff) > > Really ? > > You said : "Rudy doesn't say how he invokes his commands". > > And I responded with quoting from my first post. So yes, I did say it. > There was nothing to guess at. Sigh! Not that, despite your aggressive, confrontational, insulting communication style, you still deserve a response, but saying "commandline" is not unambiguous. You may think it is, but it isn't. That why I said what I said. Like I said "... That's all.". Time to get over it. [More of the same communication 'style' deleted. There's just no point.]