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: Wed, 11 Dec 2019 19:20:17 +0200 [thread overview]
Message-ID: <83o8weaiem.fsf@gnu.org> (raw)
In-Reply-To: <4c2a9d55-57d1-4c19-fe20-4ccf61d20d68@yandex.ru> (message from Dmitry Gutov on Wed, 11 Dec 2019 03:13:59 +0200)
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Wed, 11 Dec 2019 03:13:59 +0200
>
> Here are two ways I usually trigger it:
>
> 1. Initiate completion on the "Author:" line of a LogEdit buffer (the
> next line is an inverse-video line).
>
> 2. Have at least one space at the beginning of a line, and have
> whitespace-mode on to highlight it in red. Then initiate completion on
> the preceding line.
Thanks, but I don't think I understand how to reproduce this, based on
your descriptions. Can you show a complete recipe for the second
scenario, starting from "emacs -Q", then loading whitespace-mode and
company-mode, and finally initiating the completion so as to show the
problem?
next prev parent reply other threads:[~2019-12-11 17:20 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 [this message]
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
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=83o8weaiem.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).