hyperbole-messaging defcustom in hyperbole.el with the version below, byte-compile the file and restart Emacs and tell us if this resolves your issue #1. For issue #2, none of the byte-compilation warnings should cause any issue. If you find an issue related to the warnings, please tell us about that. Thanks, Bob
(defcustom inhibit-hyperbole-messaging t
"*Determines whether Hyperbole supports explicit buttons in mail and news buffers.
The default of t means disable such support (work remains to
modernize these features). When t, Hyperbole will not alter
messaging mode hooks nor overload functions from these packages,
preventing potential incompatibilities.
If you want to use Hyperbole buttons in mail and news buffers, set
this variable to nil by adding (hyperbole-toggle-messaging t)
to your personal Emacs initialization file, prior to loading
Hyperbole, and then restart Emacs."
:type 'boolean
:initialize (lambda (symbol value) (set symbol value))
:set (lambda (symbol value)
(set symbol (not value))
(hyperbole-toggle-messaging nil))
:group 'hyperbole-buttons)On Sat, Jul 16, 2016 at 10:00 PM, Feng Shu <
address@hidden> wrote:
>
> 1. var:remove-all
>
> #+BEGIN_EXAMPLE
> Debugger entered--Lisp error: (void-function var:remove-all)
> var:remove-all()
> hyperbole-toggle-messaging(nil)
> #[(_symbol value) " ?\302\303!\207" [value inhibit-hyperbole-messaging hyperbole-toggle-messaging nil] 2](inhibit-hyperbole-messaging t)
> custom-initialize-reset(inhibit-hyperbole-messaging t)
> custom-declare-variable(inhibit-hyperbole-messaging t "*Determines whether Hyperbole supports explicit buttons in mail and news buffers.\nThe default of t means disable such support (work remains to\nmodernize these features). When t, Hyperbole will not alter\nmessaging mode hooks nor overload functions from these packages,\npreventing potential incompatibilities.\n\nIf you want to use Hyperbole buttons in mail and news buffers, set\nthis variable to nil by adding (hyperbole-toggle-messaging t)\nto your personal Emacs initialization file, prior to loading\nHyperbole, and then restart Emacs." :type boolean :set #[(_symbol value) " ?\302\303!\207" [value inhibit-hyperbole-messaging hyperbole-toggle-messaging nil] 2] :group hyperbole-buttons)
> byte-code("\301\302\303\304\305\306\307\310& \210\301\311\303\312\305\306\307\310& \210\301\313\303\314\305\306\315\316\307\317& \210\320\321!\210\320\322\323\324 \"\"\210\320\325!\210\326\327!\204=\327\330M\210\301\207" [hyperb:dir custom-declare-variable hkey-init t "*A non-nil value (default) at system load time binds the Action and Assist Keyboard Keys, as well as other keys.\n{\\[hkey-either]} invokes the Action Key and {C-u \\[hkey-either]} invokes the Assist Key.\nAdditionally, {\\[hkey-help]} shows what the Action Key will do in the current\ncontext (wherever point is). {C-u \\[hkey-help]} shows what the Assist Key will do." :type boolean :group hyperbole-keys hkey-init-override-local-keys "*If set together with `hkey-init', remove any local key bindings that hide the Hyperbole Smart Keys." inhibit-hyperbole-messaging "*Determines whether Hyperbole supports explicit buttons in mail and news buffers.\nThe default of t means disable such support (work remains to\nmodernize these features). When t, Hyperbole will not alter\nmessaging mode hooks nor overload functions from these packages,\npreventing potential incompatibilities.\n\nIf you want to use Hyperbole buttons in mail and news buffers, set\nthis variable to nil by adding (hyperbole-toggle-messaging t)\nto your personal Emacs initialization file, prior to loading\nHyperbole, and then restart Emacs." :set #[(_symbol value) " ?\302\303!\207" [value inhibit-hyperbole-messaging hyperbole-toggle-messaging nil] 2] hyperbole-buttons require hui-select set expand-file-name "set" hvar fboundp defalias fset] 10)
> require(hyperbole)
> eval((require (quote hyperbole)) nil)
> elisp--eval-last-sexp(nil)
> eval-last-sexp(nil)
> funcall-interactively(eval-last-sexp nil)
> call-interactively(eval-last-sexp nil nil)
> command-execute(eval-last-sexp)
>
> #+END_EXAMPLE
>
>
> 2. Too many build warns
>
>
> --
>
>