Re: User interaction from multiple threads

[Richard Stallman]

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > My conclusion from the discussion is that when a thread asks for
  > input, it might be too late, because the prompt was already issued.

In Emacs, prompts are usually output by a function
whose main purpose is to ask for input.  Is this no longer true?
So in practice it is easy to tell what is a prompt that asks for input.

  > > until the thread exits?

  > Not until it exits, until it no longer needs to interact with the
  > user, for the current transaction (whatever that means).

How does a thread say that it no longer needs to interact...?

  > I'm saying that fixing the prompt itself is a better alternative,
  > because we will always give the prompt more screen estate than to the
  > thread ID.

Emacs could add the thread ID at the start of a prompt
when there are multiple threads that could be asking for input,
such that there is a possibility of confusion.

That could avoid lengthening the prompts in the usual cases.
 


-- 
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)