From: Nikhil Nair <nnair@pobox.com>
Subject: Re: Windows Emacs and screen readers
Date: Wed, 29 Jun 2005 18:32:09 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.58.0506291749440.8990@dsl-212-23-31-41.zen.co.uk> (raw)
In-Reply-To: <loom.20050629T092720-383@post.gmane.org>
On Wed, 29 Jun 2005, Emilio Lopes wrote:
> Jason Rumney <jasonr <at> gnu.org> writes:
>
> > [...]
> > You need the later development version. Although the first changes to
> > use the system caret were made in 2001, a few months before 21.1 was
> > released, it was too close to the release to make it into 21.1, and
> > subsequent releases have all been bugfix releases.
> >
>
> Here is the documentation of the relevant user option:
>
> w32-use-visible-system-caret's value is nil
>
> Flag to make the system caret visible.
> When this is non-nil, Emacs will indicate the position of point by
> using the system caret instead of drawing its own cursor. Some screen
> reader software does not track the system cursor properly when it is
> invisible, and gets confused by Emacs drawing its own cursor, so this
> variable is initialized to t when Emacs detects that screen reader
> software is running as it starts up.
>
> When this variable is set, other variables affecting the appearance of
> the cursor have no effect.
>
> Defined in `C source code'.
Thanks to both of you for these helpful comments, and to Lennart Borgman
who pointed me to the precompiled version at
http://ourcomments.org/Emacs/EmacsW32.html .
I've just tried to install the development version I found there, on XP
SP2 (non-admin account), keeping all of the defaults except the
installation directory, which I put in my user account's filespace. It
seemed to install, but then wouldn't run; I get:
---------------------------
C:\Documents and Settings\nnair\Emacs\setup\bin\gnuclientw.exe
---------------------------
Could not start runemacs --load="C:/Documents and Settings/nnair/Emacs/setup/bin/gnuservauto.el"
---------------------------
OK
---------------------------
(the above is the result of cutting from a message box with C-c.)
Any hints appreciated. I did the installation from an unprivileged
account, but since the option it gave me was to do a full installation
except anything requiring privileged access, I presumed this would be
fine.
Cheers,
Nikhil.
next prev parent reply other threads:[~2005-06-29 17:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-28 21:55 Windows Emacs and screen readers Nikhil Nair
2005-06-28 22:17 ` Nick Roberts
2005-06-28 23:30 ` Jason Rumney
2005-06-29 7:30 ` Emilio Lopes
2005-06-29 17:32 ` Nikhil Nair [this message]
2005-06-29 18:57 ` NTEmacs documentation (was: Windows Emacs and screen readers) Eli Zaretskii
2005-07-01 16:50 ` Screen reader detection broken [Was: Re: Windows Emacs and screen readers] Nikhil Nair
2005-07-01 21:17 ` Eli Zaretskii
2005-07-01 22:04 ` Screen reader detection broken Jason Rumney
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=Pine.LNX.4.58.0506291749440.8990@dsl-212-23-31-41.zen.co.uk \
--to=nnair@pobox.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 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).