From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Andrea Corallo Newsgroups: gmane.emacs.devel Subject: Re: Inferred function types in the *Help* buffer Date: Thu, 01 Jun 2023 07:50:13 -0400 Message-ID: References: <83o7manh0e.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23598"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: Andrea Corallo , Eli Zaretskii , emacs-devel To: Mattias =?utf-8?Q?Engdeg=C3=A5rd?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Jun 01 13:51:30 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 1q4gq0-0005yv-Or for ged-emacs-devel@m.gmane-mx.org; Thu, 01 Jun 2023 13:51:28 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1q4gp2-0005Az-V5; Thu, 01 Jun 2023 07:50:28 -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 1q4gp1-0005Ab-0k for emacs-devel@gnu.org; Thu, 01 Jun 2023 07:50:27 -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 1q4goy-0008K3-CA; Thu, 01 Jun 2023 07:50:25 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-Version:Date:References:In-Reply-To:Subject:To: From; bh=C6a2QTw0oapQ87KxWxCD/YbCX+DMHgEE7dioFzCXrU0=; b=THr+AxgISYW0lgDCMuw4 VAlhcH1SVcq0j0LGdGEBlVSZwU4y5NfqydZSZZ0G67gxPE42Opb86/PTP1zRmwKAwEhJaDthifmz4 lFcx4t5+Ww2DNwoeDhMHoujkV1y/CS3ykp3oTD9RktjtiTrO1ZJcwhfdltO8lQoRd3T+zwr4+GQpN W6OXYbiwLlRwE82e1MCJ6eE9ZQpgaB93f4ADugRGPBKAjeMBwp3y5e4DkmeeqvsLKezvF8jWcYBir FBxq29rhU8g+PKgZA9FHhaTqFe/5+ryraSnjYWmUhefsnvF1XQhdldHhNNLp/S8TZAkipGsApidaX oZ76KN5wzFrAVQ==; Original-Received: from acorallo by fencepost.gnu.org with local (Exim 4.90_1) (envelope-from ) id 1q4gon-00034Y-D5; Thu, 01 Jun 2023 07:50:23 -0400 In-Reply-To: ("Mattias =?utf-8?Q?Engdeg=C3=A5rd=22's?= message of "Thu, 1 Jun 2023 13:28:43 +0200") 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:306510 Archived-At: Mattias Engdeg=C3=A5rd writes: > 31 maj 2023 kl. 14.19 skrev Andrea Corallo : > >>> The main reason why I'd like to move them out is not to require the load >>> of comp.el for a simple C-h f. Secondary yeah I think that if it's in >>> use outside the compilation functionality should just not live there. >>=20 >> Thinking about more I can't see why we should force people to load >> comp.el for a simple C-h f. If this data is consumed by both comp.el >> and help-fns.el it should stay in a commonly available place. > > Let's use a separate file for the data then, rather than > subr-x.el. That also keeps down the size of subr-x.el which is used > very widely in practice. If the information is moved into function > declarations then that new file will just go away. > > Another concern is whether this information is useful to display in > the help in the first place. The documentation should be > authoritative; if the symbolic type is in conflict, actually or > seemingly, the user will be confused. Hi Mattias, I'm not sure I understand this argument, if something will prove not to be correct we'll just fix it as we do for everything else. I don't think sweeping something under the carpet will help us on the long term anyway, I rather prefer exposing things and having a feedback in case something is not optimal. Best Regards Andrea