From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.devel Subject: Re: x-display-pixel-width/height inconsistency Date: Fri, 05 Jul 2013 09:44:36 +0200 Message-ID: <51D67964.2070604@gmx.at> References: <83haibdipo.fsf@gnu.org> <837gj7co0l.fsf@gnu.org> <8338tvcjlp.fsf@gnu.org> <83wqr7b3h6.fsf@gnu.org> <51D12678.5090806@gmx.at> <51D2ADAA.9000805@gmx.at> <51D2D180.6050002@gmx.at> <51D3EE69.9080808@gmx.at> <51D41CA2.8000206@gmx.at> <51D541B6.1000908@gmx.at> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1373010299 21063 80.91.229.3 (5 Jul 2013 07:44:59 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 5 Jul 2013 07:44:59 +0000 (UTC) Cc: YAMAMOTO Mitsuharu , Emacs developers To: Juanma Barranquero Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jul 05 09:44:59 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 1Uv0hP-00040F-IA for ged-emacs-devel@m.gmane.org; Fri, 05 Jul 2013 09:44:59 +0200 Original-Received: from localhost ([::1]:50129 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Uv0hP-0003kC-7q for ged-emacs-devel@m.gmane.org; Fri, 05 Jul 2013 03:44:59 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43306) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Uv0hF-0003cn-VP for emacs-devel@gnu.org; Fri, 05 Jul 2013 03:44:56 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Uv0hA-0007YV-UL for emacs-devel@gnu.org; Fri, 05 Jul 2013 03:44:49 -0400 Original-Received: from mout.gmx.net ([212.227.17.20]:56461) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Uv0hA-0007Xp-HI for emacs-devel@gnu.org; Fri, 05 Jul 2013 03:44:44 -0400 Original-Received: from [62.47.47.33] ([62.47.47.33]) by mail.gmx.com (mrgmx102) with ESMTPA (Nemesis) id 0Li1hG-1UPkbq3j8c-00n6NN; Fri, 05 Jul 2013 09:44:42 +0200 In-Reply-To: X-Provags-ID: V03:K0:JUb1LjSuaBRoIMgSxWAJLtUiPOsX9ohSGrMKq8MbhQKfbWilwCE cAqF2kVBDfBUt63VVVoAmsTKLj//d1dzcAgStxDTyoIt19+a04x7g3VEF4J/LUeVgUDKTu0 sRFrPtr6Ql5p/EeT9F7em5XBgYbdspXQ16EZhNQ80SM3o8IbhkwO3RcrLbVMM88NOC9T2cP Q7LaacwNaQWwI7vlPEMJg== X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] X-Received-From: 212.227.17.20 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:161561 Archived-At: > But, OTOH, it is entirely possible that the user is saving the desktop > with some frames only partially visible. If you have many, and some of > them are less used, you can set them aside so only a fraction of the > frame is shown, which makes them accessible without taking too much > screen space. Perfectly reasonable, yes. > So, IMO, the only thing that makes sense is to > move/resize a frame while restoring when that frame is entirely > outside the current viewing area. The Windows window manager does that automatically, IIRC. > Or, perhaps, when the caption is > (because in many/most/all? window managers, you can mouse-drag a > window only from its caption). > > Of course, there's no way to know the caption height (in pixels) from > inside Emacs, I think, so in the end it's all an ugly heuristics: the > top of the frame is some arbitrary number of pixels inside the viewing > area. Or is there a better way? I think that once users have the workarea from Yamamoto's function, they can easily adjust frame positions and sizes in a hook. So I wouldn't care about this problem from the POV of `desktop-read' any more. Let's see whether this really could become an issue. martin