From: Eli Zaretskii <eliz@gnu.org>
To: joaotavora@gmail.com
Cc: 54488@debbugs.gnu.org, dgutov@yandex.ru
Subject: bug#54488: 29.0.50; move-to-column/overlay-related regression in latest master, perhaps 28?
Date: Tue, 22 Mar 2022 15:57:17 +0200 [thread overview]
Message-ID: <835yo6f5tu.fsf@gnu.org> (raw)
In-Reply-To: <83a6difahu.fsf@gnu.org> (message from Eli Zaretskii on Tue, 22 Mar 2022 14:16:29 +0200)
> Date: Tue, 22 Mar 2022 14:16:29 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 54488@debbugs.gnu.org, dgutov@yandex.ru
>
> > > You can try putting a multiline string on the 'display property.
> > >
> > > Instead of just "BAR".
> >
> > I tried that, but I don't know how to align it like company does.
> >
> > > Apart from that, I can only suggest reading the code and
> > > experimenting.
> >
> > I admit I was hoping that you as company maintainer/specialist :-) could
> > provide a small snippet to create a dummy but company-realistic overlay
> > of, say, two completion "foo" and "bar" in the middle of any buffer. Or
> > perhaps explain in layman's terms how company constructs its overlays.
> >
> > Not asking that you get to the root of the move-to-column problem, which
> > is clearly a regression (presumably a regression to correct behaviour,
> > but a regression nonetheless) just help perhaps come up with a simpler
> > repro to assist Eli in seeing the issue.
>
> Thank you for your efforts. I will take a look at this issue when I
> have time, hopefully soon enough.
I think I see the problem. Stay tuned.
next prev parent reply other threads:[~2022-03-22 13:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 6:54 bug#54488: 29.0.50; move-to-column/overlay-related regression in latest master, perhaps 28? João Távora
2022-03-21 12:32 ` Eli Zaretskii
2022-03-21 16:37 ` João Távora
2022-03-21 17:05 ` Eli Zaretskii
2022-03-21 21:59 ` João Távora
2022-03-21 23:14 ` Dmitry Gutov
2022-03-22 9:48 ` João Távora
2022-03-22 12:16 ` Eli Zaretskii
2022-03-22 13:57 ` Eli Zaretskii [this message]
2022-03-22 14:31 ` Eli Zaretskii
2022-03-22 14:54 ` João Távora
2022-03-22 15:22 ` Eli Zaretskii
2022-03-22 16:06 ` João Távora
2022-03-22 16:53 ` Eli Zaretskii
2022-03-22 21:05 ` João Távora
2022-03-22 23:55 ` Dmitry Gutov
2022-03-23 1:11 ` João Távora
2022-03-23 3:39 ` Eli Zaretskii
2022-03-23 10:10 ` João Távora
2022-03-23 11:08 ` João Távora
2022-03-23 14:21 ` Eli Zaretskii
2022-03-24 15:01 ` João Távora
2022-03-24 15:29 ` Eli Zaretskii
2022-03-24 16:03 ` João Távora
2022-03-24 16:59 ` Eli Zaretskii
2022-03-23 3:34 ` Eli Zaretskii
2022-03-23 3:29 ` Eli Zaretskii
2022-03-23 10:04 ` João Távora
2022-03-23 13:23 ` Eli Zaretskii
2022-03-24 14:54 ` João Távora
2022-03-22 12:33 ` Dmitry Gutov
2022-03-22 13:50 ` João Távora
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=835yo6f5tu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=54488@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=joaotavora@gmail.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).