Re: Silencing noise

[T.V Raman]

Correct -- re a thread might be accessing multiple buffers / frames --
I was thinking more along the  lines of 

1. Messages displayed to the user should come from threads handling
the UI -- and roughly equated each thread of control to a user-visible
Frame (admittedly a very coarse granularity of threading but better
than the present)

and in that world,
2. Suggested that some app the user launches from a frame e.g. get
news, update packages etc should not cause UI changes such as
flickering messages in other frames where one i happily editting. 

Stephen J. Turnbull writes:
 > raman writes:
 > 
 >  > thinking forward to concutrrent/multi-threaded emacs, it would be
 >  > ideal if messages displayed from a thread running in a frame was
 >  > limited to that frame.
 > 
 > Does that actually make sense?  The point of threads is shared state,
 > a thread might very well be accessing multiple buffers/frames.
 > 
 >  > Food for thought: Should we in that world have a single *Messages*
 >  > buffer where all messages land up -- or a per-frame *Messages*
 >  > buffer with an additional Global-Messages buffer that shows up
 >  > everywhere -- that message queue could then be sued to display
 >  > truly urgent alerts etc.
 > 
 > That's an interesting idea.

-- 

--