From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Inferred function types in the *Help* buffer Date: Wed, 31 May 2023 17:08:42 +0300 Message-ID: <83wn0oegph.fsf@gnu.org> References: <83o7manh0e.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="20624"; mail-complaints-to="usenet@ciao.gmane.io" Cc: mattias.engdegard@gmail.com, akrl@sdf.org, emacs-devel@gnu.org To: Andrea Corallo Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed May 31 16:08:53 2023 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 1q4MVQ-00057f-R2 for ged-emacs-devel@m.gmane-mx.org; Wed, 31 May 2023 16:08:52 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1q4MUf-0002WW-TQ; Wed, 31 May 2023 10:08:05 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1q4MUe-0002VR-Eo for emacs-devel@gnu.org; Wed, 31 May 2023 10:08:04 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1q4MUc-0007VE-Q1; Wed, 31 May 2023 10:08:03 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=rflIkSmfdBixTHhK9elGQ3pH7dQAYyd7cIJ04UntRgA=; b=ONCC5rkA1FRf sHeTcGqpRiBourMEMmiTHLDyoYc1X0j9JbS4YHKni1TtAmsQ2hZKGilmClOOa4XAG6QytGYX5HQX3 uFXWCCtfyJBgsgCCJGGxuDngrtk3E8AzXNxBgfilUgFOfPioKNS83FzKhwEnK8278tD/tvvSvlPVj ME2Zg6xUxCthJMMdz1hc4HdSIUiz6mWZ1fwWBH4DJfE1tyk2dGKxl2EVTBpl5cfkTkECPRDeNh8oo d1y2sf3czOG6JsIXFSKnXAsJMRsG45ytb/SDJREMEQwEPunwooWI04k5kLvldCawKiGl7wlV0cXll hm3sqJldA7YiUNcwiBn/0g==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1q4MUa-0004M6-5W; Wed, 31 May 2023 10:08:00 -0400 In-Reply-To: (message from Andrea Corallo on Wed, 31 May 2023 08:19:31 -0400) 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:306446 Archived-At: > From: Andrea Corallo > Cc: Andrea Corallo , Eli Zaretskii , > emacs-devel > Date: Wed, 31 May 2023 08:19:31 -0400 > > Thinking about more I can't see why we should force people to load > comp.el for a simple C-h f. It happens more often than not anyway, because Help functions frequently load packages to access documentation and other information, and loading a package native-compiles it. I wouldn't worry about loading comp.el too much. > Moreover this functionality would be available to non native compiled > Emacsen as well, so forcing the load of comp.el feels to me even more > odd. When this is available to non-NATIVE_COMP builds, it would maybe make sense to split it in two, and have each part stored in a relevant file, no?