From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.devel Subject: RE: Exposing Isearch toggleable options Date: Thu, 29 Oct 2015 10:19:27 -0700 (PDT) Message-ID: <9d79a7aa-e2bd-49fb-b7ab-3cfa6a94a255@default> References: < > <<8337wt3axe.fsf@gnu.org>> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1446139199 6138 80.91.229.3 (29 Oct 2015 17:19:59 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 29 Oct 2015 17:19:59 +0000 (UTC) Cc: bruce.connor.am@gmail.com, emacs-devel@gnu.org To: Eli Zaretskii , John Wiegley Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Oct 29 18:19:44 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZrqrW-0003fq-Dy for ged-emacs-devel@m.gmane.org; Thu, 29 Oct 2015 18:19:42 +0100 Original-Received: from localhost ([::1]:45471 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZrqrW-0007rx-2g for ged-emacs-devel@m.gmane.org; Thu, 29 Oct 2015 13:19:42 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46574) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZrqrR-0007pa-DC for emacs-devel@gnu.org; Thu, 29 Oct 2015 13:19:38 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZrqrQ-0005UB-HT for emacs-devel@gnu.org; Thu, 29 Oct 2015 13:19:37 -0400 Original-Received: from aserp1040.oracle.com ([141.146.126.69]:43362) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZrqrL-0005Qr-Q2; Thu, 29 Oct 2015 13:19:31 -0400 Original-Received: from aserv0022.oracle.com (aserv0022.oracle.com [141.146.126.234]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id t9THJSm9030935 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 29 Oct 2015 17:19:28 GMT Original-Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by aserv0022.oracle.com (8.13.8/8.13.8) with ESMTP id t9THJSew018645 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 29 Oct 2015 17:19:28 GMT Original-Received: from abhmp0004.oracle.com (abhmp0004.oracle.com [141.146.116.10]) by aserv0121.oracle.com (8.13.8/8.13.8) with ESMTP id t9THJSow032305; Thu, 29 Oct 2015 17:19:28 GMT In-Reply-To: <<8337wt3axe.fsf@gnu.org>> X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9 (901082) [OL 12.0.6691.5000 (x86)] X-Source-IP: aserv0022.oracle.com [141.146.126.234] X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] X-Received-From: 141.146.126.69 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:192916 Archived-At: > > Artur, does this mean the I-search prompt would be two-lines high in th= e > > minibuffer, instead of one-line? If so, I would definitely want a way t= o > > disable it; if I already know the options, it shortens the text window = for > > documentation I wouldn't need. >=20 > How about showing that on the mode line, like we do for eldoc-mode? There are many Isearch bindings, some of which are (far) more important than toggles. Why promote these particular bindings in this way? Why not encourage users to consult the Isearch help? And have that help explicitly describe the available toggles, as well as the most important keys. And have that help list _all_ of the Isearch key bindings, at the end. And provide that help on a quick Isearch key (e.g. `C-h'). It is misguided, IMHO, to privilege this kind of thing, either at Isearch startup (a message) or in the mode line. Messages should be used for changes of state. Mode-line indications should be used for the current state.