unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dani Moncayo <dmoncayo@gmail.com>
To: 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 22:36:01 +0100	[thread overview]
Message-ID: <CAH8Pv0iGT7g83ueivUfZ3sZ0wUekXzvkXdm0xbrauF0xiaMVCQ@mail.gmail.com> (raw)
In-Reply-To: <83fw46zkcr.fsf@gnu.org>

>> > We don't normally do that in the manuals, but feel free to suggest
>> > changes, perhaps Stefan or Chong will accept them.
>>
>> Not sure about the docstrings, but the Emacs Manual has many
>> references to MS-Windows, explaining things specific to that platform,
>> which obviously is TRT, as that is a supported platform.
>
> No, I meant we don't normally say in the manual "this and that feature
> is not (yet) implemented on this and that platform."  Especially if
> that platform is Windows.

I don't see the point of not doing that.

>> The very reason for filing this bug report was that I read about a
>> feature that didn't work for me.  If the documentation had been
>> accurate, I wouldn't have had to send this bug report.
>>
>> IOW, this is a documentation bug.  So, why not fixing it?
>
> Because it's not a documentation bug.  It's a feature that's missing
> on one particular platform.

To me, a documentation bug is 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.

-- 
Dani Moncayo





  reply	other threads:[~2012-11-18 21:36 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 [this message]
2012-11-18 21:46               ` Drew Adams
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=CAH8Pv0iGT7g83ueivUfZ3sZ0wUekXzvkXdm0xbrauF0xiaMVCQ@mail.gmail.com \
    --to=dmoncayo@gmail.com \
    --cc=12922@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).