From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "Jan D." Newsgroups: gmane.emacs.devel Subject: Re: DOC for Mac OS shown for Emacs compiled for X. Date: Fri, 29 Oct 2004 23:16:46 +0200 Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Message-ID: References: <20041029080140.SPWE44.mxfep02.bredband.com@coolsville.localdomain> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1099084701 1132 80.91.229.6 (29 Oct 2004 21:18:21 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 29 Oct 2004 21:18:21 +0000 (UTC) Cc: Andreas Schwab , emacs devel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Oct 29 23:18:07 2004 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1CNe8N-0001DB-00 for ; Fri, 29 Oct 2004 23:18:07 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CNeGE-000694-KW for ged-emacs-devel@m.gmane.org; Fri, 29 Oct 2004 17:26:14 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CNeG0-000673-5i for emacs-devel@gnu.org; Fri, 29 Oct 2004 17:26:00 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CNeFz-00066V-4l for emacs-devel@gnu.org; Fri, 29 Oct 2004 17:25:59 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CNeFz-00066S-17 for emacs-devel@gnu.org; Fri, 29 Oct 2004 17:25:59 -0400 Original-Received: from [195.54.107.73] (helo=mxfep02.bredband.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CNe83-0000cc-G0 for emacs-devel@gnu.org; Fri, 29 Oct 2004 17:17:47 -0400 Original-Received: from coolsville.localdomain ([83.226.180.220] [83.226.180.220]) by mxfep02.bredband.com with ESMTP id <20041029211746.YPIK44.mxfep02.bredband.com@coolsville.localdomain>; Fri, 29 Oct 2004 23:17:46 +0200 In-Reply-To: Original-To: Stefan X-Mailer: Apple Mail (2.619) 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: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:29150 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:29150 >> Is the approach in the attached patch OK? I generate a list with the >> objects used to build Emacs and in Snarf-documentation I compare the >> files >> in DOC with that list. If not in that list, those sections in DOC >> are skipped. > > I think instead that the docstring should be the same no matter what > system > I'm running on. If the behavior is not quite the same, either the > docstring > should be general enough to describe the common part, or it should > include > a discussion of the possible differences on various platforms. > > This way I can write code on GNU/Linux and be warned if I'm using > things > that might work differently on some other system. That is also possible, and seems to be what the previous discussion indicated. More work though. And it does not solve the error that doing C-h f x-server-vendor and clicking on the "C source code" link gives xfns.c when it should give macfns.c. I think a list of what files where used in the link is the only way to solve this. For a build on Mac OSX xfns.c or macfns.c could be used, depending on if it was an X build or Carbon build. Jan D.