unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: master 87e422f: Beef up the Emacs string utility set a bit
Date: Mon, 21 Dec 2020 16:29:53 -0500	[thread overview]
Message-ID: <258ef70f-5ee6-d6ad-264a-8fc77e5ac821@gmail.com> (raw)
In-Reply-To: <87tusec19r.fsf@gnus.org>

On 12/21/20 4:11 PM, Lars Ingebrigtsen wrote:
> Clément Pit-Claudel <cpitclaudel@gmail.com> writes:
> 
>>> s-shared-start is already covered by try-completion, right?  Which has
>>> various uses, e.g. in project--read-file-cpd-relative.
>>
>> It's also covered by compare-strings, but both need a bit of setup to
>> do the same as s-shared-start, so a wrapper can be useful (for
>> example, it's easy to forget to reset
>> completion-regexp-list). Additionally, discovering the right function
>> to call can be hard (I hadn't realized that try-completion could be
>> used for this, and neither had the authors or s.el).
> 
> Perhaps adding something like shared-start would be a good addition for
> seq?  The s.el semantics seem a bit unclear -- do "Foobar" and "foozot"
> share a prefix?  Adding to seq (with a predicate to compare characters)
> would be nice...

But slow, right?  Or maybe it would have a fast path for specific predicates? 



  reply	other threads:[~2020-12-21 21:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20201221175345.27592.89597@vcs0.savannah.gnu.org>
     [not found] ` <20201221175347.9F1B820B76@vcs0.savannah.gnu.org>
2020-12-21 18:24   ` master 87e422f: Beef up the Emacs string utility set a bit Stefan Kangas
2020-12-21 18:32     ` Lars Ingebrigtsen
2020-12-21 18:44       ` Lars Ingebrigtsen
2020-12-21 19:05         ` Stefan Kangas
2020-12-21 20:03           ` Lars Ingebrigtsen
2020-12-21 20:18         ` Basil L. Contovounesios
2020-12-21 20:38           ` Clément Pit-Claudel
2020-12-21 21:11             ` Lars Ingebrigtsen
2020-12-21 21:29               ` Clément Pit-Claudel [this message]
2020-12-21 21:32                 ` Lars Ingebrigtsen
2020-12-21 20:20         ` Clément Pit-Claudel
2020-12-21 20:34           ` Lars Ingebrigtsen
2020-12-21 20:44             ` Clément Pit-Claudel
2020-12-21 21:06               ` Lars Ingebrigtsen
2020-12-21 22:13                 ` Basil L. Contovounesios
2020-12-21 22:19                   ` Lars Ingebrigtsen
2020-12-22 10:41         ` Mattias Engdegård
2020-12-22 14:48           ` Lars Ingebrigtsen
2020-12-22 15:03             ` Mattias Engdegård
2020-12-22 15:24           ` Alfred M. Szmidt
2020-12-21 19:05       ` Stefan Monnier
2020-12-21 19:19         ` Lars Ingebrigtsen

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=258ef70f-5ee6-d6ad-264a-8fc77e5ac821@gmail.com \
    --to=cpitclaudel@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    /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).