From: Juri Linkov <juri@linkov.net>
To: James N. V. Cash <james.nvc@gmail.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: [PATCH] Handle case where `beg` and `end` are strings instead of markers
Date: Wed, 04 May 2022 22:27:43 +0300 [thread overview]
Message-ID: <86bkwdjeeg.fsf@mail.linkov.net> (raw)
In-Reply-To: <87pmkt1owo.fsf@occasionallycogent.com> (James N. V. Cash's message of "Wed, 04 May 2022 08:08:07 -0400")
>>> The other approach, which the below patch implements, is try to find the
>>> bounds based on the strings, but if the contents been edited, find the
>>> nearest CRM separator. This is kind of nice in that it lets you edit
>>> other selections but then still select a candidate, but I don't know how
>>> useful/expected that really is. The logic could also be made somewhat
>>> more complex (count the number of separators in `start` and `end`, try
>>> to guess how many we should skip over in each direction) but I don't
>>> know if that's really worthwhile.
>>
>> I tried out this approach and it works nicely, except the case
>> when the CRM separator gets deleted by the user. But OTOH,
>> the user might want to delete the separator intentionally,
>> to reduce the number of selections. So it seems there is no need
>> to make the logic more complex.
>
> Should I make a new thread with this patch then, or is the one here okay?
If you think your latest patch is safe enough to install and
you signed a copyright assignment for your changes, I could push it
without the need to create a bug report.
next prev parent reply other threads:[~2022-05-04 19:27 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
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 [this message]
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=86bkwdjeeg.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).