From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Mendler <mail@daniel-mendler.de>
Cc: 61274@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#61274: 29.0.60; dabbrev-capf signals errors
Date: Sat, 04 Feb 2023 18:54:01 +0200 [thread overview]
Message-ID: <83mt5ttlqu.fsf@gnu.org> (raw)
In-Reply-To: <b03f603b-d00d-880d-7e61-9f8b3dcedf71@daniel-mendler.de> (message from Daniel Mendler on Sat, 4 Feb 2023 17:03:26 +0100)
> Date: Sat, 4 Feb 2023 17:03:26 +0100
> Cc: 61274@debbugs.gnu.org, monnier@iro.umontreal.ca
> From: Daniel Mendler <mail@daniel-mendler.de>
>
> On 2/4/23 14:16, Eli Zaretskii wrote:
> > The patch below fixes the error.
>
> Thanks!
Should I install it?
> > Regarding "No dynamic expansion" error: what did you expect to happen
> > instead and why? IOW, what is the expected result of having
> > dabbrev-capf alone in completion-at-point-functions, and then typing
> > "x M-TAB"?
>
> I would expect the completion UI to show a message, instead of an error
> from the Capf. For example if you start emacs -Q, type "nonexistent
> M-TAB" in the scratch buffer to access the normal Elisp completions.
> Then you will see the message "No match" in the minibuffer. If
> `dabbrev-capf' would not throw an error, we would get the same message.
maybe dabbrev-capf is unsuitable to serve as the value of
completion-at-point-functions?
Stefan, any comments?
next prev parent reply other threads:[~2023-02-04 16:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 11:03 bug#61274: 29.0.60; dabbrev-capf signals errors Daniel Mendler
2023-02-04 13:16 ` Eli Zaretskii
2023-02-04 16:03 ` Daniel Mendler
2023-02-04 16:54 ` Eli Zaretskii [this message]
2023-02-04 17:13 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-04 17:17 ` Eli Zaretskii
2023-02-04 17:30 ` Daniel Mendler
2023-02-04 18:09 ` Eli Zaretskii
2023-02-04 18:21 ` Daniel Mendler
2023-02-04 17:23 ` Daniel Mendler
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=83mt5ttlqu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=61274@debbugs.gnu.org \
--cc=mail@daniel-mendler.de \
--cc=monnier@iro.umontreal.ca \
/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).