unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Christopher Lam <christopher.lck@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: [PATCH] Add string-replace-substring to (ice-9 string-fun)
Date: Sun, 5 Jan 2020 13:51:29 +0000	[thread overview]
Message-ID: <CAKVAZZ+ggRp1XNP23rvCCeioCRWRUk32Oigns4uhHSfw6+74kA@mail.gmail.com> (raw)
In-Reply-To: <87k166ump3.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1915 bytes --]

This function has an interesting history.

Someone or something in #guile had clued me there was a magic
string-replace-substring somewhere in guile-user archives. With some luck I
found it, and had bookmarked it, and kept it at the back of my mind for a
good number of months.

Meanwhile I was steadily learning guile, and cleaning up GnuCash. Noting
GnuCash still supports use of guile-2.0, I was finally able to use Mark's
implementation to fix a bad one[1].   After discussing this change with
GnuCash's lead developer, we realised that upgrading the embedded guile in
GnuCash in Windows to 2.2 would solve a whole lot of i18n issues, which it
did.

Hence in a roundabout way, we are thankful for the original post and the
discussion[2] around it.

[1] https://github.com/Gnucash/gnucash/commit/7d15e6e4
[2] https://lists.gnu.org/archive/html/guile-devel/2014-03/msg00058.html

On Sun, 5 Jan 2020 at 12:12, Jan Nieuwenhuizen <janneke@gnu.org> wrote:

> Andy Wingo writes:
>
> > On Fri 20 Dec 2019 18:32, lloda <lloda@sarc.name> writes:
> >
> >> This patch adds string-replace-substring that wingo posted to the
> >> mailing list to (ice-9 strings). This is a commonly used function and a
> >> good implementation isn't trivial, so I think it deserves inclusion.
> >
> > I didn't know that this module existed :)  Sure, why not.  Please fix
> > the commit message when you push.
>
> That's great!  This is one of the things that has always amazed and
> annoyed me to be missing and I have written several half-baken
> implementations of it when I needed something like it.
>
> Would it be too much to ask for some documentation to go with it, so
> that we will be able to find it?
>
> Greetings,
> janneke
>
> --
> Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
> Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
>
>

[-- Attachment #2: Type: text/html, Size: 2880 bytes --]

  reply	other threads:[~2020-01-05 13:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-20 17:32 [PATCH] Add string-replace-substring to (ice-9 string-fun) lloda
2020-01-05 11:34 ` Andy Wingo
2020-01-05 12:12   ` Jan Nieuwenhuizen
2020-01-05 13:51     ` Christopher Lam [this message]
2020-01-05 15:49       ` Arne Babenhauserheide
2020-01-05 14:01     ` lloda
2020-01-05 23:40       ` David Pirotte
2020-01-06  9:08 ` Linus Björnstam

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/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKVAZZ+ggRp1XNP23rvCCeioCRWRUk32Oigns4uhHSfw6+74kA@mail.gmail.com \
    --to=christopher.lck@gmail.com \
    --cc=guile-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.
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).