[Emacs-bug-tracker] bug#7474: closed (In latest source, icomplete-mode makes cursor disappear in minibuffer)

[GNU bug Tracking System]

Your message dated Thu, 25 Nov 2010 20:40:18 +0200
with message-id <address@hidden>
and subject line Re: bug#7474: In latest source, icomplete-mode makes cursor 
disappear in minibuffer
has caused the GNU bug report #7474,
regarding In latest source, icomplete-mode makes cursor disappear in minibuffer
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
7474: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=7474
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> In latest source, icomplete-mode makes cursor disappear in minibuffer
>
>
>
>
> Date: 
>
> Wed, 24 Nov 2010 14:56:28 -0500
>
>
>
>
> Using Emacs built from the latest source on Windows 7, the cursor
> can be made to disappear as follows:
>
> 1. Start Emacs with: emacs -Q
>
> 2. Type: ESC ESC : (icomplete-mode 1) RET C-h v desc
>
> 3. The cursor is no longer visisble in the minibuffer.
>
> 4. Type: C-b
>
> 5. The cursor is visible over the letter 'c' in "desc".
>
> 6. Type: C-f
>
> 7. The cursor is once again no longer visible.
>
> This is acting like some of the text in the minibuffer has the
> 'intangible property, but the word "intangible" doesn't appear anywhere
> in lisp/icomplete.el.
> --
> Fran
>
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#7474: In latest source,	icomplete-mode makes cursor disappear in minibuffer
>
>
>
>
> Date: 
>
> Thu, 25 Nov 2010 20:40:18 +0200
>
>
>
>
> > Date: Wed, 24 Nov 2010 23:16:21 +0200
> > From: Eli Zaretskii <address@hidden>
> > Cc: address@hidden
> > 
> > > From: address@hidden (Francis Litterio)
> > > Date: Wed, 24 Nov 2010 14:56:28 -0500
> > > Cc: 
> > > 
> > > Using Emacs built from the latest source on Windows 7, the cursor
> > > can be made to disappear as follows:
> > 
> > I see it on Windows XP as well.  It's probably my fault, due to the
> > latest changes in cursor positioning code.
>
> As expected, this was due to latest changes in cursor positioning.
> Should be fixed now (in revno 102512).  Thanks.
>
>
> --- End Message ---