all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: tfheen@err.no, 66398@debbugs.gnu.org
Subject: bug#66398: 29.1; Buggy handling of transparency changes / blur/unblur
Date: Mon, 16 Oct 2023 14:51:15 +0300	[thread overview]
Message-ID: <831qdupyz0.fsf@gnu.org> (raw)
In-Reply-To: <87lec36usq.fsf@yahoo.com> (message from Po Lu on Mon, 16 Oct 2023 12:44:05 +0800)

> From: Po Lu <luangruo@yahoo.com>
> Cc: Eli Zaretskii <eliz@gnu.org>,  66398@debbugs.gnu.org
> Date: Mon, 16 Oct 2023 12:44:05 +0800
> 
> Tollef Fog Heen <tfheen@err.no> writes:
> 
> > ]] Po Lu 
> >
> >> Oh, I see, thanks.  Please test the attached patch:
> >
> > With the patch, I am no longer able to reproduce the problem.  Thanks
> > for the help fixing this problem!
> >
> > Regards,
> 
> Thanks.  Eli, is this safe for Emacs 29?

I guess so, thanks.





  reply	other threads:[~2023-10-16 11:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-07 20:07 bug#66398: 29.1; Buggy handling of transparency changes / blur/unblur Tollef Fog Heen
2023-10-14  8:13 ` Eli Zaretskii
2023-10-14  8:23   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-14 17:31     ` Tollef Fog Heen
2023-10-15  1:25       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-15 20:14         ` Tollef Fog Heen
2023-10-16  0:51           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-16  4:42             ` Tollef Fog Heen
2023-10-16  4:44               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-16 11:51                 ` Eli Zaretskii [this message]
2023-10-17  0:34                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=831qdupyz0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=66398@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=tfheen@err.no \
    /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.