From: Kevin Rodgers <kevin.rodgers@ihs.com>
Subject: Re: changing the shape/visability of the mouse-pointer
Date: Thu, 23 Jan 2003 17:28:09 -0700 [thread overview]
Message-ID: <3E308899.5060704@ihs.com> (raw)
In-Reply-To: mailman.891.1043361727.21513.help-gnu-emacs@gnu.org
don fisher wrote:
> I do not subscribe normally to this list, so please copy me direct. Is
> there any way to change the mouse pointer from XC_xterm to something
> else. When I use small fonts, this cursor is hard to track/see.
>
> XC_sb_v_double_arrow is similar, but XC_top_left_arrow would work also.
>
> I can recompile the code, but I assumed there must be an easier way.
> Sorry if this is a real dumb one;-)
(setq x-pointer-shape x-pointer-sb-v-double-arrow) ; or x-pointer-top-left-arrow
--
<a href="mailto:<kevin.rodgers@ihs.com>">Kevin Rodgers</a>
next parent reply other threads:[~2003-01-24 0:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.891.1043361727.21513.help-gnu-emacs@gnu.org>
2003-01-24 0:28 ` Kevin Rodgers [this message]
[not found] ` <3E308D6D.6070805@as.arizona.edu>
2003-01-24 0:58 ` changing the shape/visability of the mouse-pointer Kevin Rodgers
2003-01-23 22:40 don fisher
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=3E308899.5060704@ihs.com \
--to=kevin.rodgers@ihs.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.
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).