From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: sva-news@mygooglest.com, 18480@debbugs.gnu.org
Subject: bug#18480: 24.3.93; Popups "broken" with lines of different heights
Date: Mon, 15 Sep 2014 22:55:35 +0300 [thread overview]
Message-ID: <83tx484q14.fsf@gnu.org> (raw)
In-Reply-To: <jwvlhpk66me.fsf-monnier+emacsbugs@gnu.org>
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Sebastien Vauban <sva-news@mygooglest.com>, 18480@debbugs.gnu.org
> Date: Mon, 15 Sep 2014 15:13:48 -0400
>
> >> As demo'ed with this Org file, enabling completion mechanisms such as AC
> >> or Company shows graphical glitches when themes have heights != 1.0.
> > Since neither of these packages is part of Emacs, I think you should
> > report this to the respective developers instead.
>
> Since Company is part of GNU ELPA, I think it's OK to report its bugs here.
> In any case, I'm pretty sure this is a known limitation that will only
> be lifted when those packages start using "lightweight frames" or "GUI
> menus" or something like that, and I think those will require changes to
> the C code.
Maybe so, but I think the respective developers should first be given
chance to fix this or improve it, if they can. Only if the developers
come to the conclusion that there are fundamental problems that
prevent the solution, then they should come here with the details.
Alternatively, the OP could look into the sources and make sure these
are not simple bugs in those packages, then explain all that in the
report.
Failing any of these, I don't see how filing this report can be of any
use. I mean, who will look at this?
next prev parent reply other threads:[~2014-09-15 19:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 10:26 bug#18480: 24.3.93; Popups "broken" with lines of different heights Sebastien Vauban
2014-09-15 15:00 ` Eli Zaretskii
2014-09-15 19:13 ` Stefan Monnier
2014-09-15 19:55 ` Eli Zaretskii [this message]
2014-09-16 0:13 ` Stefan Monnier
2016-02-19 8:34 ` Marcin Borkowski
2016-02-19 8:57 ` Eli Zaretskii
2016-02-19 9:22 ` Dmitry Gutov
2016-02-19 10:11 ` Eli Zaretskii
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=83tx484q14.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=18480@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=sva-news@mygooglest.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 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).