all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@gmail.com>
To: Vasilij Schneidermann <v.schneidermann@gmail.com>
Cc: 20076@debbugs.gnu.org
Subject: bug#20076: 24.4; x-nontext-pointer-shape not existent as option from Lisp code
Date: Sun, 12 Aug 2018 20:05:32 -0400	[thread overview]
Message-ID: <87600fw2pf.fsf@gmail.com> (raw)
In-Reply-To: <87fv9cwl0l.fsf@gmail.com> (Vasilij Schneidermann's message of "Tue, 10 Mar 2015 23:22:18 +0100")

Vasilij Schneidermann <v.schneidermann@gmail.com> writes:

> I've attempted to customize the shape of the pointer for the current
> frame, what I've found out so far is that there are a text property to
> change the pointer shape when hovering over it and the `x-pointer-shape'
> option which takes effect on hovering over text.  Looking at the xfns.c
> file in the Emacs 24.4 sources revealed to me that there is a
> `x-nontext-pointer-shape' option which is processed similiarly to the
> `x-pointer-shape' option, however the code responsible for exposing it
> in the Lisp code is commented out with a preprocessor directive.
>
> Is there any particular reason for this peculiar decision?  Or more
> generally, why would a desirable feature be present, but commented out
> from code?  Are there any special known caveats that led to it?

I think the reasons are lost to the mist of time, [1: af01ef2643] is the commit
which ifdefs it out; the changelog is not very enlightening.

[1: af01ef2643]: 1993-05-21 20:22:10 +0000
  (syms_of_xfns): Don't make Lisp vars x-mode-pointer-shape and x-nontext-pointer-shape.
  https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=af01ef26430d69c04421aac4d862df4f5898a838





  reply	other threads:[~2018-08-13  0:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-10 22:22 bug#20076: 24.4; x-nontext-pointer-shape not existent as option from Lisp code Vasilij Schneidermann
2018-08-13  0:05 ` Noam Postavsky [this message]
2018-08-13 15:06   ` Eli Zaretskii

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=87600fw2pf.fsf@gmail.com \
    --to=npostavs@gmail.com \
    --cc=20076@debbugs.gnu.org \
    --cc=v.schneidermann@gmail.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.