Re: Terminology in multi-tty primitives

[Chetan Pandya]

--- On Sun, 1/4/09, Jason Rumney <address@hidden> wrote:

> That is distinct from creating a frame on a different tty. The issue 
> here is that creating a frame on a tty that Emacs does not already own 
> can lead to corruption, because the process that owns that tty keeps 
> drawing to it while Emacs is using it.
> 
> Perhaps we should limit the ttys that Emacs will create frames on with 
> make-frame-on-tty to ttys that Emacs already owns (either through 
> emacsclient, or the tty that emacs -nw was started in). It is true that 
> we don't limit displays in the same way, but X displays are designed to 
> have multiple applications using them at a time, so we don't have the 
> same problem there.

I don't see how the situation needs to be different for emacsclient. If 
emacsclient is waiting, so can the other process be. Isn't it the user's 
responsibility to make sure of that?