From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ralf Angeli Newsgroups: gmane.emacs.devel Subject: Re: display-mm-width return value off on Windows Date: Sun, 16 Jul 2006 00:06:18 +0200 Message-ID: <8764hycylh.fsf@neutrino.caeruleus.net> References: <87slldpd8s.fsf@neutrino.caeruleus.net> <44AFB1E1.20906@student.lu.se> <8764i7kywu.fsf@neutrino.caeruleus.net> <874pxls3bu.fsf@neutrino.caeruleus.net> <85k66hjmy4.fsf@lola.goethe.zz> <85veq0c9zi.fsf@lola.goethe.zz> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1153001201 30778 80.91.229.2 (15 Jul 2006 22:06:41 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 15 Jul 2006 22:06:41 +0000 (UTC) Cc: rms@gnu.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jul 16 00:06:38 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1G1sHT-0003nr-Qv for ged-emacs-devel@m.gmane.org; Sun, 16 Jul 2006 00:06:36 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G1sHT-0001tL-Bv for ged-emacs-devel@m.gmane.org; Sat, 15 Jul 2006 18:06:35 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1G1sHJ-0001tF-DO for emacs-devel@gnu.org; Sat, 15 Jul 2006 18:06:25 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1G1sHH-0001t3-7U for emacs-devel@gnu.org; Sat, 15 Jul 2006 18:06:24 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G1sHH-0001t0-4B for emacs-devel@gnu.org; Sat, 15 Jul 2006 18:06:23 -0400 Original-Received: from [212.227.126.188] (helo=moutng.kundenserver.de) by monty-python.gnu.org with esmtp (Exim 4.52) id 1G1sJY-0002q9-Cv; Sat, 15 Jul 2006 18:08:44 -0400 Original-Received: from [84.165.29.143] (helo=neutrino.caeruleus.net) by mrelayeu.kundenserver.de (node=mrelayeu6) with ESMTP (Nemesis), id 0ML29c-1G1sHD1uYR-0005h5; Sun, 16 Jul 2006 00:06:20 +0200 Original-To: Stefan Monnier In-Reply-To: (Stefan Monnier's message of "Fri, 14 Jul 2006 17:37:30 -0400") X-Provags-ID: kundenserver.de abuse@kundenserver.de login:abf9ffac21f8345504ac40c53d3b40ba X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:57062 Archived-At: * Stefan Monnier (2006-07-14) writes: >>>> Would that not be a case for a terminal-local variable? >>> >>> It sounds attractive (the idea of adding a frame-local parameter for it >>> doesn't seem too appealing since it implies the possibility of returning >>> different results for different frames of the same display). >>> >>> Tho I'm not sure what would happen with multi-head configs. > >> Doesn't multi-head imply multi-display for Emacs? > > It probably depends on the setup (I guess most recent multihead configs use > Xinerama so Emacs should be completely oblivious, but in other cases it may > be separate displays but with a single keyboard, now whether that means > a single (Emacs) terminal or not, I don't know). The info node pointed out by David says it does: ,----[ (info "(elisp)Multiple Displays") ] | A single X server can handle more than one screen. A display name | `HOST:SERVER.SCREEN' has three parts; the last part specifies the | screen number for a given server. When you use two screens belonging | to one server, Emacs knows by the similarity in their names that they | share a single keyboard, and it treats them as a single terminal. `---- So one rather needs screen-dependent or display-dependent values for screen width and height. (Obviously.) A pragmatic way for specifying this would be an alist with (DISPLAY . LENGTH) elements as suggested by Kim (assuming display is equivalent to screen). -- Ralf