From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gregory Heytings via "Emacs development discussions." Newsgroups: gmane.emacs.devel Subject: Re: How to make Emacs popular again. Date: Fri, 09 Oct 2020 07:38:00 +0000 Message-ID: References: <20200926163008.GS1349@protected.rcdrun.com> <83blhc7f4x.fsf@gnu.org> Reply-To: Gregory Heytings Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="13971"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Alpine 2.22 (NEB 394 2020-01-19) Cc: Eli Zaretskii , =?ISO-8859-15?Q?Daniel_Mart=EDn?= , bobnewell@bobnewell.net, rms@gnu.org, rpluim@gmail.com, emacs-devel@gnu.org, joaotavora@gmail.com To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Oct 09 09:39:55 2020 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 1kQn0N-0003YJ-PH for ged-emacs-devel@m.gmane-mx.org; Fri, 09 Oct 2020 09:39:55 +0200 Original-Received: from localhost ([::1]:39540 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kQn0M-0002dA-SC for ged-emacs-devel@m.gmane-mx.org; Fri, 09 Oct 2020 03:39:54 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37742) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kQmyn-0001ml-Ja for emacs-devel@gnu.org; Fri, 09 Oct 2020 03:38:18 -0400 Original-Received: from mx.sdf.org ([205.166.94.24]:63225) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kQmyj-0007SY-RC; Fri, 09 Oct 2020 03:38:16 -0400 Original-Received: from sdf.org (IDENT:ghe@otaku.sdf.org [205.166.94.8]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id 0997c4jp023845 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Fri, 9 Oct 2020 07:38:04 GMT Original-Received: (from ghe@localhost) by sdf.org (8.15.2/8.12.8/Submit) id 0997cPP3028832; Fri, 9 Oct 2020 07:38:25 GMT In-Reply-To: Received-SPF: pass client-ip=205.166.94.24; envelope-from=ghe@sdf.org; helo=mx.sdf.org X-detected-operating-system: by eggs.gnu.org: First seen = 2020/10/09 03:38:11 X-ACL-Warn: Detected OS = ??? X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-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.23 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:257254 Archived-At: >>> We could add a "View in Manual" button in Help buffers if info-lookup >>> says that the symbol is in the Emacs Lisp Info index. > > Yes, it should be fairly easy to do using the > `help-fns-describe-*-functions` hooks. > >> For interactive functions (a.k.a. "commands"), there's an ambiguity >> here: should the link lead to the Emacs user manual or to the Emacs >> Lisp Reference manual? We could show both, but that could confuse >> users (as opposed to Lisp programmers). > > I think something like: > > Also documented in the >Emacs user's manual<. > Also documented in the >ELisp programmer's reference<. > > should be clear enough (where >...< is meant to delimit the hyperlink). > Perhaps it would be even clearer as follows (again with the example of kill-buffer): See also `(emacs) Buffers'. For programmers, see also `(elisp) Buffers'.