unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Perry E. Metzger" <perry@piermont.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: malsburg@posteo.de, emacs-devel@gnu.org
Subject: Re: [PATCH] Implement functions for measuring fonts and max chars per line
Date: Sun, 18 Jan 2015 17:26:33 -0500	[thread overview]
Message-ID: <20150118172633.61609906@jabberwock.cb.piermont.com> (raw)
In-Reply-To: <83h9voyu9m.fsf@gnu.org>

On Sun, 18 Jan 2015 17:37:41 +0200 Eli Zaretskii <eliz@gnu.org> wrote:
> > Regardless, my .emacs currently includes
> >
> > (if window-system
> >     (add-to-list 'default-frame-alist
> > 		 (cons 'height 60)))
> >
> > and I'd like to compute which "height" is full height for my
> > display (again, rather than simply figuring a number out by trial
> > and error).
>
> So your actual goal is to maximize the frame's height.

No, my goal is that all new emacs frames, including the first one,
start out at a maximum height -- but my broader goal is to know what
that height is programatically. I do things at times like setting up
an elisp function to achieve a particular window layout, for example,
and knowing what the maximum height is comes in use there as well.

> > How about (set-frame-parameter nil 'fullscreen 'fullheight)?
>
> Isn't that exactly what you want?

Not really. That will maximize the current frame only at the moment it
is executed, and it doesn't tell me in advance what the height (in
lines) is going to end up being.

What I want is to know (by calculation) what the maximum height, in
lines, happens to be so I can shove that in for 'height in
default-frame-alist. (There are other uses for such information of
course, see above.)

Perry
-- 
Perry E. Metzger		perry@piermont.com



  reply	other threads:[~2015-01-18 22:26 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-22 14:39 [PATCH] Implement functions for measuring fonts and max chars per line Titus von der Malsburg
2014-12-22 22:25 ` Titus von der Malsburg
2014-12-23 12:52   ` Titus von der Malsburg
2015-01-17 18:13     ` Titus von der Malsburg
2015-01-17 18:43       ` Eli Zaretskii
2015-01-17 20:38       ` Perry E. Metzger
2015-01-17 20:41         ` Eli Zaretskii
2015-01-17 22:21           ` Perry E. Metzger
2015-01-17 22:24             ` David Kastrup
2015-01-18  0:08               ` Perry E. Metzger
2015-01-18  0:11               ` Perry E. Metzger
2015-01-18  1:01                 ` Michael Heerdegen
2015-01-18  3:42             ` Eli Zaretskii
2015-01-18  4:08               ` Perry E. Metzger
2015-01-18 15:37                 ` Eli Zaretskii
2015-01-18 22:26                   ` Perry E. Metzger [this message]
2015-01-19  0:38                     ` Drew Adams
2015-01-19  2:56                       ` Perry E. Metzger
2015-01-19  3:41                         ` Eli Zaretskii
2015-01-19 13:31                           ` Perry E. Metzger
2015-01-19 16:21                             ` Eli Zaretskii
2015-01-19 21:49                               ` Perry E. Metzger
2015-01-19  2:01                     ` Michael Heerdegen
2015-01-19  3:37                     ` Eli Zaretskii
2015-03-21 10:33       ` Eli Zaretskii

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=20150118172633.61609906@jabberwock.cb.piermont.com \
    --to=perry@piermont.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=malsburg@posteo.de \
    /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).