From: Eli Zaretskii <eliz@gnu.org>
To: "andrés ramírez" <rrandresf@hotmail.com>
Cc: 61432@debbugs.gnu.org
Subject: bug#61432: 28.2; [PATCH] viper-init: disable face support
Date: Sat, 11 Feb 2023 18:30:28 +0200 [thread overview]
Message-ID: <83zg9ki2qj.fsf@gnu.org> (raw)
In-Reply-To: <SJ1PR12MB63633D7BFE129E338E2FFF82A6DF9@SJ1PR12MB6363.namprd12.prod.outlook.com> (message from andrés ramírez on Sat, 11 Feb 2023 16:10:23 +0000)
> From: andrés ramírez <rrandresf@hotmail.com>
> Cc: 61432@debbugs.gnu.org
> Date: Sat, 11 Feb 2023 16:10:23 +0000
>
> Eli> Can't you have the same effect if you customize the faces viper-minibuffer-emacs-face and
> Eli> viper-minibuffer-vi-face to look the same?
>
> I have tried some modifications. like this one.
The easiest one is this:
(require 'viper-init)
(setq viper-minibuffer-vi-face viper-minibuffer-emacs-face)
Did you try that?
> Hope that clarifies the use of this variable.
>
> And the most of vipers users are not going to notice that variable.
My problem with this is twofold:
. I don't like to have code in Emacs which "works around" our own code
. viper-has-face-support-p is used for more than just the mode line
So I'd prefer a different solution. And in this case, it sounds like
a possible solution already exists, see above.
next prev parent reply other threads:[~2023-02-11 16:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 14:22 bug#61432: 28.2; [PATCH] viper-init: disable face support Andrés Ramírez
2023-02-11 15:38 ` Eli Zaretskii
2023-02-11 16:10 ` andrés ramírez
2023-02-11 16:30 ` Eli Zaretskii [this message]
2023-02-11 18:32 ` andrés ramírez
2023-02-11 18:48 ` Eli Zaretskii
2023-02-12 17:54 ` andrés ramírez
2023-02-12 18:30 ` Eli Zaretskii
2023-02-12 18:53 ` andrés ramírez
2023-02-13 14:00 ` Robert Pluim
2023-02-13 15:02 ` andrés ramírez
2023-02-13 17:02 ` Robert Pluim
2023-02-18 17:01 ` Eli Zaretskii
2023-02-18 17:01 ` Eli Zaretskii
[not found] ` <SJ1PR12MB63635DCA5881078AB2D3ED0BA6AB9@SJ1PR12MB6363.namprd12.prod.outlook.com>
2023-02-23 15:09 ` Robert Pluim
2023-02-23 15:24 ` andrés ramírez
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=83zg9ki2qj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=61432@debbugs.gnu.org \
--cc=rrandresf@hotmail.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 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.