zsh-workers
 help / color / mirror / code / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Oliver Kiddle <opk@zsh.org>
Cc: zsh-workers@zsh.org
Subject: Re: ksh compatibility: initial value of $_
Date: Sat, 15 Apr 2023 00:02:51 -0500	[thread overview]
Message-ID: <CAMP44s3agUj5KVo3JX6P=3X66GT8FRrVoWiPVGL3DrWN3B_p-g@mail.gmail.com> (raw)
In-Reply-To: <91076-1680970954.277199@scD9.nSRV.LVCF>

On Sat, Apr 8, 2023 at 11:22 AM Oliver Kiddle <opk@zsh.org> wrote:

> One disadvantage of prefixing variables with "BASH" or "ZSH" is that it
> makes it harder for different shells to later be compatible with each
> other.

Has that actually happened with any variable in the last 20 years? (my
living memory)

I tried to push the git project to do something like
`ARGZERO=${ZSH_ARGZERO-$0}` for their sh testing framework to work on
zsh and it did not fly at all. I wonder if any such consensus has
actually taken place.

I think it's fine to use a ZSH_ prefix until there's consensus.

-- 
Felipe Contreras


  parent reply	other threads:[~2023-04-15  5:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-28  1:52 Bart Schaefer
2023-03-23 10:40 ` Jun T
2023-03-31  8:18   ` Jun T
2023-03-31 14:31     ` Jun. T
2023-03-31 17:45       ` Bart Schaefer
2023-04-03 11:16         ` Jun. T
2023-04-03 16:48           ` Bart Schaefer
2023-03-31 19:02       ` Bart Schaefer
2023-03-31 19:03         ` Bart Schaefer
2023-04-03 12:13     ` Jun. T
2023-04-03 16:50       ` Bart Schaefer
2023-04-04 16:24         ` Jun. T
2023-04-05  1:03           ` Oliver Kiddle
2023-04-05  8:15             ` zeurkous
2023-04-05  9:00               ` Oliver Kiddle
2023-04-05 16:24             ` Jun. T
2023-04-05  8:14           ` dana
2023-04-05 18:16             ` Jun. T
2023-04-08  4:03               ` dana
2023-04-08 16:22                 ` Oliver Kiddle
2023-04-09 13:30                   ` Jun. T
2023-04-10  0:51                     ` Jun T
2023-04-15  5:02                   ` Felipe Contreras [this message]
2023-04-15 22:24               ` Bart Schaefer

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='CAMP44s3agUj5KVo3JX6P=3X66GT8FRrVoWiPVGL3DrWN3B_p-g@mail.gmail.com' \
    --to=felipe.contreras@gmail.com \
    --cc=opk@zsh.org \
    --cc=zsh-workers@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).