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: Thu, 08 Oct 2020 14:22:01 +0000 Message-ID: References: <20200926163008.GS1349@protected.rcdrun.com> 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="32085"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Alpine 2.22 (NEB 394 2020-01-19) Cc: =?ISO-8859-15?Q?Jo=E3o_T=E1vora?= , bobnewell@bobnewell.net, emacs-devel@gnu.org To: Richard Stallman Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Oct 08 16:22:50 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 1kQWoj-0008CI-RJ for ged-emacs-devel@m.gmane-mx.org; Thu, 08 Oct 2020 16:22:49 +0200 Original-Received: from localhost ([::1]:39672 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kQWoi-0003FH-UY for ged-emacs-devel@m.gmane-mx.org; Thu, 08 Oct 2020 10:22:48 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37416) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kQWoF-0002oh-Tj for emacs-devel@gnu.org; Thu, 08 Oct 2020 10:22:19 -0400 Original-Received: from mx.sdf.org ([205.166.94.24]:51692) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kQWoD-0005KZ-QX; Thu, 08 Oct 2020 10:22:19 -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 098EM434027662 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Thu, 8 Oct 2020 14:22:05 GMT Original-Received: (from ghe@localhost) by sdf.org (8.15.2/8.12.8/Submit) id 098EM4Ys013484; Thu, 8 Oct 2020 14:22:04 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/08 10:22:09 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:257208 Archived-At: >> I also didn't read the manual very often, because I didn't find it >> easily. > > Can you suggest a way to make that easier for others in the future? > My suggestion would be to add links in the docstrings to the relevant chapter in the Emacs and Emacs Lisp manuals. Three examples: kill-line would have a link to (info "(emacs)Killing") kill-buffer would have two links, one to (info "(emacs)Buffers") and another to (info "(elisp)Buffers") call-process would have a link to (info "(elisp)Processes") I think a link to the relevant chapter, as in the examples above, is better than a link to the relevant section or subsection. With this, users who follow that link would find more information about the general context of the command or function, and not just a similar documentation.