unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 22483@debbugs.gnu.org
Subject: bug#22483: 25.1.50; Doc string of `isearch-lax-whitespace' does not show toggle key
Date: Thu, 28 Jan 2016 09:00:24 -0800 (PST)	[thread overview]
Message-ID: <669780ea-838a-4101-8022-1947f9d00add@default> (raw)
In-Reply-To: <<838u39zm8f.fsf@gnu.org>>

> > The doc string says you can toggle using command
> > `isearch-togggle-lax-whitespace'.  That's pretty useless, as it makes
> > sense only during Isearch.
> 
> Not true, it makes sense outside of Isearch as well (toggles the
> default).

Interesting.  I thought this was a user option, but I see now that
it is not.  (I know that vanilla Emacs refuses to let users toggle
an option during Isearch, even though that lets them perform
subsequent searches also using the new value.)

So why does the toggle command initiate search as well?  And if
that is by design and not a bug, perhaps it should be documented
as part of the command behavior (it does not just toggle the
variable value).

`M-x isearch-lax-whitespace' starts searching backward, with this
message:

  Pending literal I-search backward:

Oh, and that happens each time I "toggle" the value.  The value
changes (correctly), but the search initiated always shows that
backward-literal-search message.





       reply	other threads:[~2016-01-28 17:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<f3c5f45c-4ce2-49f9-96e6-f4c0fe0d9b7d@default>
     [not found] ` <<838u39zm8f.fsf@gnu.org>
2016-01-28 17:00   ` Drew Adams [this message]
2016-01-28 15:55 bug#22483: 25.1.50; Doc string of `isearch-lax-whitespace' does not show toggle key Drew Adams
2016-01-28 16:00 ` Drew Adams
2016-01-28 16:08   ` Drew Adams
2016-01-28 16:46   ` Eli Zaretskii
2016-01-28 16:45 ` Eli Zaretskii
2021-09-25 16:12 ` Stefan Kangas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=669780ea-838a-4101-8022-1947f9d00add@default \
    --to=drew.adams@oracle.com \
    --cc=22483@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).