> 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.
> 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?
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?
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.
> |> 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.
> Do **any** commands have an option to suppress error messages? If so,
> that's what I had in mind for ACTIVATE.
> 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.
|Thread starter||Similar threads||Forum||Replies||Date|
|Expand all aliases on the command line||Support||2|
|S||Take Command crashes for aliases with length > 1015||Support||1|
|SETLOCAL removes Aliases and Functions||Support||3|
|V||Two @FUNCTIONs/aliases with the same name||Support||4|
|V||Append command line to @@key alias?||Support||13|