From: Nikolaj Schumacher <me@nschum.de>
To: Rick Mohr <Rick@RickMohr.net>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Changing pointer shape in Windows
Date: Fri, 03 Oct 2008 16:20:27 +0200 [thread overview]
Message-ID: <m2iqs9vjys.fsf@nschum.de> (raw)
In-Reply-To: <48E4C0E8.4040603@RickMohr.net> (Rick Mohr's message of "Thu\, 02 Oct 2008 08\:39\:04 -0400")
Rick Mohr <Rick@RickMohr.net> wrote:
> I will enter a bug as you suggest for the I-beam pointer.
>
> Are you saying it's no longer an option to use the "arrow" pointer
> over text?
No, I didn't say that. It might be possible, I don't know.
> Is it no longer an option to use the "box" cursor?
On my installation that's still the default.
Check the variable `cursor-type', if it doesn't work.
regards,
Nikolaj Schumacher
prev parent reply other threads:[~2008-10-03 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 15:11 Changing pointer shape in Windows Rick Mohr
2008-10-01 17:50 ` Nikolaj Schumacher
2008-10-02 12:39 ` Rick Mohr
2008-10-03 14:20 ` Nikolaj Schumacher [this message]
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=m2iqs9vjys.fsf@nschum.de \
--to=me@nschum.de \
--cc=Rick@RickMohr.net \
--cc=help-gnu-emacs@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.
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).