From: Po Lu <luangruo@yahoo.com>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: "Alexander Adolf" <alexander.adolf@condition-alpha.com>,
"João Távora" <joaotavora@gmail.com>,
"Eshel Yaron" <me@eshelyaron.com>,
"Juri Linkov" <juri@linkov.net>, "Eli Zaretskii" <eliz@gnu.org>,
emacs-devel@gnu.org
Subject: Re: Inline completion preview
Date: Wed, 01 Nov 2023 21:28:41 +0800 [thread overview]
Message-ID: <877cn1wqk6.fsf@yahoo.com> (raw)
In-Reply-To: <8af5efc7-754a-111d-42d7-b875edbb6202@gutov.dev> (Dmitry Gutov's message of "Tue, 31 Oct 2023 00:49:59 +0200")
Dmitry Gutov <dmitry@gutov.dev> writes:
> The GUI-only users are free to install company-posframe, with similar
> benefits. It's not in GNU ELPA, though: still collecting the last
> copyright assignment signature.
I hope I'm not interrupting, but the free time to follow these
discussions with hasn't come by me as of late.
There are several shortcomings to child frames as they stand: when a
child frame is displayed, the manner in which focus is transferred
between frames becomes erratic; each frame occupies plenty of memory,
reconfiguring such frames is slow, and particular operations possible
with regular frames cannot be performed on child frames under specific
window systems (such as PGTK, where restacking child frames after their
creation is forbidden).
It's better if Emacs didn't incorporate any code or documentation
encouraging users to make use of child frames until such time as the
aforementioned deficiencies are resolved.
next prev parent reply other threads:[~2023-11-01 13:28 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 18:11 Inline completion preview Eshel Yaron
2023-10-26 18:38 ` Eli Zaretskii
2023-10-26 19:39 ` Eshel Yaron
2023-10-27 5:52 ` Eli Zaretskii
2023-10-27 15:43 ` Eshel Yaron
2023-10-27 17:12 ` Eli Zaretskii
2023-10-27 18:13 ` Eshel Yaron
2023-10-27 20:25 ` chad
2023-10-28 16:47 ` Juri Linkov
2023-10-28 19:01 ` Eshel Yaron
2023-10-29 16:24 ` Alexander Adolf
2023-10-29 23:29 ` João Távora
2023-10-30 9:25 ` Juergen Fenn
2023-10-30 9:36 ` João Távora
2023-10-30 11:04 ` Dmitry Gutov
2023-10-30 12:42 ` Alexander Adolf
2023-10-30 13:01 ` João Távora
2023-10-30 17:32 ` Alexander Adolf
2023-10-30 17:52 ` João Távora
2023-10-30 13:20 ` Dmitry Gutov
2023-10-30 17:43 ` Alexander Adolf
2023-10-30 22:49 ` Dmitry Gutov
2023-10-31 6:50 ` Eshel Yaron
2023-10-31 17:31 ` Alexander Adolf
2023-10-31 17:43 ` Eshel Yaron
2023-10-31 23:29 ` Dmitry Gutov
2023-11-01 8:30 ` Eshel Yaron
2023-11-01 10:11 ` João Távora
2023-11-01 10:44 ` Eshel Yaron
2023-11-01 11:07 ` João Távora
2023-11-01 12:17 ` Eshel Yaron
2023-11-01 12:23 ` Dmitry Gutov
2023-11-01 14:07 ` Juergen Fenn
2023-11-01 19:57 ` Dmitry Gutov
2023-11-01 12:08 ` Dmitry Gutov
2023-11-01 12:14 ` Dmitry Gutov
2023-11-01 12:24 ` Dmitry Gutov
2023-11-01 12:29 ` Eshel Yaron
2023-11-01 12:32 ` Dmitry Gutov
2023-11-01 12:34 ` Eli Zaretskii
2023-11-01 12:36 ` Dmitry Gutov
2023-11-01 13:28 ` Po Lu [this message]
2023-11-01 19:49 ` Dmitry Gutov
2023-10-27 8:58 ` Ihor Radchenko
2023-10-27 15:53 ` Eshel Yaron
2023-10-27 11:49 ` João Távora
2023-10-27 11:52 ` João Távora
2023-10-27 12:18 ` Eli Zaretskii
2023-10-27 12:55 ` João Távora
2023-10-27 12:58 ` Eli Zaretskii
2023-10-27 13:05 ` Dmitry Gutov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877cn1wqk6.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=alexander.adolf@condition-alpha.com \
--cc=dmitry@gutov.dev \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=joaotavora@gmail.com \
--cc=juri@linkov.net \
--cc=me@eshelyaron.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.