From: Hongyi Zhao <hongyi.zhao@gmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Tab completion doesn't work.
Date: Mon, 15 May 2023 08:27:23 +0800 [thread overview]
Message-ID: <CAGP6POKq=uvvUPd1FqZ5A=TJxu4mmyezoD6VcV42ifz1cFG5yw@mail.gmail.com> (raw)
In-Reply-To: <87353yv4rj.fsf@web.de>
On Mon, May 15, 2023 at 8:05 AM Michael Heerdegen
<michael_heerdegen@web.de> wrote:
>
> Hongyi Zhao <hongyi.zhao@gmail.com> writes:
>
> > Any tips for this problem?
>
> Is the package correctly installed and loaded?
In my case, the configuration for helm and helm-bibtex is as follows:
```elisp
(use-package helm
:bind (:map helm-command-map
("C-c h" . helm-execute-persistent-action)))
(use-package helm-bibtex
:init
(setq
bibtex-completion-pdf-field "File"
;;https://github.com/tmalsburg/helm-bibtex#insert-latex-cite-commands
bibtex-completion-cite-prompt-for-optional-arguments nil)
:bind-keymap
("<menu>" . helm-command-prefix)
:bind
(
:map helm-command-map
("b" . helm-bibtex)
("B" . helm-bibtex-with-local-bibliography)
("n" . helm-bibtex-with-notes)
("<menu>" . helm-resume)
)
:config
(require 'helm-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)))
)
```
I confirm the above configuration alone when testing with `emacs -Q`
doesn't trigger the problem here. So, it must be caused by other
settings.
See here [1] for the related discussion.
[1] https://github.com/tmalsburg/helm-bibtex/issues/431#issuecomment-1545772936
> Michael.
Regards,
Zhao
next prev parent reply other threads:[~2023-05-15 0:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-14 14:28 Tab completion doesn't work Hongyi Zhao
2023-05-15 0:04 ` Michael Heerdegen
2023-05-15 0:27 ` Hongyi Zhao [this message]
2023-05-15 0:35 ` Michael Heerdegen
2023-05-15 0:46 ` Hongyi Zhao
2023-05-15 1:22 ` Michael Heerdegen
2023-05-15 1:29 ` Hongyi Zhao
2023-05-15 1:58 ` Michael Heerdegen
2023-05-15 3:24 ` Hongyi Zhao
2023-05-15 3:36 ` Michael Heerdegen
2023-05-15 3:58 ` Hongyi Zhao
2023-05-15 4:20 ` Michael Heerdegen
2023-05-15 4:48 ` Hongyi Zhao
2023-05-15 5:35 ` Michael Heerdegen
2023-05-15 6:21 ` Hongyi Zhao
2023-05-15 22:56 ` Michael Heerdegen
2023-05-16 0:14 ` Hongyi Zhao
2023-05-16 1:31 ` Michael Heerdegen
2023-05-16 1:50 ` Hongyi Zhao
2023-05-16 2:11 ` Michael Heerdegen
2023-05-16 2:55 ` Hongyi Zhao
2023-05-16 3:21 ` Michael Heerdegen
2023-05-16 3:44 ` Hongyi Zhao
2023-05-16 3:53 ` Hongyi Zhao
2023-05-16 4:24 ` Michael Heerdegen
2023-05-16 6:18 ` Hongyi Zhao
2023-05-16 20:01 ` Michael Heerdegen
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='CAGP6POKq=uvvUPd1FqZ5A=TJxu4mmyezoD6VcV42ifz1cFG5yw@mail.gmail.com' \
--to=hongyi.zhao@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.de \
/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).