From: "Feng Shu" <tumashu@163.com>
To: martin rudalics <rudalics@gmx.at>
Cc: Emacs-Devel <emacs-devel@gnu.org>
Subject: Re: Is it possible let child-frame not hide the mode-line and minibuffer out
Date: Sun, 04 Feb 2018 10:45:44 +0800 [thread overview]
Message-ID: <874lmx321z.fsf@163.com> (raw)
In-Reply-To: <5A757B47.8020502@gmx.at> (martin rudalics's message of "Sat, 03 Feb 2018 10:05:11 +0100")
[-- Attachment #1: Type: text/plain, Size: 825 bytes --]
martin rudalics <rudalics@gmx.at> writes:
>> When a child-frame move to position (-1 . 0), it will hide its
>> parent-frame's mode-line and minibuffer, is it possible let child-frame
>> auto move above a little, and let it not hide its parent-frame's
>> mode-line and minibuffer?
>
> I'm not sure why a position like (-1 . 0) should do that - did you
> mean (0 . -1)?
>
> But what is "auto" move? Positioning and sizing of child frames is
> completely left to the caller with one exception: When the parent
> frame is resized, the child frame may have to be resized and
> repositioned too. IIRC we try to do that proportionally so it's
> possible that the parent frame's mode line gets obscured. Is it that
> you had in mind?
>
sorry, it is (0 . -1) :-)
If I move a child-frame to (0 . -1), it like this at the moment:
[-- Attachment #2: 1.png --]
[-- Type: image/png, Size: 80460 bytes --]
[-- Attachment #3: Type: text/plain, Size: 86 bytes --]
but I think the below result is more useful when I move a child-frame to
(0 . -1)
[-- Attachment #4: 2.png --]
[-- Type: image/png, Size: 62595 bytes --]
[-- Attachment #5: Type: text/plain, Size: 19 bytes --]
> martin
>
--
next prev parent reply other threads:[~2018-02-04 2:45 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 [this message]
2018-02-04 10:02 ` martin rudalics
2018-02-04 11:43 ` tumashu
2018-02-05 7:53 ` tumashu
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=874lmx321z.fsf@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 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.