An alias like @@key=`activate "..."` causes a new prompt to show ... use it several times and the console fills up with unused prompts. Is there a way to suppress the new prompt? If not, perhaps there will be in V12.
WAD, and there's no way to suppress it (nor will there be in v12).> An alias like @@key=`activate "..."` causes a new prompt to show ...
> use it several times and the console fills up with unused prompts. Is
> there a way to suppress the new prompt? If not, perhaps there will be
> in V12.
No new prompt, provided you pass 0 as the second arg to Command(). If you> What if a plugin keyhandler used Command(), during command line entry,
> to execute something like ACTIVATE ... would that cause a new prompt, or
> mess up the current command line?
If you'll forgive an ignorant newbie question: What's the advantage of using Command() instead of Activate_Cmd() ?What if a plugin keyhandler used Command(), during command line entry, to execute something like ACTIVATE ... would that cause a new prompt, or mess up the current command line?
I haven't tried it myself, but I imagine it wouldn't be difficult to do your own redirection via DuplicateHandle(). (Just be sure to save the original stderr handle, and put it back when you're done!)On Fri, 21 May 2010 22:55:35 -0400, Charles Dye <> wrote:
|If you'll forgive an ignorant newbie question: What's the advantage of using Command() instead of Activate_Cmd() ?
Now that I think of it (and having tried it) ... you can't put the "2> NUL" in
ACTIVATE's arguments. Rex, ACTIVATE could use a /q(uiet) option.
What good would that do? ACTIVATE doesn't display any text.> Rex, ACTIVATE could use a /q(uiet) option.
/Q never suppresses error messages -- I don't think it'd be a good idea to> |---Quote---
> |> Rex, ACTIVATE could use a /q(uiet) option.
> |---End Quote---
> |What good would that do? ACTIVATE doesn't display any text.
>
> I meant an option to suppress error messages.
No command has an option to suppress fatal errors (which are the only kinds> Do **any** commands have an option to suppress error messages? If so,
> that's what I had in mind for ACTIVATE.
I can't conceive of any case where suppressing fatal errors is a good idea.> I can conceive of situations when one wants to suppress this REAL
> error message (and others, such as the above failure to delete),
> currently supported only by redirecting STDERR to NUL.