all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: 33664@debbugs.gnu.org
Subject: bug#33664: 26.1; Document vars and functions in `cursor-sensor.el'
Date: Sun, 9 Dec 2018 10:38:10 -0800 (PST)	[thread overview]
Message-ID: <2d046b88-a442-43ec-98a1-88a5a96f1e7c@default> (raw)
In-Reply-To: <cfd3992c-7a13-4ff5-816f-689ceb856396@default>

> +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?





  parent reply	other threads:[~2018-12-09 18:38 UTC|newest]

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

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

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

  git send-email \
    --in-reply-to=2d046b88-a442-43ec-98a1-88a5a96f1e7c@default \
    --to=drew.adams@oracle.com \
    --cc=33664@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.