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: Tue, 23 Jul 2013 05:45:37 +0300 [thread overview]
Message-ID: <83y58yvvse.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0SSfu4o6h8RPhLPgnDEi4uMAWyrOQPCXcdWB29m7wLa7Fg@mail.gmail.com>
> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Mon, 22 Jul 2013 22:36:33 +0200
> Cc: martin rudalics <rudalics@gmx.at>, Emacs developers <emacs-devel@gnu.org>
>
> > If the latter, can you describe the unsolved problem(s) you have in
> > that case?
>
> The biggest problem right now is not related to frame-height, but
> frame-pixel-height, that is, we'd need a function that returned (for
> every available window system and toolkit) the real width & height of
> an Emacs frame in pixels, not of the client area, but the whole frame.
> It's the only sane way to check whether a frame is currently visible
> in a monitor.
Why do you need all that? Isn't frame-height, frame-width, and the
top and left frame parameters enough to restore the frame's dimensions
and position?
> > People who wrap menus deserve that.
>
> On one hand, I agree with you. It's ugly and I would never do it. On
> the other hand, I'm not trying to make desktop-restore-frames work for
> me, but for as many users as possible. And we have an elisp API to
> create a frame without menu-bar or remove it from one (via frame
> parameters), but I don't think we have a UI command to do that, so if
> the user wants to use menus, but s/he also wants to have a narrow
> frame for some reason (let's say, to follow the output of some command
> which only prints short lines), s/he's forced to make the frame wider,
> or accept a wrapped menu. If s/he then saves & restores...
...then the frame will not be restored to the exact size it was, but
maybe one or two lines more or less. I don't see a big problem here,
it's a marginal use case, one I doubt even exists.
next prev parent reply other threads:[~2013-07-23 2:45 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
2013-07-22 20:36 ` Juanma Barranquero
2013-07-23 2:45 ` Eli Zaretskii [this message]
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=83y58yvvse.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).