From: Eli Zaretskii <eliz@gnu.org>
To: 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, 07 Dec 2018 17:35:30 +0200 [thread overview]
Message-ID: <83k1kl5ozh.fsf@gnu.org> (raw)
In-Reply-To: <cfd3992c-7a13-4ff5-816f-689ceb856396@default> (message from Drew Adams on Fri, 7 Dec 2018 15:15:37 +0000 (UTC))
> Date: Fri, 7 Dec 2018 15:15:37 +0000 (UTC)
> From: Drew Adams <drew.adams@oracle.com>
>
> Please document the variables and functions in `cursor-sensor.el'. It
> would be a step backward for Emacs to document less and less. Calling
> something an "internal" function is not, in itself, a sufficient reason
> not to give it a doc string.
>
> In particular, please add a doc string for variable
> `cursor-sensor-inhibit'.
>
> I was reading the `isearch.el' code and saw this: (push 'isearch
> cursor-sensor-inhibit). Had to start searching `cursor-sensor.el' to
> try to understand what this variable is for. Even that didn't really
> help, since there is nothing in `cursor-sensor.el' that would lead one
> to understand that the variable is used somehow as a list of values.
>
> Even grepping for that var didn't help with such understanding, as there
> are no uses of it outside of isearch.el.
>
> Isearch apparently goes to the trouble of allowing for the var to be
> used as a list (similar to `buffer-invisibility-spec', perhaps), but
> there is no comment, doc, or spec describing this behavior/use in
> `cursor-sensor.el'.
AFAIK, about the only person who could do something about this doesn't
read bug reports.
next prev parent reply other threads:[~2018-12-07 15:35 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 [this message]
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
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=83k1kl5ozh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33664@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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.