From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Juanma Barranquero Newsgroups: gmane.emacs.devel Subject: Re: frame size&position woes Date: Wed, 24 Jul 2013 01:47:51 +0200 Message-ID: References: <51EBEA23.2000805@gmx.at> <51ECEBDB.8010203@gmx.at> <837ggiy4ko.fsf@gnu.org> <83y58yvvse.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: ger.gmane.org 1374623326 15923 80.91.229.3 (23 Jul 2013 23:48:46 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 23 Jul 2013 23:48:46 +0000 (UTC) Cc: martin rudalics , Emacs developers To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jul 24 01:48:45 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1V1mJr-0000uK-9p for ged-emacs-devel@m.gmane.org; Wed, 24 Jul 2013 01:48:39 +0200 Original-Received: from localhost ([::1]:53946 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V1mJq-0003sp-Eh for ged-emacs-devel@m.gmane.org; Tue, 23 Jul 2013 19:48:38 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:55947) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V1mJo-0003sk-4J for emacs-devel@gnu.org; Tue, 23 Jul 2013 19:48:37 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V1mJm-00051d-4o for emacs-devel@gnu.org; Tue, 23 Jul 2013 19:48:36 -0400 Original-Received: from mail-ee0-x234.google.com ([2a00:1450:4013:c00::234]:38993) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V1mJk-00050l-K8; Tue, 23 Jul 2013 19:48:32 -0400 Original-Received: by mail-ee0-f52.google.com with SMTP id c50so4936193eek.11 for ; Tue, 23 Jul 2013 16:48:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=3YxOTkim2wQD8cWLDO6994nDTdFBKDbKxDRerdw+w6A=; b=q1O8t6EwxO3g8wqYLs7v2Ka0Gh6kH+6/rvYmAphCn3PKgecZr8c6Ea6M1KLoZWWVoF 7OrBdnQVzyArRdVnBU7s3AHB7G91c0tg1gRqrJfZqarN+ItA/+o8RIJ0+Qvccv7GX2Qk 88/AzchvQaTRNaZVbHd2xpCcerYOb9wQl2dzwXAF3nEkGrpQ87dQdZ1enDYF6sFSmxy4 UZ9jkmeQy02JS/aBNgs8imBcOp+cFcAOtKM8ctc2lcXvAXqHckSSilhCKkJYaB4loLpv 4S5k5Kiccf6FZzDQPpweUBjesxwcOCrG1phDdzIjd0N+kFoUBM4N2l5AkHm6cvreyR5I rWCA== X-Received: by 10.14.4.70 with SMTP id 46mr34278240eei.42.1374623311716; Tue, 23 Jul 2013 16:48:31 -0700 (PDT) Original-Received: by 10.14.142.4 with HTTP; Tue, 23 Jul 2013 16:47:51 -0700 (PDT) In-Reply-To: <83y58yvvse.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4013:c00::234 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:162099 Archived-At: On Tue, Jul 23, 2013 at 4:45 AM, Eli Zaretskii wrote: > 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? This is not about restoring the frame size & position, is about knowing whether it intersects with some monitor. Some people want for desktop-restore-frames to move on-screen frames that are wholly off-screen. The only way to know the screen dimensions is via `frame-monitor-attributes', which answers in pixels. Without the real, window manager style physical size of a frame in pixels, all we can do is crude heuristics. > ...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. Which is a way to say, we won't jump through complex hoops to fix it. Fine. I'm trying all the simple ones first, because big or not, it's still a problem. Restoring "one or two lines more or less" is not a big failure, but it is also not a good result for code whose only purpose is to restore frames' sizes and positions.