From: Maxime Devos <maximedevos@telenet.be>
To: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: Macro for replacing a placeholder in an expression
Date: Sat, 30 Jul 2022 23:10:36 +0200 [thread overview]
Message-ID: <b28c3c8f-5df3-d8a6-d017-4ff9618f4680@telenet.be> (raw)
In-Reply-To: <64ef2c56-2999-9514-c98b-7a14c9683e1a@telenet.be>
[-- Attachment #1.1.1: Type: text/plain, Size: 548 bytes --]
On 30-07-2022 22:44, Maxime Devos wrote:
>
>> "All I want to do" is to replace some placeholder (in this case <?>)
>> in an arbitrary form. No matter how that form looks or how deeply it
>> is nested, if there are <?> inside of it, I want to replace them. Is
>> this impossible?
>>
> Yes, see e.g. the replace-placeholder+replace-result-placeholder I
> sent, subject to the limitations of messy nesting semantics. However ...
Oops, double negative etc. Correction: No, this is not impossible, it's
possible, see e.g. the [...]
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-07-30 21:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 23:57 Macro for replacing a placeholder in an expression Zelphir Kaltstahl
2022-07-28 0:55 ` Maxime Devos
2022-07-28 10:23 ` Zelphir Kaltstahl
2022-07-28 10:28 ` Maxime Devos
2022-07-30 15:42 ` Zelphir Kaltstahl
2022-07-30 20:44 ` Maxime Devos
2022-07-30 21:10 ` Maxime Devos [this message]
2022-07-30 21:13 ` Maxime Devos
2022-08-05 9:42 ` Linus Björnstam
2022-08-06 14:28 ` Zelphir Kaltstahl
2022-07-28 1:04 ` Maxime Devos
2022-07-28 8:39 ` Zelphir Kaltstahl
2022-07-28 9:48 ` Maxime Devos
2022-07-28 11:26 ` Zelphir Kaltstahl
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=b28c3c8f-5df3-d8a6-d017-4ff9618f4680@telenet.be \
--to=maximedevos@telenet.be \
--cc=guile-user@gnu.org \
--cc=zelphirkaltstahl@posteo.de \
/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).