Clarify a cospawn pause section

[jjhursey]

No description provided.

[jjhursey]

WIP label because I want to show someone the diff before opening it for general review.

[rhc54]

Still feels a little awkward, doesn't it? What I think we want to say is that any attributes to pause the job will only be applied to the apps that are not flagged as "debugger", yes? I see no reason why we wouldn't allow the launcher to pause the application procs, do you?

[jjhursey]

The prior sentence was a bit confusing as it could be read to imply that if you colaunch then you cannot pause the application which I don't think is what we wanted.

Note that this method for starting the debugger precludes the use of \ac{PMIx} attributes to \emph{pause} the application prior to attaching the debugger.

I think you are correct that a better wording here might be more along the lines of:

Note that \ac{PMIx} job \emph{pause} attributes (e.g., \refattr{PMIX_DEBUG_STOP_IN_INIT}) do not apply to applications where the \refattr{PMIX_DEBUGGER_DAEMONS} attribute set to true.

[rhc54]

Agreed - that sounds much more accurate. Original version was poorly written by me. ☹️

[jjhursey]

I pushed the updated language. I think this is ready for review now.

[jjhursey]

PR has now been updated to clarify both the co-launch and co-spawn cases regarding the pausing of the application.

[rhc54]

That got it - thanks!