all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
* viper and the minibuffer text color
@ 2022-11-04 16:12 Andrés Ramírez
  2022-11-05 11:54 ` Thorsten Bonow
  0 siblings, 1 reply; 3+ messages in thread
From: Andrés Ramírez @ 2022-11-04 16:12 UTC (permalink / raw)
  To: help-gnu-emacs

[-- Attachment #1: Type: text/plain, Size: 824 bytes --]

Hi.

I am trying viper.

When I do:
--8<---------------cut here---------------start------------->8---
TERM=xterm-256color emacs -Q -nw --eval "(run-at-time nil nil #'call-interactively 'execute-extended-command)"
--8<---------------cut here---------------end--------------->8---

colors in the minibuffer are showed as it should be.

But If I do:
--8<---------------cut here---------------start------------->8---
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))"
--8<---------------cut here---------------end--------------->8---

then the minibuffer text color is affected. How Could I restore the
minibuffer color as it should be?.

Is that a bug?


[-- Attachment #2: as_it_should_be --]
[-- Type: image/png, Size: 24476 bytes --]

[-- Attachment #3: changed_by_viper --]
[-- Type: image/png, Size: 24807 bytes --]

[-- Attachment #4: Type: text/plain, Size: 14 bytes --]


Best Regards

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: viper and the minibuffer text color
  2022-11-04 16:12 viper and the minibuffer text color Andrés Ramírez
@ 2022-11-05 11:54 ` Thorsten Bonow
  2022-11-05 14:01   ` andrés ramírez
  0 siblings, 1 reply; 3+ messages in thread
From: Thorsten Bonow @ 2022-11-05 11:54 UTC (permalink / raw)
  To: help-gnu-emacs

>>>>> 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




^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: viper and the minibuffer text color
  2022-11-05 11:54 ` Thorsten Bonow
@ 2022-11-05 14:01   ` andrés ramírez
  0 siblings, 0 replies; 3+ messages in thread
From: andrés ramírez @ 2022-11-05 14:01 UTC (permalink / raw)
  To: Thorsten Bonow; +Cc: help-gnu-emacs

Hi. Thorsten.
My comments below.

>>>>> "Thorsten" == Thorsten Bonow <thorsten.bonow@post.rwth-aachen.de> writes:

[...]

    Thorsten> No, it's not a bug.  You activated Viper and GNU Emacs behaves accordingly ;-)

Ok. That is good to know. The reason I am asking is because evil-mode does not change that
face.

    Thorsten> Viper indicates in which vi/viper state it is in by visual feedback.  The "pink"
    Thorsten> you're seeing is `viper-minibuffer-insert-face', the face used in
    Thorsten> `viper-minibuffer-insert' which is the---quoting from the documentation---"Face used
    Thorsten> in the Minibuffer when it is in Insert state".  You could customize
    Thorsten> `viper-minibuffer-insert' if you want to change it.  (Which I wouldn't do until being
    Thorsten> so familiar with Viper and the reasoning behind it to make an informed decision.)
    
As I came from evil. Some evil users had found a different way of detecting the
states. It involves the funct (which changes the modeline color):
,---- [  ]
| (add-hook 'post-command-hook 'do--change-mode-line-color-by-viper-state)
`----

I am sharing my complete viper setup(JIC):
--8<---------------cut here---------------start------------->8---
https://termbin.com/zzfu
--8<---------------cut here---------------end--------------->8---

    Thorsten> Hope this helps, Toto

Yes. It helps. Thanks.

Best Regards



^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2022-11-05 14:01 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-11-04 16:12 viper and the minibuffer text color Andrés Ramírez
2022-11-05 11:54 ` Thorsten Bonow
2022-11-05 14:01   ` andrés ramírez

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.