From: Drew Adams <drew.adams@oracle.com>
To: Daniel Colascione <dancol@dancol.org>, 16619@debbugs.gnu.org
Subject: bug#16619: 24.3.50; REGRESSION: transparent *Completions* now
Date: Sat, 1 Feb 2014 16:06:00 -0800 (PST) [thread overview]
Message-ID: <b0bc2a9d-1f4f-4046-8e2a-52f7d3654acf@default> (raw)
In-Reply-To: <52ED8592.70502@dancol.org>
> What happens if you set frame-alpha-lower-limit to 100?
Yes, that fixes the problem. Thank you, Daniel! That gives
me a temporary workaround.
But I hope that is not the ultimate answer, and that you mean
that as something more than a workaround (I doubt that you do).
IOW, I don't think I should have to set this to 100.
I'm not familiar with this variable, but it seems to affect
all frames wrt frame parameter `alpha'. I do not want to be
limited to not having frames of different opacity. (No, I do
not currently use frames that are semi-transparent. But I do
not want to be gratuitously prevented from doing so.)
> I don't think anyone made this change deliberately.
I don't suppose so either. But I'm not sure what new features
that have been allowed might have been tweaked lately to make
them "work" better and which fix might have broken other things.
IOW, I have no idea what the cause is. To me, this is just a
regression, regardless of the source.
next prev parent reply other threads:[~2014-02-02 0:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-01 23:11 bug#16619: 24.3.50; REGRESSION: transparent *Completions* now Drew Adams
2014-02-01 23:38 ` Daniel Colascione
2014-02-01 23:46 ` Juanma Barranquero
2014-02-02 0:06 ` Drew Adams [this message]
2014-02-02 0:09 ` Daniel Colascione
2014-02-02 4:01 ` Drew Adams
2014-02-02 6:39 ` Juanma Barranquero
2014-02-02 13:19 ` martin rudalics
2014-02-02 13:19 ` martin rudalics
2014-02-02 15:41 ` Drew Adams
2014-02-02 16:04 ` Drew Adams
2014-02-01 23:57 ` Drew Adams
2014-11-26 21:33 ` bug#16619: 24.4.1; REGRESSION: transparent *Completions* Alan Schmitt
2014-11-26 21:52 ` Glenn Morris
2014-11-27 7:56 ` Alan Schmitt
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=b0bc2a9d-1f4f-4046-8e2a-52f7d3654acf@default \
--to=drew.adams@oracle.com \
--cc=16619@debbugs.gnu.org \
--cc=dancol@dancol.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).