From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 33664@debbugs.gnu.org
Subject: bug#33664: 26.1; Document vars and functions in `cursor-sensor.el'
Date: Fri, 7 Dec 2018 15:57:58 +0000 (UTC) [thread overview]
Message-ID: <b9d9cc19-8e6e-49d6-bc96-07ee50aeb40a@default> (raw)
In-Reply-To: <<83k1kl5ozh.fsf@gnu.org>>
> AFAIK, about the only person who could do something about this doesn't
> read bug reports.
Maybe you mean might instead of could? Anyone who has
the will could, I suppose.
But maybe the use of the variable as a list value is
only an Isearch thing (that's the only place it's used,
so far), and is not something intended/prescribed by
`cursor-sensor.el'.
Juri reads bug reports, and he has worked on Isearch
(dunno whether he worked on this part of it). Maybe
the design/use of the var for Isearch could be
documented in a comment in `isearch.el', at least.
But if its use as a list is part of the general
design/intention then that should be made clear in
`cursor-sensor.el', I think.
next prev parent reply other threads:[~2018-12-07 15:57 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
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 [this message]
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=b9d9cc19-8e6e-49d6-bc96-07ee50aeb40a@default \
--to=drew.adams@oracle.com \
--cc=33664@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).