zsh-users
 help / color / mirror / code / Atom feed
From: zzapper <zsh@rayninfo.co.uk>
To: zsh-users@zsh.org
Subject: Re: Can I test if a parameter expansion has worked
Date: Thu, 15 Sep 2022 09:38:17 +0100	[thread overview]
Message-ID: <e0b6d25e-f361-ff7f-7698-69edaf1c3ef5@rayninfo.co.uk> (raw)
In-Reply-To: <1026093540.752006.1663230255721@mail.virginmedia.com>


On 15/09/2022 09:24, Peter Stephenson wrote:
>> On 15/09/2022 08:34 zzapper <zsh@rayninfo.co.uk> wrote:
>> # adding a prefix '_s' to an image name
>>
>> f=stuff.jpg;
>>
>> print ${f/%(#m).[pjg][npi]e#[gf]/_s$MATCH}
>>
>> stuff_s.jpg  # good this is what i want
>>
>> # now pass 'bad' input
>>
>> f=stuff.txt;
>>
>> print ${f/%(#m).[pjg][npi]e#[gf]/_s$MATCH}
>> stuff.txt  #  expansion has obviously left the input unchanged but can I
>> test for that???
> No, there's no way of telling if some expansion actually changed an
> expression without actually testing the final result.  The differences
> between the cases (changed / not changed) are buried deep within the
> shell and don't leave an obvious trace above --- and in any case given
> how complicated zsh expressions can get finding a useful binary way of
> testing what the whole expression did would be incredibly hairy.
>
> Just test the resulting expression.
>
> pws
>

I now realise that it would horribly subjective to decide whether or not 
an expansion had succeeded in any case :)

f=pws

echo ${f/%(#m)pws/thanks $MATCH}


zzapper



  reply	other threads:[~2022-09-15  8:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-14 10:03 zzapper
2022-09-14 18:36 ` Bart Schaefer
2022-09-15  0:08 ` Alex Satrapa
2022-09-15  7:34 ` zzapper
2022-09-15  8:24   ` Peter Stephenson
2022-09-15  8:38     ` zzapper [this message]
2022-09-15 16:48   ` Bart Schaefer
2022-09-20  7:14     ` david rayner
2022-09-16  0:41   ` Alex Satrapa
2022-09-20 12:49   ` Stephane Chazelas
2022-09-20 13:25   ` Stephane Chazelas
2022-09-20 13:31     ` Stephane Chazelas

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

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

  git send-email \
    --in-reply-to=e0b6d25e-f361-ff7f-7698-69edaf1c3ef5@rayninfo.co.uk \
    --to=zsh@rayninfo.co.uk \
    --cc=zsh-users@zsh.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.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).