From: "समीर सिंह Sameer Singh" <lumarzeli30@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: 58424@debbugs.gnu.org
Subject: bug#58424: [PATCH] Ensure emacs-pgtk does not get stuck after iconify-frame
Date: Tue, 11 Oct 2022 09:34:59 +0530 [thread overview]
Message-ID: <CAOR1sLwUubL2AZcLskeXmLutZMcm174kzbBhXikOnki17djijw@mail.gmail.com> (raw)
In-Reply-To: <87o7ujjacy.fsf@yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]
>
> forcemerge 55836 58424
oops, looks like I missed this discussion.
Thanks for working on this, I will wait for a fix.
On Tue, Oct 11, 2022 at 9:11 AM Po Lu <luangruo@yahoo.com> wrote:
> forcemerge 55836 58424
>
> समीर सिंह Sameer Singh <lumarzeli30@gmail.com> writes:
>
> > On Tue, Oct 11, 2022 at 6:11 AM समीर सिंह Sameer Singh <
> lumarzeli30@gmail.com> wrote:
> >
> > steps to reproduce
> > 1. configure emacs to use pgtk
> > 2. emacs -Q
> > 3. C-z or M-x iconify-frame
> > 4. Restore emacs by clicking on its icon
> > Emacs does not display characters any more.
> >
> > I believe this bug is similar to bug#42655 except this time it is for
> pgtk and not lucid.
> >
> > I believe I have fixed this problem and will attach a patch in the next
> mail, but the thing is I have no idea how I fixed it so please check for
> any unintended
> > consequences.
>
> This is definitely not the right fix.
>
> I'm still looking into that problem, and will definitely fix it before
> November.
>
[-- Attachment #2: Type: text/html, Size: 1737 bytes --]
prev parent reply other threads:[~2022-10-11 4:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 0:41 bug#58424: [PATCH] Ensure emacs-pgtk does not get stuck after iconify-frame समीर सिंह Sameer Singh
2022-10-11 0:44 ` समीर सिंह Sameer Singh
2022-10-11 3:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-11 4:04 ` समीर सिंह Sameer Singh [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOR1sLwUubL2AZcLskeXmLutZMcm174kzbBhXikOnki17djijw@mail.gmail.com \
--to=lumarzeli30@gmail.com \
--cc=58424@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.