GNU bug report logs - #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.

Previous Next

Full log

Message #16 received at 15282 <at> debbugs.gnu.org (full text, mbox):

From: Chow Loong Jin <hyperair <at> debian.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 15282 <at> debbugs.gnu.org
Subject: Re: 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: Fri, 6 Sep 2013 17:00:37 +0800

[Message part 1 (text/plain, inline)]

On Fri, Sep 06, 2013 at 11:46:35AM +0300, Eli Zaretskii wrote:
> > Date: Fri, 6 Sep 2013 09:46:17 +0800
> > From: Chow Loong Jin <hyperair <at> 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.
> 
> Don't you also see some stray characters in the mode line?  (Your
> snapshot didn't show the mode lines of the two client frames.)

Yeah the stray characters are part of the corruption. It gets even weirder in
the presence of fci-mode or linum-mode.

Doesn't the screenshot show the corrupted portions of the modeline?

-- 
Kind regards,
Loong Jin

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.