[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#61274: 29.0.60; dabbrev-capf signals errors
From: |
Stefan Monnier |
Subject: |
bug#61274: 29.0.60; dabbrev-capf signals errors |
Date: |
Sat, 04 Feb 2023 12:13:27 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
> maybe dabbrev-capf is unsuitable to serve as the value of
> completion-at-point-functions?
As the name implies, it's a function designed specifically for use on
`completion-at-point-functions`. Maybe dabbrev is not well adapted
for use within a normal completion UI, but `dabbrev-capf` should do its
best to obey the rules of `completion-at-point-functions`, so I think
the behavior Daniel suggests is indeed what `dabbrev-capf` should try
to do.
Those people who don't like it can use dabbrev via various other UIs.
Stefan
- bug#61274: 29.0.60; dabbrev-capf signals errors, Daniel Mendler, 2023/02/04
- bug#61274: 29.0.60; dabbrev-capf signals errors, Eli Zaretskii, 2023/02/04
- bug#61274: 29.0.60; dabbrev-capf signals errors, Daniel Mendler, 2023/02/04
- bug#61274: 29.0.60; dabbrev-capf signals errors, Eli Zaretskii, 2023/02/04
- bug#61274: 29.0.60; dabbrev-capf signals errors,
Stefan Monnier <=
- bug#61274: 29.0.60; dabbrev-capf signals errors, Eli Zaretskii, 2023/02/04
- bug#61274: 29.0.60; dabbrev-capf signals errors, Daniel Mendler, 2023/02/04
- bug#61274: 29.0.60; dabbrev-capf signals errors, Eli Zaretskii, 2023/02/04
- bug#61274: 29.0.60; dabbrev-capf signals errors, Daniel Mendler, 2023/02/04
- bug#61274: 29.0.60; dabbrev-capf signals errors, Daniel Mendler, 2023/02/04