From: tumashu <tumashu@163.com>
To: "martin rudalics" <rudalics@gmx.at>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re:Re: Is it possible let child-frame not hide the mode-line and minibuffer out
Date: Mon, 5 Feb 2018 15:53:40 +0800 (CST) [thread overview]
Message-ID: <4a882d58.833c.16164f4cccb.Coremail.tumashu@163.com> (raw)
In-Reply-To: <5A76DA1B.3050103@gmx.at>
[-- Attachment #1: Type: text/plain, Size: 1211 bytes --]
I have re-read the elisp documents and found it is not a problem :-), sorry for disturb...
A positive integer always relates the left edge of the frame
to the left edge of its display or parent frame. A negative
integer relates the right frame edge to the right edge of the
display or parent frame.
At 2018-02-04 18:02:03, "martin rudalics" <rudalics@gmx.at> wrote:
> > but I think the below result is more useful when I move a child-frame to
> > (0 . -1)
>
>We should not inhibit placement there just as we allow a frame to hide
>the taskbar of the window manager on the desktop. But we could
>provide a parameter for child frames that would, if set, accomplish
>that.
>
>Could you try coding such a thing? The value to be added in the
>y-direction should account for the internal border width of the frame,
>the height of the minibuffer, a vertical window divider and the height
>of the mode line if these are set. In the x-direction we then should
>probably avoid hiding the internal border as well. And we probably
>should disable the effect of this if it would cause the child frame to
>no more fit into its parent at the top or the right.
>
>martin
[-- Attachment #2: Type: text/html, Size: 1680 bytes --]
prev parent reply other threads:[~2018-02-05 7:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 15:57 Is it possible let child-frame not hide the mode-line and minibuffer out Feng Shu
2018-02-03 9:05 ` martin rudalics
2018-02-04 2:45 ` Feng Shu
2018-02-04 10:02 ` martin rudalics
2018-02-04 11:43 ` tumashu
2018-02-05 7:53 ` tumashu [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=4a882d58.833c.16164f4cccb.Coremail.tumashu@163.com \
--to=tumashu@163.com \
--cc=emacs-devel@gnu.org \
--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).