unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Daniel Clemente <n142857@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 71343@debbugs.gnu.org
Subject: bug#71343: 30.0.50; TTY frame doesn't automatically redisplay itself after having closed another frame
Date: Thu, 6 Jun 2024 13:22:45 +0000	[thread overview]
Message-ID: <CAJKAhPA04Qi=m2cYGCQE5aQgRK1rid-b9jXugmWUB0UKa5A9Hg@mail.gmail.com> (raw)
In-Reply-To: <86jzj6kmyh.fsf@gnu.org>

> What do you mean by "kill the terminal running emacsclient" in step 6?

Pressing a wmii key, that closes the X window. I don' know which
signal it sends, but kill -SIGQUIT pid also reproduces this issue.

I found an easier way to reproduce it. No left/right columns needed

1. Using X (I reproduced this in wmii and icewm; more on this below)
2. emacs --fg-daemon -Q
3. I run this command twice: urxvt -e 'emacsclient' '-c' &. Now I have
2 X windows running, and emacsclient works fine in both (including
resizing the X window)
4. I go to the last one of those two
5. I press the window manager key to close the window, this kills
urxvt  with the emacsclient that's running inside
6. I see the other X window (the first one) with emacsclient inside,
but it doesn't refresh. If I resize it, black space or garbage
appears. In some rare cases it gets messy: the text of the line I'm
editing (where the cursor is) doesn't appear in the cursor line but
somewhere else, e.g. 1 line below. In those cases I need to restart
something, maybe the daemon.



> Also, since you mention the window manager, does it mean the problem
> doesn't happen with other window managers, if you start 2 emacsclient
> sessions with the same daemon and then "kill" (whatever that means)
> one of these two sessions?

I just reproduced the same in icewm.

Killing the 2nd window, and then resizing the 1st one to make it
wider, the new areas are black.

There may be some details or differences because I'm not familiar with icewm.





  reply	other threads:[~2024-06-06 13:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-03 15:33 bug#71343: 30.0.50; TTY frame doesn't automatically redisplay itself after having closed another frame Daniel Clemente
2024-06-03 16:31 ` Eli Zaretskii
2024-06-06 13:22   ` Daniel Clemente [this message]
2024-06-06 11:54 ` Eli Zaretskii
2024-06-06 13:24   ` Daniel Clemente
2024-06-06 13:44     ` Eli Zaretskii
2024-06-16  5:40       ` Daniel Clemente
2024-06-16  6:33         ` Eli Zaretskii
2024-06-21 10:47           ` Daniel Clemente

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='CAJKAhPA04Qi=m2cYGCQE5aQgRK1rid-b9jXugmWUB0UKa5A9Hg@mail.gmail.com' \
    --to=n142857@gmail.com \
    --cc=71343@debbugs.gnu.org \
    --cc=eliz@gnu.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).