From: Hongyi Zhao <hongyi.zhao@gmail.com>
To: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: command-execute: Wrong type argument: commandp, helm-command-prefix
Date: Fri, 5 May 2023 08:34:07 +0800 [thread overview]
Message-ID: <CAGP6PO+YCVnjkN59o0sx2Dt7Bu7=YmBeodSpLJnReZP8rj5TUQ@mail.gmail.com> (raw)
Hi here,
I'm using the following configuration for `helm-bibtex`:
```
(use-package helm-bibtex
:init
(setq
;; bibtex-completion-bibliography (directory-files-recursively
;; (concat (getenv "HOME")
"/texmf/bibtex/bib/local") "^[A-Za-z].+.bib$")
;;bibtex-completion-library-path (concat (getenv "HOME") "/pdf")
;;bibtex-completion-notes-path (concat (getenv "HOME") "/notes")
bibtex-completion-pdf-field "File"
;;https://github.com/tmalsburg/helm-bibtex#insert-latex-cite-commands
bibtex-completion-cite-prompt-for-optional-arguments nil)
:config
(require 'helm-config)
:bind
(("<menu>" . helm-command-prefix)
:map helm-command-map
("b" . helm-bibtex)
("B" . helm-bibtex-with-local-bibliography)
("n" . helm-bibtex-with-notes)
("<menu>" . helm-resume))
:config
;;https://github.com/tmalsburg/helm-bibtex#application-used-for-opening-pdfs
;;https://github.com/tmalsburg/helm-bibtex/issues/386
(defun bibtex-completion-open-pdf-external (keys &optional fallback-action)
(let ((bibtex-completion-pdf-open-function
(lambda (fpath) (start-process "evince" "*helm-bibtex-evince*"
"/usr/bin/evince" fpath))))
(bibtex-completion-open-pdf keys fallback-action)))
(helm-bibtex-helmify-action bibtex-completion-open-pdf-external
helm-bibtex-open-pdf-external)
(helm-add-action-to-source
'helm-bibtex
'(("P" helm-bibtex-open-pdf-external "Open PDF file in external
viewer (if present)")))
;;https://github.com/tmalsburg/helm-bibtex#browser-used-for-opening-urls-and-dois
(setq bibtex-completion-browser-function
(lambda (url _) (start-process "firefox" "*firefox*" "firefox" url)))
)
```
When I hit <menu> hey for the first time, the following error will be triggered:
command-execute: Wrong type argument: commandp, helm-command-prefix
If I hit this key once more, the problem doesn't appear. I'm very
puzzled by this problem. Any tips will be appreciated.
See https://github.com/tmalsburg/helm-bibtex/issues/429#issuecomment-1535010227
for the related discussion.
Regards,
Zhao
--
Assoc. Prof. Hongsheng Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province
next reply other threads:[~2023-05-05 0:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 0:34 Hongyi Zhao [this message]
2023-05-05 1:40 ` command-execute: Wrong type argument: commandp, helm-command-prefix Platon Pronko
2023-05-05 2:45 ` Ruijie Yu via Users list for the GNU Emacs text editor
2023-05-05 4:18 ` Hongyi Zhao
2023-05-05 5:04 ` Michael Heerdegen
2023-05-05 5:13 ` Hongyi Zhao
2023-05-05 5:18 ` Ruijie Yu via Users list for the GNU Emacs text editor
2023-05-05 5:59 ` Hongyi Zhao
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='CAGP6PO+YCVnjkN59o0sx2Dt7Bu7=YmBeodSpLJnReZP8rj5TUQ@mail.gmail.com' \
--to=hongyi.zhao@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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.
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).