unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: tumashu  <tumashu@163.com>
To: "martin rudalics" <rudalics@gmx.at>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re:Re: How to create a small child-frame which only show two lines
Date: Mon, 11 Dec 2017 08:21:21 +0800 (CST)	[thread overview]
Message-ID: <65b6adf3.bf1.16042f29094.Coremail.tumashu@163.com> (raw)
In-Reply-To: <5A2BBC7E.9020400@gmx.at>

[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]

Font's align problem is not a big problem :-), Chinese emacs user's fonts setup is complicate, so
it is not easily to use set-frame-font.  so I decide just ignore this small problem :-)


I have use `mode-line-format' and `header-line-format' , they are more simple. thanks for this good tip.







At 2017-12-09 18:35:42, "martin rudalics" <rudalics@gmx.at> wrote:
> > Thank your for your help, I have solved the problem: I add (window-min-height 1) and (window-min-width 1))
> > to my code and let my English main font is taller than my Chinese fonts.
>
>Would setting `set-frame-font' for that child frame help then?  Provided
>you can say in advance which of your fonts should be the dominant one
>for the frame in question.
>
>BTW, note that setting these parameters
>
>     (set-window-parameter window 'mode-line-format 'none)
>     (set-window-parameter window 'header-line-format 'none))
>
>is generally only needed when you show the corresponding buffer in a
>"normal" window and in a child frame window.  If you show the buffer in
>a child frame only, setting the buffer-local values of
>`mode-line-format' and `header-line-format' to nil usually suffices.
>
>martin

[-- Attachment #2: Type: text/html, Size: 1489 bytes --]

  reply	other threads:[~2017-12-11  0:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-07  0:04 How to create a small child-frame which only show two lines tumashu
2017-12-07  2:35 ` jun
2017-12-07  2:45   ` tumashu
2017-12-07  9:27 ` How " martin rudalics
2017-12-08 10:12   ` martin rudalics
2017-12-08 12:05     ` tumashu
2017-12-09 10:35       ` martin rudalics
2017-12-11  0:21         ` tumashu [this message]
2017-12-11  6:42           ` martin rudalics
2017-12-11  8:29             ` tumashu
2017-12-11 15:29               ` Eli Zaretskii
2017-12-12  0:43                 ` tumashu
2017-12-12  3:22                   ` Stefan Monnier
2017-12-12  8:56                     ` martin rudalics
2017-12-12 16:26                   ` Eli Zaretskii
2017-12-12 16:48                     ` Stefan Monnier
2017-12-12 17:19                       ` Eli Zaretskii
2018-01-07  2:56                 ` Feng Shu
2017-12-12  8:56               ` martin rudalics
2017-12-12 12:19                 ` Feng Shu
2017-12-12 17:05                 ` Eli Zaretskii
2017-12-13  8:50                   ` martin rudalics
2018-01-06 10:42                 ` 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=65b6adf3.bf1.16042f29094.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).