From: Feng Shu <tumashu@163.com>
To: martin rudalics <rudalics@gmx.at>
Cc: "Gerd Möllmann" <gerd.moellmann@gmail.com>,
"Emacs Devel" <emacs-devel@gnu.org>
Subject: Re: Question about minibuffer and child frames (Posframe)
Date: Mon, 07 Oct 2024 17:46:32 +0800 [thread overview]
Message-ID: <87wmikjldz.fsf@163.com> (raw)
In-Reply-To: <15f64df2-ae81-4d06-9c9a-964504c5a285@gmx.at> (martin rudalics's message of "Mon, 7 Oct 2024 10:35:11 +0200")
martin rudalics <rudalics@gmx.at> writes:
>> INTERNAL-BORDER-WIDTH and INTERNAL-BORDER-COLOR are same as
>> BORDER-WIDTH and BORDER-COLOR, but do not suggest to use for the
>> reason:
>>
>> Add distinct controls for child frames' borders (Bug#45620)
>> http://git.savannah.gnu.org/cgit/emacs.git/commit/?id=ff7b1a133bfa7f2614650f8551824ffaef13fadc
>
> Do you mean separate child frame borders don't work?
No, before child frame have it own border, posframe use internal-border,
so we have both just for back compatibility.
>
> martin
>
--
next prev parent reply other threads:[~2024-10-07 9:46 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 12:50 Question about minibuffer and child frames (Posframe) Gerd Möllmann
2024-10-02 13:39 ` Po Lu
2024-10-02 13:52 ` Gerd Möllmann
2024-10-02 14:56 ` martin rudalics
2024-10-02 15:47 ` Gerd Möllmann
2024-10-02 16:08 ` martin rudalics
2024-10-02 17:17 ` Gerd Möllmann
2024-10-02 17:34 ` martin rudalics
2024-10-02 18:48 ` Gerd Möllmann
2024-10-03 7:35 ` Gerd Möllmann
2024-10-03 8:26 ` martin rudalics
2024-10-03 9:07 ` Gerd Möllmann
2024-10-03 9:33 ` martin rudalics
2024-10-03 9:50 ` Gerd Möllmann
2024-10-03 13:12 ` martin rudalics
2024-10-03 14:03 ` Gerd Möllmann
2024-10-04 7:24 ` Gerd Möllmann
2024-10-04 8:10 ` martin rudalics
2024-10-04 9:16 ` Gerd Möllmann
2024-10-04 9:31 ` martin rudalics
2024-10-04 9:55 ` Gerd Möllmann
2024-10-05 8:31 ` Gerd Möllmann
2024-10-02 18:43 ` Eli Zaretskii
2024-10-02 18:56 ` Gerd Möllmann
2024-10-07 1:08 ` Feng Shu
2024-10-07 4:28 ` Gerd Möllmann
2024-10-07 6:43 ` Feng Shu
2024-10-07 8:00 ` Gerd Möllmann
2024-10-07 8:17 ` Feng Shu
2024-10-07 8:32 ` Gerd Möllmann
2024-10-07 10:03 ` Feng Shu
2024-10-07 10:46 ` Gerd Möllmann
2024-10-07 13:44 ` martin rudalics
2024-10-07 14:29 ` Gerd Möllmann
2024-10-07 21:45 ` Feng Shu
2024-10-08 4:19 ` Gerd Möllmann
2024-10-08 5:01 ` Gerd Möllmann
2024-10-08 5:42 ` Feng Shu
2024-10-08 6:31 ` Gerd Möllmann
2024-10-08 13:06 ` Gerd Möllmann
2024-10-07 8:35 ` martin rudalics
2024-10-07 8:46 ` Gerd Möllmann
2024-10-07 8:52 ` martin rudalics
2024-10-07 9:12 ` Gerd Möllmann
2024-10-07 10:11 ` Feng Shu
2024-10-07 10:36 ` Gerd Möllmann
2024-10-07 12:12 ` Feng Shu
2024-10-07 12:24 ` Gerd Möllmann
2024-10-07 13:44 ` martin rudalics
2024-10-07 14:24 ` Gerd Möllmann
2024-10-07 8:35 ` martin rudalics
2024-10-07 9:46 ` Feng Shu [this message]
2024-10-07 7:20 ` Feng Shu
2024-10-07 8:12 ` Gerd Möllmann
2024-10-11 8:03 ` Gerd Möllmann
2024-10-07 8:34 ` martin rudalics
2024-10-07 9:35 ` Feng Shu
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=87wmikjldz.fsf@163.com \
--to=tumashu@163.com \
--cc=emacs-devel@gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=rudalics@gmx.at \
/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).