all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Kifer <kifer@cs.sunysb.edu>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 2233@emacsbugs.donarmstrong.com,
	David Reitter <david.reitter@gmail.com>,
	Michael Kifer <kifer@cs.stonybrook.edu>,
	Nathan Sanders <ncsander@umail.iu.edu>
Subject: bug#2233: viper-mode cursor color does not reset to red
Date: Sat, 15 Aug 2009 18:38:14 -0400	[thread overview]
Message-ID: <20090815183814.3ac1157b@kiferdesk> (raw)
In-Reply-To: <87ab20n4x8.fsf@cyd.mit.edu>

Yes, the code for viper-save-cursor-color needs an overhaul, but I don't know
when I'll have the time for it.

On Sat, 15 Aug 2009 17:27:47 -0400
Chong Yidong <cyd@stupidchicken.com> wrote:

> Hi Michael, could you take a look at this bug report (2233 in the bug
> tracker)?  Thanks.
> 
> > if your present cursor color (the default is set in
> > `default-frame-alist') is the same as
> > `viper-replace-overlay-cursor-color' (by default: "Red"), then Viper
> > forgets to save it before switching to insert mode.
> >
> > The solution would be to implement `viper-save-cursor-color' cleanly,  
> > unless that's already been done for Emacs 23 (haven't checked).
> >
> > On 7 Feb 2009, at 08:48, Nathan Sanders wrote:
> >
> > > After loading viper-mode, the cursor turns green when in Insert mode.
> > > It is supposed to return to red when Esc is pressed to return to VI
> > > mode. It does not. This occurs whether starting viper-mode
> > > interactively after emacs starts, or when .emacs consists solely of
> > >
> > > (setq viper-mode t)
> > > (require 'viper)
> 





      reply	other threads:[~2009-08-15 22:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-15 21:27 bug#2233: viper-mode cursor color does not reset to red Chong Yidong
2009-08-15 22:38 ` Michael Kifer [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090815183814.3ac1157b@kiferdesk \
    --to=kifer@cs.sunysb.edu \
    --cc=2233@emacsbugs.donarmstrong.com \
    --cc=cyd@stupidchicken.com \
    --cc=david.reitter@gmail.com \
    --cc=kifer@cs.stonybrook.edu \
    --cc=ncsander@umail.iu.edu \
    /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.