unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Dani Moncayo'" <dmoncayo@gmail.com>, "'Eli Zaretskii'" <eliz@gnu.org>
Cc: 12922@debbugs.gnu.org
Subject: bug#12922: 24.3.50; `make-pointer-invisible' don't seem to work
Date: Sun, 18 Nov 2012 13:46:45 -0800	[thread overview]
Message-ID: <477A031D55CA4053A5030621C75BF681@us.oracle.com> (raw)
In-Reply-To: <CAH8Pv0iGT7g83ueivUfZ3sZ0wUekXzvkXdm0xbrauF0xiaMVCQ@mail.gmail.com>

> a bug in the documentation, i.e., the program's behavior is
> the intended one, but the documentation doesn't
> describes that behavior.  And that is what happens here.
> 
> Definitions aside, the fact is that currently, any user of the
> MS-Windows port of Emacs will be confused when she reads about the
> `make-pointer-invisible' variable and notice that the actual behavior
> of the program does not match the documentation.

If it is not possible to update the doc wrt specific platforms here and there,
describing specific limitations per platform, perhaps it would at least be
possible in some cases (like this one) to state that the feature (whatever it is
- making the pointer invisible, for instance) "might not be available on some
platforms".

That would at least give readers a heads-up, so they do not completely wonder
what's going on and whether (a) there is perhaps a product bug or (b) they are
perhaps misreading the doc.

Yes, such a weak caveat is true for nearly all features.  But this is not
something black-and-white, all-or-nothing.

If such caveats are used judiciously, i.e., only in places where we in fact do
not support a feature on some platform (especially a commonly used platform) and
where we realize there might well be a chance for reader confusion, then I, for
one, think they could be helpful. 






  reply	other threads:[~2012-11-18 21:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-18 12:36 bug#12922: 24.3.50; `make-pointer-invisible' don't seem to work Dani Moncayo
2012-11-18 15:29 ` Eli Zaretskii
2012-11-18 15:38   ` Dani Moncayo
2012-11-18 15:54     ` Drew Adams
2012-11-18 17:11       ` Eli Zaretskii
2012-11-18 19:39         ` Dani Moncayo
2012-11-18 21:12           ` Eli Zaretskii
2012-11-18 21:36             ` Dani Moncayo
2012-11-18 21:46               ` Drew Adams [this message]
2015-07-06 11:04 ` martin rudalics

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=477A031D55CA4053A5030621C75BF681@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=12922@debbugs.gnu.org \
    --cc=dmoncayo@gmail.com \
    --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).