From: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: master 87e422f: Beef up the Emacs string utility set a bit
Date: Mon, 21 Dec 2020 15:20:56 -0500 [thread overview]
Message-ID: <c46e9af0-4744-6042-dbcf-ffd812e62cb3@gmail.com> (raw)
In-Reply-To: <87a6u7dmnw.fsf@gnus.org>
On 12/21/20 1:44 PM, Lars Ingebrigtsen wrote:
> I've been going through
>
> https://github.com/magnars/s.el
>
> to see whether there's anything there that seems both 1) useful and 2)
> Emacs doesn't have already, but there was less than I remembered,
> really. With the five functions I added, the rest are mostly just
> aliases for stuff we have in Emacs 28.
>
> Things I wasn't sure about:
>
> s-chomp (s)
>
> Is this really useful? Emacs is so un-line-oriented that I can't recall
> having removed newlines from a string ever...
Look for (replace-regexp-in-string "\n$" "" and variants, or string-trim-right. One common use case is in conjunction with shell-command-to-string. Even if it was in Emacs, though, I'm not sure I'd find it and use it instead of string-trim-end.
> s-shared-start (s1 s2)
> s-shared-end (s1 s2)
It's useful for computing relative paths (as done by file-relative-name) and for abbreviating entries in a list (finding the common prefix of many entries and abbreviating them all that way). It's a trivial extension of compare-strings, but discoverability isn't great. The implementation of s-shared-start in s.el is inefficient, but my patch (https://github.com/magnars/s.el/pull/134/files) was never merged.
An efficient implementation of s-shared-end would be nice, but I think it would require generalizing compare-strings.
next prev parent reply other threads:[~2020-12-21 20:20 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
2020-12-21 21:32 ` Lars Ingebrigtsen
2020-12-21 20:20 ` Clément Pit-Claudel [this message]
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=c46e9af0-4744-6042-dbcf-ffd812e62cb3@gmail.com \
--to=cpitclaudel@gmail.com \
--cc=emacs-devel@gnu.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).