unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: martin rudalics <rudalics@gmx.at>,
	Emacs developers <emacs-devel@gnu.org>
Subject: Re: frame size&position woes
Date: Wed, 24 Jul 2013 12:42:49 +0200	[thread overview]
Message-ID: <CAAeL0SSB7okJ69XBxqk36RHfBX24nAp=DoZEbVVrMMHP=+MXug@mail.gmail.com> (raw)
In-Reply-To: <83ppu8wr1d.fsf@gnu.org>

On Wed, Jul 24, 2013 at 5:55 AM, Eli Zaretskii <eliz@gnu.org> wrote:

> You should be able to approximate that by multiplying the
> character-unit dimensions by the pixel size of the default face's
> font.

Yes. That's what I called "crude heuristics".

> The result might be a few pixels off, but I don't see that as a
> grave problem, at least not until we have better facilities.

Let's assume there's a new option
`desktop-restore-frames-move-onscreen'. If the user sets it to t, and
I move back a frame that was really visible, but just by a few pixels,
that's a tiny failure. But if I don't move back a frame that is a few
pixels off, and so, harder to access for the user without UI tricks or
M-: (modify-frame-parameters ...), that's a worse problem (not earth
shattering, but definitely not very user-friendly). Which means that,
to be safe, the heuristics must include a small constant factor to err
on the safe side. Crude. So yes, I'll do it, but certainly not having
a get-frame-window-system-metrics pains me.

> It's good enough for me, because currently I have to restore my frames
> manually every time I quit and restart Emacs for some reason.

Uh? Have you filed a bug report about it?

    J



  reply	other threads:[~2013-07-24 10:42 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
2013-07-23 23:47               ` Juanma Barranquero
2013-07-24  3:55                 ` Eli Zaretskii
2013-07-24 10:42                   ` Juanma Barranquero [this message]
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='CAAeL0SSB7okJ69XBxqk36RHfBX24nAp=DoZEbVVrMMHP=+MXug@mail.gmail.com' \
    --to=lekktu@gmail.com \
    --cc=eliz@gnu.org \
    --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).