From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 38563@debbugs.gnu.org
Subject: bug#38563: 27.0.50; Company popup renders with newlines (?) inheriting the bg properties of the character at next line's bol
Date: Sat, 21 Dec 2019 15:31:13 +0200 [thread overview]
Message-ID: <83r20xzty6.fsf@gnu.org> (raw)
In-Reply-To: <3c20fcbd-5d36-9a33-dd52-dddaab219fad@yandex.ru> (message from Dmitry Gutov on Sat, 21 Dec 2019 15:22:46 +0200)
> Cc: 38563-done@debbugs.gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Sat, 21 Dec 2019 15:22:46 +0200
>
> > In fact, I was about to
> > ask you to make a similar (less elegant) change,
>
> Like temporarily changing the face of the underlying character? Yeah, I
> would have paused at that idea.
No, a different change in the face you put on the newline.
> > because I couldn't
> > think of a way to resolve this in core: when a face explicitly asks to
> > extend itself past EOL, we cannot in good faith refrain from doing so
> > in some use cases.
>
> Let's see if other third-party issues come up, then.
Right.
prev parent reply other threads:[~2019-12-21 13:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 1:13 bug#38563: 27.0.50; Company popup renders with newlines (?) inheriting the bg properties of the character at next line's bol Dmitry Gutov
2019-12-11 17:20 ` Eli Zaretskii
2019-12-11 21:47 ` Dmitry Gutov
2019-12-12 11:32 ` Eli Zaretskii
2019-12-12 22:13 ` Dmitry Gutov
2019-12-13 8:22 ` Eli Zaretskii
2019-12-13 9:30 ` Eli Zaretskii
2019-12-13 10:31 ` Eli Zaretskii
2019-12-13 12:00 ` Dmitry Gutov
2019-12-13 10:17 ` Dmitry Gutov
2019-12-13 14:12 ` Eli Zaretskii
2019-12-13 15:04 ` Dmitry Gutov
2019-12-13 15:32 ` Eli Zaretskii
2019-12-13 23:10 ` Dmitry Gutov
2019-12-14 8:13 ` Eli Zaretskii
2019-12-15 22:26 ` Dmitry Gutov
2019-12-16 15:49 ` Eli Zaretskii
2019-12-18 20:37 ` Dmitry Gutov
2019-12-21 7:53 ` Eli Zaretskii
2019-12-21 13:22 ` Dmitry Gutov
2019-12-21 13:31 ` Eli Zaretskii [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
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=83r20xzty6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=38563@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
/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).