From: Eli Zaretskii <eliz@gnu.org>
To: eggert@cs.ucla.edu
Cc: hyperair@debian.org, 15282@debbugs.gnu.org
Subject: bug#15282: 24.3.50; Starting a new emacsclient -t instance with another instance running in a separate terminal causes display corruption in the first instance.
Date: Wed, 11 Sep 2013 07:00:22 +0300 [thread overview]
Message-ID: <8361u8j9d5.fsf@gnu.org> (raw)
In-Reply-To: <83d2ommf12.fsf@gnu.org>
Ping!
Paul, could you please take a look?
> Date: Fri, 06 Sep 2013 13:16:09 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 15282@debbugs.gnu.org
>
> > Date: Fri, 6 Sep 2013 09:46:17 +0800
> > From: Chow Loong Jin <hyperair@debian.org>
> >
> > 1. Start the daemon: emacs -Q --daemon
> > 2. Start emacsclient: emacsclient -t
> > 3. Open a new terminal, and start another emacsclient instance:
> > emacsclient -t
> > 4. Go back to the first emacsclient instance, and notice that there's
> > some text corruption that can't be cleared without closing that
> > emacsclient instance. ^Z followed by fg doesn't get rid of the issue
> > either.
>
> The reason seems to be this commit:
>
> revno: 114012
> author: Paul Eggert <eggert@cs.ucla.edu>
> committer: Paul Eggert <eggert@cs.ucla.edu>
> branch nick: trunk
> timestamp: Mon 2013-08-26 18:10:30 +0000
> message:
> Fix unlikely core dump in init_tty, and simplify terminfo case.
>
> * term.c (init_tty) [TERMINFO]: Fix check for buffer overrun.
> The old version incorrectly dumped core if malloc returned a
> buffer containing only non-NUL bytes.
> (init_tty): Do not allocate or free termcap buffers; the
> struct does that for us now.
> * termchar.h (TERMCAP_BUFFER_SIZE) [!TERMINFO]: New constant.
> (struct tty_display_info): Define members termcap_term_buffer and
> termcap_strings_buffer only if !TERMINFO, since terminfo doesn't
> use them. Allocate them directly in struct rather than indirectly
> via a pointer, to simplify init_tty.
>
> Paul, could you take a look, please?
next prev parent reply other threads:[~2013-09-11 4:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-06 1:46 bug#15282: 24.3.50; Starting a new emacsclient -t instance with another instance running in a separate terminal causes display corruption in the first instance Chow Loong Jin
[not found] ` <handler.15282.B.137843559715898.ack@debbugs.gnu.org>
2013-09-06 3:27 ` bug#15282: Acknowledgement (24.3.50; Starting a new emacsclient -t instance with another instance running in a separate terminal causes display corruption in the first instance.) Chow Loong Jin
2013-09-08 19:40 ` Gregor Zattler
2013-09-06 8:46 ` bug#15282: 24.3.50; Starting a new emacsclient -t instance with another instance running in a separate terminal causes display corruption in the first instance Eli Zaretskii
2013-09-06 9:00 ` Chow Loong Jin
2013-09-06 9:22 ` Eli Zaretskii
2013-09-06 10:14 ` Chow Loong Jin
2013-09-06 10:16 ` Eli Zaretskii
2013-09-11 4:00 ` Eli Zaretskii [this message]
2013-09-11 8:26 ` Paul Eggert
2013-09-11 13:32 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8361u8j9d5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=15282@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=hyperair@debian.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).