From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.help Subject: RE: info-find-source Date: Fri, 19 Jan 2018 15:21:35 -0800 (PST) Message-ID: <8cdd767c-1b5b-4907-bc14-31848a196874@default> References: <86bmhyk2qy.fsf@zoho.com> <87mv1ia0et.fsf@robertthorpeconsulting.com> <86a7xhgnag.fsf@zoho.com> <86po6beoxh.fsf@zoho.com> <86h8rmdhie.fsf@zoho.com> <861sim4903.fsf@zoho.com> <87zi59616g.fsf@mbork.pl> <86vafx1og8.fsf@zoho.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1516404033 15907 195.159.176.226 (19 Jan 2018 23:20:33 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 19 Jan 2018 23:20:33 +0000 (UTC) To: Emanuel Berg , help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sat Jan 20 00:20:29 2018 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ecfxK-0003EE-Mz for geh-help-gnu-emacs@m.gmane.org; Sat, 20 Jan 2018 00:20:18 +0100 Original-Received: from localhost ([::1]:52731 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ecfzK-0000mH-U5 for geh-help-gnu-emacs@m.gmane.org; Fri, 19 Jan 2018 18:22:22 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38881) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ecfyn-0000jU-4g for help-gnu-emacs@gnu.org; Fri, 19 Jan 2018 18:21:51 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ecfyk-0003OA-31 for help-gnu-emacs@gnu.org; Fri, 19 Jan 2018 18:21:48 -0500 Original-Received: from userp2130.oracle.com ([156.151.31.86]:36324) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ecfyj-0003MG-P5 for help-gnu-emacs@gnu.org; Fri, 19 Jan 2018 18:21:45 -0500 Original-Received: from pps.filterd (userp2130.oracle.com [127.0.0.1]) by userp2130.oracle.com (8.16.0.22/8.16.0.22) with SMTP id w0JNGjRC063689; Fri, 19 Jan 2018 23:21:39 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=mime-version : message-id : date : from : sender : to : subject : references : in-reply-to : content-type : content-transfer-encoding; s=corp-2017-10-26; bh=H0UGpCTTJ9KHCzPbVkEXlFmqkNVNJRV6agromNsbiJA=; b=UGgRzy49kQWuGkHvs8t7+6onOXx2MBTwyhgaRkETJXdle/8NbWvFu+RYOsPJ+7yDz33+ VoT6YxlMmyawooSaypMn0hYjszj5SjZDoWZpyjHUMWCEJMgb9GGix1TTy+CJPtqp9YX/ ZwcOM/QldiyzfUK6rp3bM0uFlfLNrkX5jvcCWXZawlm3FkOdeYyhx+AolIVunq0jd8va ZP9+OfGkxUgFBuwT5uSZmGzTDoGx6GMeFtuEwDtnvzoGIjNl7IwFla166gNfBzrZch1A GksHqitQK0he+5600+wZxkCxbPJkoiPptKopB4a+zujYtTDAYgg8Qe+qm7KvP0l3CiNi yA== Original-Received: from aserv0021.oracle.com (aserv0021.oracle.com [141.146.126.233]) by userp2130.oracle.com with ESMTP id 2fkrbjgcm1-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 19 Jan 2018 23:21:39 +0000 Original-Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by aserv0021.oracle.com (8.14.4/8.14.4) with ESMTP id w0JNLcZc031023 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Fri, 19 Jan 2018 23:21:38 GMT Original-Received: from abhmp0016.oracle.com (abhmp0016.oracle.com [141.146.116.22]) by aserv0121.oracle.com (8.14.4/8.13.8) with ESMTP id w0JNLatT012992; Fri, 19 Jan 2018 23:21:38 GMT In-Reply-To: <86vafx1og8.fsf@zoho.com> X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9.1 (1003210) [OL 16.0.4627.0 (x86)] X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=8779 signatures=668654 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=4 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=879 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1801190299 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [generic] [fuzzy] X-Received-From: 156.151.31.86 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:115798 Archived-At: > > This function is obsolete since 24.4; editing > > Info nodes by hand is not recommended. >=20 > I've seen this as well and wondered what it > meant... "By hand" - is the recommended way > having a bunch of text files and have that > compiled, or should one generate the > documentation straight from Elisp, including > docstrings and/or comments? AFAIK, the "recommended" way is to build Info files using `makeinfo' with TexInfo source files. But I'm no expert on that. > Also, when you could edit Info nodes that way, > where did those edits go? You can still edit Info nodes that way. As I said, command `Info-edit' still exists, and it still works. Try it. You are asked to confirm whether you really want to do it. After you make your changes, by editing normally, you use `C-c C-c' and enter the name of the Info file you want to write. If you give the name of the current file (see variable `Info-current-file', for instance) then you are asked to confirm overwriting it. If you instead give the name of a new file then you create a new Info file. In either case you provide an absolute file name, so that's "where" your edits go. > Using the useful and > sensible program that was the initial topic of > this thread, we find out that for example Gnus' > is here /usr/share/info/emacs-24/gnus.info > while SLIME is here: > ~/.emacs.d/elpa/slime-20170921.1000/slime.info > so while the SLIME's manual could be annotated > without any hazard, how will this be done with > Gnus' without sudo right and without the > changes/annotations being threatened > by updates? If you change that slime.info file and then you download the SLIME again to the same disk location then that will overwrite your edits. And yes, if you want to change that gnus.info file then you need the necessary permissions write to that location. Nothing new here. But you can have Info files wherever you want. See option `Info-additional-directory-list', and variables `Info-directory-list', and `Info-default-directory-list'. And see env var `INFOPATH'. To be clear, I'm not encouraging anyone to edit Info files. I'm just mentioning that you can.