unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: 14875@debbugs.gnu.org
Subject: bug#14875: 24.3.50; doc of :variable in `define-minor-mode' - lamentable
Date: Mon, 15 Jul 2013 13:53:05 -0700 (PDT)	[thread overview]
Message-ID: <ad7eb5f6-e32a-470b-837f-92af5131b1da@default> (raw)

1. Both (elisp) `Defining Minor Modes' and the doc string say the same
thing, verbatim.  The manual should explain better.

2. The description/explanation is incomplete/confusing/gobbledygook, at
best.

It says that PLACE can be a "generalized variable", without giving any
explanation of what a generalized variable is, and without
cross-referencing any doc that describes such a thing.

It says that PLACE can also be a cons (GET . SET).  In this case, it
says that "SET is a function that takes one argument, the new state, and
sets it".

Huh?  It takes the NEW state as argument?  If so, where did that new state
come from?  And then it "sets" the new state?  Huh?  Does it just set it to
what it already was (the "new state" argument)?  Or does "set" here perhaps
imply setting the value to non-nil (as in setting a bit)?

It's not clear at all what the SET of (GET . SET) (1) accepts as arg,
(2) does as its main (standard) effect, or (3) returns as a value (if that
matters).

It says that if PLACE is specified as a variable then "this function
does not define a MODE variable (nor any of the terms used in :variable)".

Huh?  Does "variable" here include the "generalized variable" case?  Does
"this function" refer to the SET function of the preceding sentence?  Or
does it refer to the minor-mode function?  What on Earth does it mean for
the function (either of those functions, or whatever function is meant)
to not define "any of the terms used in :variable"?

I honestly understand almost nothing here.  :variable does not define
any of the terms used in :variable?  Huh?

Please, please.  Users deserve better.  Give us a break.  Please clear
this up.

3. And as is too often the case, the "For example,..." at the end gives
a too-trivial example that shows none of the things that someone might
really have a question about.



In GNU Emacs 24.3.50.1 (i686-pc-mingw32)
 of 2013-07-01 on LEG570
Bzr revision: 113246 lekktu@gmail.com-20130701165437-ea20s94hqwp3ttaj
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --prefix=/c/usr --enable-checking CFLAGS='-O0 -g3'
 CPPFLAGS='-DGLYPH_DEBUG=1 -I/c/usr/include''





                 reply	other threads:[~2013-07-15 20:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=ad7eb5f6-e32a-470b-837f-92af5131b1da@default \
    --to=drew.adams@oracle.com \
    --cc=14875@debbugs.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).