From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Artur Malabarba Newsgroups: gmane.emacs.devel Subject: RE: Exposing Isearch toggleable options Date: Thu, 29 Oct 2015 10:10:31 +0000 Message-ID: References: <6d1f58d5-ccf1-46e7-b7fc-3466c0f3f3d5@default> Reply-To: bruce.connor.am@gmail.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=089e01228934631b7e05233b8531 X-Trace: ger.gmane.org 1446113447 19194 80.91.229.3 (29 Oct 2015 10:10:47 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 29 Oct 2015 10:10:47 +0000 (UTC) Cc: emacs-devel To: Drew Adams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Oct 29 11:10:43 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 1ZrkAN-0008Gz-An for ged-emacs-devel@m.gmane.org; Thu, 29 Oct 2015 11:10:43 +0100 Original-Received: from localhost ([::1]:43131 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZrkAM-0007Nx-Vv for ged-emacs-devel@m.gmane.org; Thu, 29 Oct 2015 06:10:43 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:47685) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZrkAD-0007No-Rv for emacs-devel@gnu.org; Thu, 29 Oct 2015 06:10:34 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZrkAC-0000pj-I3 for emacs-devel@gnu.org; Thu, 29 Oct 2015 06:10:33 -0400 Original-Received: from mail-lb0-x233.google.com ([2a00:1450:4010:c04::233]:35947) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZrkAC-0000pe-7Y for emacs-devel@gnu.org; Thu, 29 Oct 2015 06:10:32 -0400 Original-Received: by lbjm5 with SMTP id m5so24696179lbj.3 for ; Thu, 29 Oct 2015 03:10:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=bbKipAwp11jSv+rBaCN9gafqhxwNnwG5+ZgX8QDJYKM=; b=my+V/2WkeIn/szUiFQpa+/5l0Te5bPP1At07NHV31lIOtHeYagRwemanhwXJWf7Wig 3TUz//y6sQI41HjUzNYdXGif8QEy0aM1q+J5Lm9zxhOyYPm2KKEQM2hKHsBqHrCk8BJ6 v0TIUpJpY20n2pgxID1u85Q6YXaQqHyCG/Fi/LpgXRmUkOgFFrUeB/kQWWw3mzmmkfj1 cNVyGQ5MpR47fbwR+0r1XyUXy9kwpnSRXZEiIi5SvW+pL3X273McbDcJWYy8p2XzFscW bag2GlEtJpr1P3aPBDMIQfOL6lhwy4HmkSQJhhNq3DfA5f+O83sLCLWIrDw72ad4wTXF Svkg== X-Received: by 10.112.135.233 with SMTP id pv9mr511152lbb.42.1446113431458; Thu, 29 Oct 2015 03:10:31 -0700 (PDT) Original-Received: by 10.112.91.106 with HTTP; Thu, 29 Oct 2015 03:10:31 -0700 (PDT) Original-Received: by 10.112.91.106 with HTTP; Thu, 29 Oct 2015 03:10:31 -0700 (PDT) In-Reply-To: <6d1f58d5-ccf1-46e7-b7fc-3466c0f3f3d5@default> X-Google-Sender-Auth: mjqGh5FKATawFUGPbaoTybYxZVY X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4010:c04::233 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:192867 Archived-At: --089e01228934631b7e05233b8531 Content-Type: text/plain; charset=UTF-8 On 29 Oct 2015 1:19 am, "Drew Adams" wrote: > > > I'm not yet sure if this is worth merging to master, so I'd > > very much appreciate opinions. > > FWIW, I amnot in favor of it. I'd prefer that users consult > the Isearch help for such info. Ok, Thanks. > I have many more togglable options, and Emacs might in the > future also. FWIW, the options are not hardcoded. So a different set can be displayed. > And there are many aspects regarding the current Isearch state > that it would be worthwhile indicating to users (either on an > ongoing basis or on demand, depending on the aspect of state). > > The current value of a togglable variable, as well as the key > to toggle it, is info that falls in that category: it is part > of the current state. I'd sooner see this info handled along > with other state info. We've discussed this in other threads, > I believe. I agree with you partially. The information of which options are active or relevant is a state info. Bit the info of which key toggles them is of general use (and I'd like to expose it to users who don't read the manual). --089e01228934631b7e05233b8531 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On 29 Oct 2015 1:19 am, "Drew Adams" <drew.adams@oracle.com> wrote:
>
> > I'm not yet sure if this is worth merging to master, so I'= ;d
> > very much appreciate opinions.
>
> FWIW, I amnot in favor of it.=C2=A0 I'd prefer that users consult<= br> > the Isearch help for such info.

Ok, Thanks.

> I have many more togglable options, and Emacs might in = the
> future also.

FWIW, the options are not hardcoded. So a different set can = be displayed.

> And there are many aspects regarding the current Isearc= h state
> that it would be worthwhile indicating to users (either on an
> ongoing basis or on demand, depending on the aspect of state).
>
> The current value of a togglable variable, as well as the key
> to toggle it, is info that falls in that category: it is part
> of the current state.=C2=A0 I'd sooner see this info handled along=
> with other state info.=C2=A0 We've discussed this in other threads= ,
> I believe.

I agree with you partially. The information of which options= are active or relevant is a state info. Bit the info of which key toggles = them is of general use (and I'd like to expose it to users who don'= t read the manual).

--089e01228934631b7e05233b8531--