From: Dmitry Gutov <dmitry@gutov.dev>
To: Spencer Baugh <sbaugh@janestreet.com>, 68514@debbugs.gnu.org
Cc: juri@linkov.net
Subject: bug#68514: 30.0.50; minibuffer-choose-completion + elisp-c-a-p delete next sexp when completing after open paren
Date: Tue, 16 Jan 2024 19:28:39 +0200 [thread overview]
Message-ID: <3e453670-b669-4b87-835e-a2e199736fab@gutov.dev> (raw)
In-Reply-To: <ierjzo9rywj.fsf@igm-qws-u22796a.mail-host-address-is-not-set>
On 16/01/2024 19:06, Spencer Baugh wrote:
> I'm not sure how to fix this. I don't know all the features of
> elisp-completion-at-point, but maybe it shouldn't use (forward-sexp 1)
> when finding the end of the completion region. Maybe it should be doing
> something like (skip-syntax-forward "w_") to determine the end of the
> region?
>
> BTW, this completion region returned by elisp-completion-at-point also
> causes a bug in company-mode: since company-capf stops completion when
> the end of the completion region is after point, it's not possible to do
> Elisp company completion immediately after an open paren no matter how
> company is configured.
I don't have a patch to suggest at the moment, but
`elisp-completion-at-point` is indeed peculiar in its bounds detection
logic.
The idea to use (skip-syntax-forward "w_") sounds good. But one
alternative (in case you find it more convenient) is to use
(bounds-of-thing-at-point 'symbol).
next prev parent reply other threads:[~2024-01-16 17:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 17:06 bug#68514: 30.0.50; minibuffer-choose-completion + elisp-c-a-p delete next sexp when completing after open paren Spencer Baugh
2024-01-16 17:28 ` Dmitry Gutov [this message]
2024-01-16 17:39 ` Juri Linkov
2024-01-16 19:43 ` Spencer Baugh
2024-01-17 16:37 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-17 17:20 ` Spencer Baugh
2024-01-17 17:53 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-17 18:10 ` Spencer Baugh
2024-01-17 19:03 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-18 19:05 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-17 16:42 ` Juri Linkov
2024-01-17 17:22 ` Spencer Baugh
2024-01-17 17:44 ` Juri Linkov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3e453670-b669-4b87-835e-a2e199736fab@gutov.dev \
--to=dmitry@gutov.dev \
--cc=68514@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=sbaugh@janestreet.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.