From: Juri Linkov <juri@linkov.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "James N. V. Cash" <james.nvc@gmail.com>, emacs-devel@gnu.org
Subject: Re: [PATCH] Handle case where `beg` and `end` are strings instead of markers
Date: Fri, 29 Apr 2022 20:29:21 +0300 [thread overview]
Message-ID: <86zgk3u7bi.fsf@mail.linkov.net> (raw)
In-Reply-To: <jwvpmkzrhkd.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 29 Apr 2022 12:18:18 -0400")
> I think rather than (minibuffer--completion-prompt-end) and (point-max),
> we should be using "the beginning of the completion area" and "the end
> of the completion area". In a typical minibuffer completion, that's
> exactly the same, but in `completing-read-multiple` or
> `complete-in-region` the difference can be significant.
Is this what bug#48356 is intended to improve?
next prev parent reply other threads:[~2022-04-29 17:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 0:36 [PATCH] Handle case where `beg` and `end` are strings instead of markers James N. V. Cash
2022-04-29 1:10 ` James N. V. Cash
2022-04-29 7:05 ` Juri Linkov
2022-04-29 12:10 ` James N. V. Cash
2022-04-29 12:55 ` Stefan Monnier
2022-04-29 14:07 ` James N. V. Cash
2022-04-29 16:18 ` Stefan Monnier
2022-04-29 17:20 ` James N. V. Cash
2022-04-29 17:29 ` Juri Linkov [this message]
2022-04-29 21:05 ` Stefan Monnier
2022-04-30 12:41 ` James N. V. Cash
2022-04-30 13:44 ` Stefan Monnier
2022-04-30 15:48 ` James N. V. Cash
2022-05-01 18:06 ` Juri Linkov
2022-05-02 15:32 ` James N. V. Cash
2022-05-02 19:11 ` Juri Linkov
2022-05-04 12:08 ` James N. V. Cash
2022-05-04 19:27 ` Juri Linkov
2022-05-04 21:09 ` James N. V. Cash
2022-05-05 18:16 ` Juri Linkov
2022-05-01 18:03 ` Juri Linkov
2022-05-01 18:37 ` Stefan Monnier
2022-05-05 18:19 ` Juri Linkov
2022-05-05 18:30 ` Exiting completion-in-region-mode (was: Handle case where `beg` and `end` are strings instead of markers) Juri Linkov
2022-05-19 18:52 ` Exiting completion-in-region-mode 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
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=86zgk3u7bi.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=emacs-devel@gnu.org \
--cc=james.nvc@gmail.com \
--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).