detach /Q is more yappy than advertised

[LarryBrasfield]

> ver /r

TCC 26.01.35 x64 Windows 10 [Version 10.0.18363.720]
TCC Build 35 Windows 10 Build 18363

> fosvr sqlite-doc-v31r1.wdf
The process ID is 15172

> alias fosvr
detach /Q C:\bin\fossil.exe server %$ > nul &

From the DETACH help:

/Q	Don't display the new process's ID.

The /Q options are nice, when one prefers the "silence is golden" way. This is a bug.

 

[rconn]

WAD. You've got a problem with your syntax - either use DETACH, or the trailing &, not both.

 

[LarryBrasfield]

Thanks. I would never have guessed that yappiness could depend on depend upon stream connections.

 

[rconn]

With the trailing &, your command was converted to:

detach detach /Q C:\bin\fossil.exe server %$ > nul

The first "detach" didn't have a /Q, so it displayed a PID. The second "detach" *did* have a /Q, so it didn't - but you wouldn't have seen it anyway because it was already running in a detached session.