From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: My read-buffer-function doesn't work when called by switch-to-buffer
Date: Sat, 11 Mar 2023 01:32:07 +0100 [thread overview]
Message-ID: <87y1o486wo.fsf@web.de> (raw)
In-Reply-To: 875yb8nvvk.fsf@gnu.org
Tassilo Horn <tsdh@gnu.org> writes:
> (defun th/read-buffer-or-recentf (prompt &optional
> def require-match predicate)
> (when-let ((result (completing-read
> prompt
> (completion-table-in-turn #'internal-complete-buffer
> (completion-table-dynamic
> (lambda (s) recentf-list)))
> predicate require-match nil 'buffer-name-history def)))
> (cond
> ((get-buffer result) result)
> ((file-exists-p result) (buffer-name (find-file-noselect result)))
> (t result))))
>
> (setq read-buffer-function #'th/read-buffer-or-recentf)
> [...]
> However, when I do C-x b (switch-to-buffer), no matter what, recent
> files are not provided as completion candidates. But edebug convinces
> me that my function th/read-buffer-or-recentf is called. It just seems
> that the same completing-read call behaves differently when called
> directly and when being called by switch-to-buffer. Why is that and
> what can I do against it?
Seems this happens because `read-buffer-to-switch' sets
`minibuffer-completion-table'.
Michael.
next prev parent reply other threads:[~2023-03-11 0:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 21:10 My read-buffer-function doesn't work when called by switch-to-buffer Tassilo Horn
2023-03-11 0:32 ` Michael Heerdegen [this message]
2023-03-11 8:58 ` Tassilo Horn
2023-03-11 20:40 ` `when-let' (was: Re: My read-buffer-function doesn't work when called by switch-to-buffer) Emanuel Berg
2023-03-12 3:32 ` My read-buffer-function doesn't work when called by switch-to-buffer Michael Heerdegen
2023-03-12 18:51 ` Tassilo Horn
2023-03-13 0:32 ` Michael Heerdegen
2023-03-15 9:06 ` Tassilo Horn
2023-03-15 18:57 ` Michael Heerdegen
2023-03-16 9:18 ` Tassilo Horn
2023-03-16 16:59 ` Tassilo Horn
2023-03-16 23:46 ` Michael Heerdegen
2023-03-17 7:04 ` Tassilo Horn
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=87y1o486wo.fsf@web.de \
--to=michael_heerdegen@web.de \
--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).