bug#772: 23.0.60; cannot open multiple TTY frames using emacsclient -t

bug#772: 23.0.60; cannot open multiple TTY frames using emacsclient -t

[Yoshiaki Kasahara]

Please write in English if possible, because the Emacs maintainers
usually do not have translators to read other languages for them.

Your bug report will be posted to the emacs-pretest-bug@gnu.org mailing list.

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:

I cannot open multiple TTY frames of an Emacs instance now.  I usually
open two Emacs frames inside a 'screen' session using emacsclient -t,
but it is not working now.

When I try to open the second frame in a different tty, the first
frame on the first tty shows *scratch* buffer.  Nothing happens on the
second tty.  When I kill the second emacsclient, the first client dies
together.

I'm not sure when the symptom (or functional change?) started to
occur, because I hadn't updated my source tree for about a month.

If Emacs crashed, and you have the Emacs process in the gdb debugger,
please include the output from the following gdb commands:
    `bt full' and `xbacktrace'.
If you would like to further debug the crash, please read the file
/usr/local/share/emacs/23.0.60/etc/DEBUG for instructions.


In GNU Emacs 23.0.60.2 (x86_64-unknown-freebsd7.0, GTK+ Version 2.12.11)
 of 2008-08-25 on elvenbow.cc.kyushu-u.ac.jp
Windowing system distributor `The X.Org Foundation', version 11.0.10402000
configured using `configure  '--without-xim''

Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: C
  value of $LANG: ja_JP.eucJP
  value of $XMODIFIERS: @im=uim
  locale-coding-system: japanese-iso-8bit-unix
  default-enable-multibyte-characters: t

Major mode: Summary

Minor modes in effect:
  show-paren-mode: t
  savehist-mode: t
  iswitchb-mode: t
  icomplete-mode: t
  desktop-save-mode: t
  display-time-mode: t
  shell-dirtrack-mode: t
  tooltip-mode: t
  mouse-wheel-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  global-auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  column-number-mode: t

bug#772: marked as done (23.0.60; cannot open multiple TTY frames using emacsclient -t)

[Emacs bug Tracking System]

[-- Attachment #1: Type: text/plain, Size: 881 bytes --]


Your message dated Tue, 26 Aug 2008 13:32:36 -0400
with message-id <87tzd7u1fv.fsf@cyd.mit.edu>
and subject line Re: 23.0.60; cannot open multiple TTY frames using emacsclient -t
has caused the Emacs bug report #772,
regarding 23.0.60; cannot open multiple TTY frames using emacsclient -t
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.)


-- 
772: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=772
Emacs Bug Tracking System
Contact don@donarmstrong.com with problems

[-- Attachment #2: Type: message/rfc822, Size: 4345 bytes --]

From: Yoshiaki Kasahara <kasahara@nc.kyushu-u.ac.jp>
To: emacs-pretest-bug@gnu.org
Subject: 23.0.60; cannot open multiple TTY frames using emacsclient -t
Date: Mon, 25 Aug 2008 22:14:25 +0900 (JST)
Message-ID: <20080825.221425.245900097114586641.kasahara@nc.kyushu-u.ac.jp>


Please write in English if possible, because the Emacs maintainers
usually do not have translators to read other languages for them.

Your bug report will be posted to the emacs-pretest-bug@gnu.org mailing list.

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:

I cannot open multiple TTY frames of an Emacs instance now.  I usually
open two Emacs frames inside a 'screen' session using emacsclient -t,
but it is not working now.

When I try to open the second frame in a different tty, the first
frame on the first tty shows *scratch* buffer.  Nothing happens on the
second tty.  When I kill the second emacsclient, the first client dies
together.

I'm not sure when the symptom (or functional change?) started to
occur, because I hadn't updated my source tree for about a month.

If Emacs crashed, and you have the Emacs process in the gdb debugger,
please include the output from the following gdb commands:
    `bt full' and `xbacktrace'.
If you would like to further debug the crash, please read the file
/usr/local/share/emacs/23.0.60/etc/DEBUG for instructions.


In GNU Emacs 23.0.60.2 (x86_64-unknown-freebsd7.0, GTK+ Version 2.12.11)
 of 2008-08-25 on elvenbow.cc.kyushu-u.ac.jp
Windowing system distributor `The X.Org Foundation', version 11.0.10402000
configured using `configure  '--without-xim''

Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: C
  value of $LANG: ja_JP.eucJP
  value of $XMODIFIERS: @im=uim
  locale-coding-system: japanese-iso-8bit-unix
  default-enable-multibyte-characters: t

Major mode: Summary

Minor modes in effect:
  show-paren-mode: t
  savehist-mode: t
  iswitchb-mode: t
  icomplete-mode: t
  desktop-save-mode: t
  display-time-mode: t
  shell-dirtrack-mode: t
  tooltip-mode: t
  mouse-wheel-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  global-auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  column-number-mode: t



[-- Attachment #3: Type: message/rfc822, Size: 1070 bytes --]

From: Chong Yidong <cyd@stupidchicken.com>
To: Yoshiaki Kasahara <kasahara@nc.kyushu-u.ac.jp>
Cc: 772-done@emacsbugs.donarmstrong.com
Subject: Re: 23.0.60; cannot open multiple TTY frames using emacsclient -t
Date: Tue, 26 Aug 2008 13:32:36 -0400
Message-ID: <87tzd7u1fv.fsf@cyd.mit.edu>

I believe this was due to a typo in Eli's 2008-08-23 checkin, which he
fixed on 2008-08-26.