unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: "andrés ramírez" <rrandresf@hotmail.com>
Cc: 61432@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#61432: 28.2; [PATCH] viper-init: disable face support
Date: Mon, 13 Feb 2023 15:00:26 +0100	[thread overview]
Message-ID: <874jrpr7gl.fsf@gmail.com> (raw)
In-Reply-To: <SJ1PR12MB6363402226C2186472F16E91A6DC9@SJ1PR12MB6363.namprd12.prod.outlook.com> ("andrés ramírez"'s message of "Sun, 12 Feb 2023 18:53:05 +0000")

>>>>> On Sun, 12 Feb 2023 18:53:05 +0000, andrés ramírez <rrandresf@hotmail.com> said:
    INKA>    ;; minibuffer faces
    INKA> -  (if (viper-has-face-support-p)
    INKA> +  (if (and (viper-has-face-support-p) (not (and (boundp 'viper-disable-minibuffer-faces) viper-disable-minibuffer-faces)))
    INKA>        (setq viper-minibuffer-current-face
    INKA>  	    (cond ((eq state 'emacs-state) viper-minibuffer-emacs-face)
    INKA>  		  ((eq state 'vi-state) viper-minibuffer-vi-face)
    INKA> @@ -1923,6 +1923,12 @@
    INKA>    :group 'viper-misc)
 
You donʼt need to check if 'viper-disable-minibuffer-faces'  is
bound. Itʼs a defcustom, it will always be bound.

    INKA> +(defcustom viper-disable-minibuffer-faces nil
    INKA> +  "If non-nil, viper does change the minibuffer faces."
    INKA> +  :type 'boolean
    INKA> +  :group 'viper-misc)
    INKA> +
    INKA> +

Setting things to 't' to disable functionality I always find
confusing. How about you invert it:

    (defcustom viper-enable-minibuffer-faces t
      "Whether viper changes the minibuffer faces."
      :type 'boolean
      :group 'viper-misc)

Thanks

Robert
-- 





  reply	other threads:[~2023-02-13 14:00 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
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 [this message]
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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=874jrpr7gl.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=61432@debbugs.gnu.org \
    --cc=eliz@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).