From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Not using DOC for ELisp files Date: Tue, 28 Dec 2021 12:14:43 -0500 Message-ID: References: <834k6snbko.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="18009"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Dec 28 18:15:54 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n2G4n-0004TY-IZ for ged-emacs-devel@m.gmane-mx.org; Tue, 28 Dec 2021 18:15:53 +0100 Original-Received: from localhost ([::1]:50166 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n2G4l-0007rn-Hw for ged-emacs-devel@m.gmane-mx.org; Tue, 28 Dec 2021 12:15:51 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:50032) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n2G3m-0007An-Vb for emacs-devel@gnu.org; Tue, 28 Dec 2021 12:14:51 -0500 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:1236) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n2G3k-0002P9-EE; Tue, 28 Dec 2021 12:14:50 -0500 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 77167442A1F; Tue, 28 Dec 2021 12:14:46 -0500 (EST) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 2A61B442A1C; Tue, 28 Dec 2021 12:14:45 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1640711685; bh=VKfqf+N5Fbb5nTk9VVQwBQFGXe7ayBv4zIkZrJgWLog=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=RLXTqMOe2E6WzW59aYQB+RFFpMZkJljat5o//6g0E5iA6fmd2XSVoQt/k6BrRTiHz s6vNCfwXpkHEpPk0rAb9e2b+pj7TRgdySreB1EC91BOraujLenyTVMag0/TP9x5KOv 7HanobN7y9OD+JLF5ztRmZ6D6d1KOLqiRlQYGYOkS3Cu1aNYpFNja3VuBz3ufd1HL9 TV1Y3UfG8FIrVaUEQfVuhRvXm135FPvpP9VfCIe3QREx4ucJXirpGls+6W8Q6WdCav orbu0YQW/rianE/WfDVd952RcmOPMr9jwhdZnNxH/iAP7W59cboLOoPLyStYkWZeAs MjQpFO3zEvmJQ== Original-Received: from pastel (unknown [216.154.30.173]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id F224D1201D8; Tue, 28 Dec 2021 12:14:44 -0500 (EST) In-Reply-To: <834k6snbko.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 28 Dec 2021 14:44:23 +0200") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:283515 Archived-At: >> The patch below removes from the DOC file the docstrings coming from >> ELisp files. > What does this mean in terms of the run-time requirements in order to > get the doc strings for preloaded files? Does it mean their *.elc > files should be available from the installation tree? Yes, it means the docstring are fetched from the likes of `lisp/files.elc` (as is already the case for the non-preloaded files) instead of from `etc/DOC`. > Or does it mean the *.el files (which might be compressed) must > be available? No, the `.el` files are not used any more than before. > And what does this mean for a natively-compiled installation? I don't think this has any impact. > If there are any non-trivial consequences of this change, i.e. distros > will now need to make sure something happens that they didn't before, > I think we should get their opinions before we install this. The only non-trivial consequence I can think of is when the compiled preloaded files are missing. E.g. if the distros remove `lisp/files.elc`. I don't aware of any distro/packaging doing it (even tho it did make sense doing so to save a few bytes). Stefan