unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: rudalics@gmx.at, emacs-devel@gnu.org
Subject: Re: frame size&position woes
Date: Mon, 22 Jul 2013 18:52:55 +0300	[thread overview]
Message-ID: <837ggiy4ko.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0SREjpNo8Q+yyvZbVb7ow_YVQp9y+jz-HWB70WF-nbdn9A@mail.gmail.com>

> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Mon, 22 Jul 2013 11:40:49 +0200
> Cc: Emacs developers <emacs-devel@gnu.org>
> 
> On Mon, Jul 22, 2013 at 10:22 AM, martin rudalics <rudalics@gmx.at> wrote:
> 
> > Admittedly, it's not easy to specify what the height should be in this
> > case.
> 
> Which highlights that the usefulness of `frame-height' is relatively limited.

Is your problem, in practice, only with those weirdo frames that have
their tool bars and/or menu bars wrapped?  Or do you have problems
with the more "dull" use cases as well?

If the latter, can you describe the unsolved problem(s) you have in
that case?

> Honestly, at this point I'd rather have Emacs do one of these things,
> that the current "incredible shrinking frame" phenomenon with wrapping
> menus that I reported in another message.

People who wrap menus deserve that.

> I love how two simple requests: "Can I have the dimensions of that
> frame, please?" and "Can I create another frame with that very same
> metrics?" get so complex and GUI dependent answers.

It's not complex.  AFAIK, "(make-frame '((height . N)))" creates a
frame whose "(frame-height)" returns N plus the value returned by
tool-bar-lines-needed.  I expect the same to be true on X, with the
exception of a GTK build, where we might need to do something special.

Does this solve the problem with visible frames?  If not, what is
left?



  reply	other threads:[~2013-07-22 15:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-21 12:56 frame size&position woes Juanma Barranquero
2013-07-21 12:58 ` Juanma Barranquero
2013-07-21 14:03 ` martin rudalics
2013-07-21 15:42   ` Juanma Barranquero
2013-07-21 15:58     ` Juanma Barranquero
2013-07-22  8:22     ` martin rudalics
2013-07-22  9:40       ` Juanma Barranquero
2013-07-22 15:52         ` Eli Zaretskii [this message]
2013-07-22 20:36           ` Juanma Barranquero
2013-07-23  2:45             ` Eli Zaretskii
2013-07-23 23:47               ` Juanma Barranquero
2013-07-24  3:55                 ` Eli Zaretskii
2013-07-24 10:42                   ` Juanma Barranquero
2013-07-24 14:37                     ` Eli Zaretskii
2013-07-24 14:51                       ` Juanma Barranquero
2013-07-24 16:55                         ` Eli Zaretskii
2013-07-24 17:01                           ` Juanma Barranquero
2013-07-24 17:41                             ` Eli Zaretskii
2013-07-24 17:49                               ` Juanma Barranquero

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=837ggiy4ko.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@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).