From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Keith David Bershatsky Newsgroups: gmane.emacs.bugs Subject: bug#21415: 25.0.50; Emacs Trunk -- pixelwise width/height for x-create-frame Date: Fri, 04 Sep 2015 17:31:24 -0700 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 (generated by - "") Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1441413146 26825 80.91.229.3 (5 Sep 2015 00:32:26 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 5 Sep 2015 00:32:26 +0000 (UTC) Cc: 21415@debbugs.gnu.org To: martin rudalics Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sat Sep 05 02:32:15 2015 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1ZY1Ot-0002kz-6P for geb-bug-gnu-emacs@m.gmane.org; Sat, 05 Sep 2015 02:32:11 +0200 Original-Received: from localhost ([::1]:36187 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZY1Os-0000Qv-Tj for geb-bug-gnu-emacs@m.gmane.org; Fri, 04 Sep 2015 20:32:10 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39518) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZY1On-0000NJ-Or for bug-gnu-emacs@gnu.org; Fri, 04 Sep 2015 20:32:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZY1Ok-0002IU-GL for bug-gnu-emacs@gnu.org; Fri, 04 Sep 2015 20:32:05 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:56907) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZY1Ok-0002IN-Ai for bug-gnu-emacs@gnu.org; Fri, 04 Sep 2015 20:32:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1ZY1Oj-0008WF-Tk for bug-gnu-emacs@gnu.org; Fri, 04 Sep 2015 20:32:01 -0400 X-Loop: help-debbugs@gnu.org In-Reply-To: Resent-From: Keith David Bershatsky Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 05 Sep 2015 00:32:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 21415 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 21415-submit@debbugs.gnu.org id=B21415.144141309032704 (code B ref 21415); Sat, 05 Sep 2015 00:32:01 +0000 Original-Received: (at 21415) by debbugs.gnu.org; 5 Sep 2015 00:31:30 +0000 Original-Received: from localhost ([127.0.0.1]:49117 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1ZY1OD-0008VQ-RU for submit@debbugs.gnu.org; Fri, 04 Sep 2015 20:31:30 -0400 Original-Received: from cobb.liquidweb.com ([50.28.13.150]:56623) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1ZY1OA-0008VG-Mz for 21415@debbugs.gnu.org; Fri, 04 Sep 2015 20:31:27 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lawlist.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Subject:Cc:To:From:Message-ID:Date; bh=sNZzEiIO7YgBrMZR0rzmEoADzuNCcbk6AkJO6n4KFgw=; b=AoYXIz7DjiXW7u1+qUoJUIl6hdhOZDucStVQqd5v95Rj9FWzeQ3oYneys7rX2IJzrYwSAcGKeRHGJ81kljaVxQlk1VE3BD0f7thKzZGi+Ln7OB6CEes6zYa1deKl1cj7; Original-Received: from rrcs-74-62-211-60.west.biz.rr.com ([74.62.211.60]:49499 helo=MBA.local.localhost) by cobb.liquidweb.com with esmtp (Exim 4.82) (envelope-from ) id 1ZY1O7-0003F6-GG; Fri, 04 Sep 2015 20:31:23 -0400 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cobb.liquidweb.com X-AntiAbuse: Original Domain - debbugs.gnu.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - lawlist.com X-Get-Message-Sender-Via: cobb.liquidweb.com: acl_c_relayhosts_text_entry: lawlist|lawlist.com X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:106160 Archived-At: In my opinion, it would be useful to set the frame specifications exactly at the time of creation -- rather than fix it after the fact with `set-frame-size` using the pixelwise argument. My particular immediate use case is to simply fill the screen exactly (on OSX, XP, and Windows 7). In my testing, `toggle-frame-maximized` was never as accurate as `set-frame-size` using the pixelwise argument. I would imagine there are other situations where a user may wish to create a frame with exact specifications to fit precisely into a specific location on the screen, without the need to fix it after the fact. I have a test that identifies the current operating system and screen sizes on my different machines, and I have already determined exactly how many Emacs frame pixels fill the screen based on other factors such as font, fringe widths, no scroll bars, and no menu-bar. The general approach has been to take the initial frame or subsequently created frames and use `set-frame-size` with the pixelwise argument to blow it up to the preferred size. It sure would be nice, however, to set the pixel width/height along with the other frame parameters both programmatically (passing as parameters to `make-frame`), and as part of the `initial-frame-alist` and `default-frame-alist`. I would still use `set-frame-size` with the pixelwise argument for functions where contraction/expansion of frames is needed -- e.g., I have a custom reduce-all-frame-size function and a custom maximize-all-frame-size function. That is handy for me to see other programs without completely hiding Emacs, and then to restore it again to full size when I'm done with those other programs. I don't fully understand the floating point because the pixels are whole numbers, rather than decimals -- this is probably because I'm just a hobbyist, not a real programmer. But yes, a frame-parameter for pixel width and pixel height would be awesome. Last weekend, I learned how to build Emacs from any point in time based on a particular commit; and, I also learned the layman's way to download prebuilt nightlies from http://emacsformacosx.com/ I'd be happy to work on pinpointing when the intermittent flickering began, and will spend a little time on that project each day. ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; At Fri, 04 Sep 2015 21:17:51 +0200, martin rudalics wrote: > > > I am trying to do three things: > > > > (1) . . . > > Interesting. This is the first time someone asks for this. Do you have > a particular use case? > > > (2) . . . > > We'd need a ‘pixel-width' and a ‘pixel-height' frame parameter. When > any of these is present, it would be used instead of the ‘width' and > ‘height' parameters. Alternatively, we could interpret floating point > values of ‘width' and ‘height' specially. > > > (3) . . . > > Could you try bisecting to find out when this started?