From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: unshift
Date: Mon, 1 Apr 2024 09:40:03 -0700 [thread overview]
Message-ID: <4de03717-ebcb-4b85-bc1b-14be0d2cc8c3@eastlink.ca> (raw)
In-Reply-To: <CAN=4vMpJJBuXkSH+nAyf+26psC3XdirsDAEfMk4WUTJ+53qBFA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 780 bytes --]
On 2024-04-01 09:20, Roman Perepelitsa wrote:
> It doesn't seem super useful to be honest. The semantics are odd, too.
> What should this do?
>
> shift
> set blah
> unshift
>
> Or this?
>
> foo=(42)
> shift foo
> integer foo
> unshift
>
> There is no obvious answer, only options with pros and cons. The path
> from a special-purpose hack to a general solution is long and arduous.
>
Sure, that's what I expected to here. Come to that, I've never used
shift for anything other than the positionals which is all I'm
considering, but if there was an unshift it would obviously have to be
globally useful not, as you say, some single use hack. And since the
hack is easy, your way or Stephane's, the functionality is already there.
[-- Attachment #2: Type: text/html, Size: 1257 bytes --]
next prev parent reply other threads:[~2024-04-01 16:41 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 ` unshift Mark J. Reed
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 ` Ray Andrews [this message]
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=4de03717-ebcb-4b85-bc1b-14be0d2cc8c3@eastlink.ca \
--to=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).