unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 33664@debbugs.gnu.org, Stefan Monnier <monnier@IRO.UMontreal.CA>
Subject: bug#33664: 26.1; Document vars and functions in `cursor-sensor.el'
Date: Sun, 13 Oct 2019 00:12:57 +0200	[thread overview]
Message-ID: <874l0dipee.fsf@gnus.org> (raw)
In-Reply-To: <2d046b88-a442-43ec-98a1-88a5a96f1e7c@default> (Drew Adams's message of "Sun, 9 Dec 2018 10:38:10 -0800 (PST)")

Drew Adams <drew.adams@oracle.com> writes:

>> +1.  The bug can be closed, IMO.
>
> Oh, but one other thing:
>
> We're still saying that it's enough that
> the variable be Boolean.  OK - that's true,
> and that's perhaps all that matters to
> `cursor-sensor.el'.
>
> But what about Isearch's use of it?  There
> seems to be a disconnect of sorts, wrt
> intention.
>
> Should the variable be documented more in
> line with the Isearch use of it: encourage
> pushing to a list value instead of just
> setting to some other non-nil value?

This was part of the patch:

+(defvar cursor-sensor-inhibit nil
+  "When non-nil, suspend `cursor-sensor-mode' and `cursor-intangible-mode'.
+By convention, this is a list of symbols where each symbol stands for the
+\"cause\" of the suspension.")

So I think this has been documented now, unless I misunderstand what you
mean, and I'm closing this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2019-10-12 22:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<cfd3992c-7a13-4ff5-816f-689ceb856396@default>
     [not found] ` <<jwvo99u4x81.fsf-monnier+bug#33664@gnu.org>
     [not found]   ` <<83zhte3f4n.fsf@gnu.org>
2018-12-07 15:15     ` bug#33664: 26.1; Document vars and functions in `cursor-sensor.el' Drew Adams
2018-12-07 15:28       ` Drew Adams
2018-12-07 15:34         ` Drew Adams
2018-12-07 15:35       ` Eli Zaretskii
2018-12-08  3:24         ` Richard Stallman
2018-12-09 14:01       ` Stefan Monnier
2018-12-09 15:15         ` Eli Zaretskii
2018-12-10  3:09         ` Richard Stallman
2018-12-09 18:38       ` Drew Adams
2019-10-12 22:12         ` Lars Ingebrigtsen [this message]
2018-12-09 18:32     ` Drew Adams
2018-12-09 19:35       ` Stefan Monnier
2018-12-09 20:56         ` Drew Adams
2018-12-10  1:58           ` Stefan Monnier
     [not found] ` <<83k1kl5ozh.fsf@gnu.org>
2018-12-07 15:57   ` Drew Adams
2018-12-07 16:29     ` Eli Zaretskii
2018-12-08 23:10     ` Juri Linkov
2018-12-09  3:53       ` Drew Adams

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=874l0dipee.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=33664@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=monnier@IRO.UMontreal.CA \
    /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).