[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: viper and the minibuffer text color
From: |
Thorsten Bonow |
Subject: |
Re: viper and the minibuffer text color |
Date: |
Sat, 05 Nov 2022 12:54:02 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) |
>>>>> Andrés Ramírez <rrandresf@hotmail.com> writes:
> Hi. I am trying viper.
> When I do:
> TERM=xterm-256color emacs -Q -nw --eval "(run-at-time nil nil
> #'call-interactively 'execute-extended-command)"
> colors in the minibuffer are showed as it should be.
> But If I do:
> TERM=xterm-256color emacs -Q -nw --eval "(progn (setq viper-mode t) (setq
> viper-inhibit-startup-message 't) (setq viper-expert-level '1) (require
> 'viper)(run-at-time nil nil #'call-interactively 'execute-extended-command))"
> then the minibuffer text color is affected. How Could I restore the
> minibuffer color as it should be?.
> Is that a bug?
Hi Andrés!
No, it's not a bug. You activated Viper and GNU Emacs behaves accordingly ;-)
Viper indicates in which vi/viper state it is in by visual feedback. The
"pink" you're seeing is `viper-minibuffer-insert-face', the face used in
`viper-minibuffer-insert' which is the---quoting from the documentation---"Face
used in the Minibuffer when it is in Insert state". You could customize
`viper-minibuffer-insert' if you want to change it. (Which I wouldn't do until
being so familiar with Viper and the reasoning behind it to make an informed
decision.)
Hope this helps,
Toto
> Best Regards
--
Sent from my GNU Emacs running on GNU/Linux