zsh-users
 help / color / mirror / code / Atom feed
From: "Mark J. Reed" <markjreed@gmail.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: unshift
Date: Mon, 1 Apr 2024 09:54:49 -0400	[thread overview]
Message-ID: <CAA=-s3xvS7d5hv4tqwQ7_kXnWj58+X+rHdLfy_WK_g+_VRJTLQ@mail.gmail.com> (raw)
In-Reply-To: <f1e0b92a-07b6-46c0-a2d6-6eeda828620b@eastlink.ca>

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

I haven't read your whole message yet, but to unshift a new value in front
of the positional params, all you have to do is this:


    set -- "$new" "$@"

And now $1 is "$new", $2 is whatever $1 used to be, and so on.

On Mon, Apr 1, 2024 at 9:52 AM Ray Andrews <rayandrews@eastlink.ca> wrote:

> Can we unshift the positional params?  I have a complex function that has
> shifts throughout and at one point there's a while loop:
>
> shift
> while [ "$1" ]; do
>     if [ a ]; then b; c  fi
>     if [ d ]; then e; f  fi
>     if [ g ]; then h; i  fi
> ...
> shift
> done
>
> ... works fine, but I'm thinking to restructure it:
>
> shift
> while [ "$1" ]; do
>     if [ a ]; then b; c; continue fi
>     if [ d ]; then e; f; continue fi
>     if [ g ]; then h; i; continue fi
> ...
> shift
> done
>
> ... because only one 'if' test will be relevant per loop and the remaining
> 'if' tests might even do some bad stuff.  The problem of course is that if
> I 'continue', the final 'shift' is missed.  I could do this:
>
> # shift
> while [ "$2" ]; do
>     shift
>     if [ a ]; then b; c; continue fi
>     if [ d ]; then e; f; continue fi
>     if [ g ]; then h; i; continue fi
> ...
> # shift
> done
>
> ... except that the leading (commented) 'shift' might happen in any number
> of places and changing them all would be troublesome.  It can be done of
> course, but I'm wondering if we have some way of  faking this:
>
> shift
> unshift
> while [ "$1" ]; do
>     shift
>     if [ a ]; then b; c; continue fi
>     if [ d ]; then e; f; continue fi
>     if [ g ]; then h; i; continue fi
> ...
> # shift
> done
>
> ... it looks pointless above, however note that the leading 'shift' might
> in fact have happened in any one of several different places all of which
> would need to be reworked and it's fragile, so the 'unshift' would take
> care of it in one place, at least temporarily.  I know we don't have an
> official unshift, but can it be faked?  Of course there's also this:
>
>     ...
>     if [ a ]; then b; c; shift; continue fi
>     ...
>
> ... but I'm wondering about a more succinct logic.  The quick and dirty
> 'unshift' idea would solve a temporary problem very nicely.
>
>
>
>

-- 
Mark J. Reed <markjreed@gmail.com>

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

  reply	other threads:[~2024-04-01 14:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-01 13:52 unshift Ray Andrews
2024-04-01 13:54 ` Mark J. Reed [this message]
2024-04-01 14:00   ` unshift Mark J. Reed
2024-04-01 14:23   ` unshift Ray Andrews
2024-04-01 16:03   ` unshift Stephane Chazelas
2024-04-01 14:38 ` unshift Roman Perepelitsa
2024-04-01 16:11   ` unshift Ray Andrews
2024-04-01 16:20     ` unshift Roman Perepelitsa
2024-04-01 16:40       ` unshift Ray Andrews
2024-04-01 19:41         ` unshift Bart Schaefer
2024-04-01 22:52           ` unshift Ray Andrews
2024-04-01 16:03 ` unshift Bart Schaefer
2024-04-01 16:30   ` unshift Ray Andrews
2024-04-02 12:41 ` unshift Dennis Eriksen
2024-04-02 14:01   ` unshift Ray Andrews
2024-04-02 19:59     ` unshift Roman Perepelitsa
2024-04-02 20:24       ` unshift Ray Andrews

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='CAA=-s3xvS7d5hv4tqwQ7_kXnWj58+X+rHdLfy_WK_g+_VRJTLQ@mail.gmail.com' \
    --to=markjreed@gmail.com \
    --cc=rayandrews@eastlink.ca \
    --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).