From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.bugs Subject: bug#25357: 25.1; Doc for `cursor-sensor-mode' (and modes generally) Date: Wed, 4 Jan 2017 20:29:08 -0800 (PST) Message-ID: <678f8299-e6e8-4b08-a412-bf367194f6d7@default> References: <9ad8b225-73da-4533-a676-b0f8e84e54ca@default> <878tqq5fw2.fsf@users.sourceforge.net> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1483590622 7562 195.159.176.226 (5 Jan 2017 04:30:22 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 5 Jan 2017 04:30:22 +0000 (UTC) Cc: 25357@debbugs.gnu.org To: npostavs@users.sourceforge.net Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Jan 05 05:30:17 2017 Return-path: Envelope-to: geb-bug-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 1cOzgm-0000Cn-1R for geb-bug-gnu-emacs@m.gmane.org; Thu, 05 Jan 2017 05:30:08 +0100 Original-Received: from localhost ([::1]:43605 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cOzgq-0000WD-3d for geb-bug-gnu-emacs@m.gmane.org; Wed, 04 Jan 2017 23:30:12 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:34604) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cOzgk-0000Ur-JS for bug-gnu-emacs@gnu.org; Wed, 04 Jan 2017 23:30:07 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cOzgh-0007kS-Dq for bug-gnu-emacs@gnu.org; Wed, 04 Jan 2017 23:30:06 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:54497) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cOzgh-0007kA-Ac for bug-gnu-emacs@gnu.org; Wed, 04 Jan 2017 23:30:03 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1cOzgh-0003or-4E for bug-gnu-emacs@gnu.org; Wed, 04 Jan 2017 23:30:03 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Drew Adams Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 05 Jan 2017 04:30:03 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 25357 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 25357-submit@debbugs.gnu.org id=B25357.148359056114596 (code B ref 25357); Thu, 05 Jan 2017 04:30:03 +0000 Original-Received: (at 25357) by debbugs.gnu.org; 5 Jan 2017 04:29:21 +0000 Original-Received: from localhost ([127.0.0.1]:41663 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cOzg0-0003nM-Pp for submit@debbugs.gnu.org; Wed, 04 Jan 2017 23:29:20 -0500 Original-Received: from aserp1040.oracle.com ([141.146.126.69]:27239) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cOzfz-0003n9-Gr for 25357@debbugs.gnu.org; Wed, 04 Jan 2017 23:29:20 -0500 Original-Received: from aserv0021.oracle.com (aserv0021.oracle.com [141.146.126.233]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id v054TB6S018019 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 5 Jan 2017 04:29:12 GMT Original-Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by aserv0021.oracle.com (8.13.8/8.14.4) with ESMTP id v054TBmD023724 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 5 Jan 2017 04:29:11 GMT Original-Received: from abhmp0018.oracle.com (abhmp0018.oracle.com [141.146.116.24]) by aserv0121.oracle.com (8.13.8/8.13.8) with ESMTP id v054T9KT001653; Thu, 5 Jan 2017 04:29:10 GMT In-Reply-To: <878tqq5fw2.fsf@users.sourceforge.net> X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9.1 (1003210) [OL 12.0.6753.5000 (x86)] X-Source-IP: aserv0021.oracle.com [141.146.126.233] X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:127774 Archived-At: > > I even think it would help to emphasize that "one" - not zero. > > IOW, you cannot turn off a major mode without turning on another one. >=20 > Sure, here's a patch to the manuals to clarify that. Thanks. Some minor comments. If they help, fine; if not, ignore. One not-so-minor comment, flagged by ** (in two places). --- The comma here should be a semicolon (or use two sentences); otherwise it is a comma splice: ``turn off'' a major mode, instead you must switch ; > I don't think explaining about the relationship between M-x and > Lisp functions again is needed though. ** How so, "again"? Here we are telling someone how to turn it on interactively. I think we should also tell them how to do it using Lisp. Or at least cross-reference some Elisp manual reference doc that tells you that you "turn on" a major mode by calling the function with no arguments. Examples where you add a major-mode function as a normal hook imply that (no args), but it would be good to spell it out once. Here, I would drop the apostrophe - not needed: definitions that customize Emacs' behavior Here, I would say for a particular kind of editing or interaction: used for editing a particular kind of text (Not all modes are for editing, in the usually understood sense.) Here, I would append "at a time". Each buffer has exactly one @dfn{major mode}. Otherwise it sounds like the mode-buffer association is fixed. For this: Major modes specialize Emacs for editing particular kinds of text. see above. We should not give the impression that a major mode is only for editing. `Info-mode' is not an editing mode (in the usual sense), for example. (Yes, I know that this particular text was already there.) This is OK, and I see that you put it in quotes (which is good): the only way to ``turn off'' a major mode is to switch to a different one. But it is different from what you said in the Emacs manual, where (I thought that) you specifically avoided any mention of turning a major mode on or off, and instead spoke about putting the buffer into the given mode. IOW, either we say that you CANNOT turn off (with quotes) a major mode, and INSTEAD of turning it off you switch the buffer to a different mode, or we say that THE WAY TO turn it off (with quotes) is to switch to a different mode. Those are different statements. Either is OK by me, but it might be better not to use both. ** Again, though, I think we should say explicitly somewhere (in the Elisp manual, as reference, and either linked to that or repeated in the Emacs manual) that you put a buffer into a major mode by invoking the mode function with no args. I repeat: feel free to ignore any of the above, and please make the changes you feel are best at this point. Thx.