From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#18636: 24.4.50; doc of `display-monitor-attributes-list' - DISPLAY? FRAME? Date: Wed, 08 Oct 2014 17:10:31 +0300 Message-ID: <8338ayk5yg.fsf@gnu.org> References: Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1412777484 16066 80.91.229.3 (8 Oct 2014 14:11:24 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 8 Oct 2014 14:11:24 +0000 (UTC) Cc: 18636@debbugs.gnu.org To: Drew Adams Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Oct 08 16:11:17 2014 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 1XbrxV-0007T4-2Z for geb-bug-gnu-emacs@m.gmane.org; Wed, 08 Oct 2014 16:11:17 +0200 Original-Received: from localhost ([::1]:36427 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XbrxU-0008Hl-FM for geb-bug-gnu-emacs@m.gmane.org; Wed, 08 Oct 2014 10:11:16 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40591) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XbrxM-0008B9-5v for bug-gnu-emacs@gnu.org; Wed, 08 Oct 2014 10:11:13 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XbrxG-0004Vw-Np for bug-gnu-emacs@gnu.org; Wed, 08 Oct 2014 10:11:08 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:46591) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XbrxG-0004Vp-KV for bug-gnu-emacs@gnu.org; Wed, 08 Oct 2014 10:11:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1XbrxG-0008UZ-8T for bug-gnu-emacs@gnu.org; Wed, 08 Oct 2014 10:11:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 08 Oct 2014 14:11:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 18636 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 18636-submit@debbugs.gnu.org id=B18636.141277742332592 (code B ref 18636); Wed, 08 Oct 2014 14:11:02 +0000 Original-Received: (at 18636) by debbugs.gnu.org; 8 Oct 2014 14:10:23 +0000 Original-Received: from localhost ([127.0.0.1]:38155 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1Xbrwc-0008Ta-Ig for submit@debbugs.gnu.org; Wed, 08 Oct 2014 10:10:23 -0400 Original-Received: from mtaout23.012.net.il ([80.179.55.175]:36874) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1XbrwZ-0008TR-FG for 18636@debbugs.gnu.org; Wed, 08 Oct 2014 10:10:20 -0400 Original-Received: from conversion-daemon.a-mtaout23.012.net.il by a-mtaout23.012.net.il (HyperSendmail v2007.08) id <0ND400600PGE4P00@a-mtaout23.012.net.il> for 18636@debbugs.gnu.org; Wed, 08 Oct 2014 17:10:17 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout23.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0ND4005XWQ15UX70@a-mtaout23.012.net.il>; Wed, 08 Oct 2014 17:10:17 +0300 (IDT) In-reply-to: X-012-Sender: halo1@inter.net.il 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: 140.186.70.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:94301 > Date: Wed, 8 Oct 2014 07:04:51 -0700 (PDT) > From: Drew Adams > Cc: 18636@debbugs.gnu.org > > > IOW, what other details are required to correctly invoke and use > > these functions? > > Dunno what other details are needed to understand these functions. > That was the point. > > I'm not looking for implementation details. I'm guessing that a > description of the function, and a good understanding of it, involves > some description/understanding of the argument and what it means > to the function. What the function needs it for - not in terms of > just what it does with it, but in logical terms - why it is required. > > Maybe no more info is needed - dunno. But usually a user can tell > why a given argument might have a value of different types, e.g. a > buffer or a string that names a buffer. The connection here, between > a frame arg value and a display arg value, is not obvious. I was > guessing that what the function needs, ultimately, is a display, and > that if given a frame it uses the frame's display. But apparently > that is not the connection. > > I'm in the dark on this. Use your own judgment. If you think > nothing is unclear or missing, that's good enough for me. In my judgment, nothing else is needed. Most functions just need the type of the frames on display, which can be gleaned from any of the possible argument types. The other need the screen used by the display, which again can be gotten from any argument type. IOW, these arguments serve as proxies to the information needed by the functions.