bug#800: marked as done (multi-tty suspend confusion)

[Emacs bug Tracking System]

Your message dated Thu, 28 Aug 2008 17:19:02 -0400
with message-id <87r688aldl.fsf@cyd.mit.edu>
and subject line Re: multi-tty suspend confusion
has caused the Emacs bug report #800,
regarding multi-tty suspend confusion
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact don@donarmstrong.com
immediately.)


-- 
800: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=800
Emacs Bug Tracking System
Contact don@donarmstrong.com with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> multi-tty suspend confusion
>
>
>
>
> Date: 
>
> Wed, 27 Aug 2008 16:20:58 -0400
>
>
>
>
> User-agent: 
>
> Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/)
>
>
>
>
> Package: emacs
> Version: 23.0.60
>
> (Filing a report for an old issue from FOR-RELEASE.)
>
> http://lists.gnu.org/archive/html/emacs-devel/2007-12/msg00545.html
>
>
> >From xterm:
> ./src/emacs -Q -nw --eval "(server-start)"
>
> C-z works in the normal way to suspend Emacs.
>
> >From another xterm:
>
> ./lib-src/emacsclient -c README
>
> Now C-z in the "emacs -nw" frame reports:
>
> "Suspending an Emacs running under X makes no sense"
>
> It continues to do so even after the X frame is closed.
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: multi-tty suspend confusion
>
>
>
>
> Date: 
>
> Thu, 28 Aug 2008 17:19:02 -0400
>
>
>
>
> > ./src/emacs -Q -nw --eval "(server-start)"
> >
> > From another xterm:
> >
> > ./lib-src/emacsclient -c README
> >
> > Now C-z in the "emacs -nw" frame reports:
> >
> > "Suspending an Emacs running under X makes no sense"
> >
> > It continues to do so even after the X frame is closed.
>
> I've checked in a fix.
>
>
> --- End Message ---