/help, /theme and /add-dir now respond instantly; /config and /advisor do only if a remote flag turns on.
tengu_immediate_model_command On for this account, and not off by defaultThe flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.
This account: on · anonymous baseline: on · compiled default in v2.1.234: on
Read once, for one account on one subscription tier, against v2.1.234. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
Commands can now mark themselves as resolving immediately rather than on the next render pass. /help and /theme do so whenever the flicker-free alternate-screen renderer is active, /add-dir when it is active or when you passed an argument, and /config and /advisor when the tengu_immediate_model_command flag is on, which falls back to off.
- With an argument supplied,
/add-diris immediate regardless of the renderer. /configand/advisorfall back to the renderer-dependent behaviour when the flag is off.
tengu_immediate_model_command
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.221
In non-interactive runs, built-in help and feedback no longer reserve those command names
Both mention help slash command