zsh-users
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: Why would I use .namespace.myvar?
Date: Sun, 10 Mar 2024 16:02:52 -0700	[thread overview]
Message-ID: <2e33aeab-865a-48cc-8f31-4916d4a0c604@eastlink.ca> (raw)
In-Reply-To: <8b8064f6-1310-4d01-804c-ee78ace9b730@app.fastmail.com>



On 2024-03-10 15:45, Lawrence Velázquez wrote:
> On Sun, Mar 10, 2024, at 6:16 PM, Ray Andrews wrote:
>> BTW interesting
>> to learn that ksh is still in active development, I thought it was on
>> ice, like bash.
> Neither is "on ice".  Both are quite active.
Not that I'm in the loop, but I recall some time back, there was an 
exploit in bash and the talk was that there was no one available to fix 
it.  Then I heard that bash development was down to one guy, namely 
Chet.  Mind ... looking at your link, it seems he's quite active, so 
thereyago.  Thanks.  It's healthy.  I know zsh has taken huge 
inspiration from ksh, so having those dudes 'competing' is good for 
everybody.

>
> https://github.com/ksh93/ksh/commits/dev/
> https://git.savannah.gnu.org/cgit/bash.git/log/?h=devel
>



  reply	other threads:[~2024-03-10 23:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-09 14:30 Stephane Chazelas
2024-03-09 22:58 ` Bart Schaefer
2024-03-10 12:13   ` Stephane Chazelas
2024-03-10 20:08     ` Bart Schaefer
2024-03-10 22:16       ` Ray Andrews
2024-03-10 22:45         ` Lawrence Velázquez
2024-03-10 23:02           ` Ray Andrews [this message]
2024-03-10 23:53             ` Mark J. Reed
2024-03-11  2:22               ` Ray Andrews
2024-03-11  2:35                 ` Bart Schaefer
2024-03-11  2:50                   ` Ray Andrews
2024-03-11  7:53               ` Stephane Chazelas
2024-03-10 22:48         ` Bart Schaefer
2024-03-10 23:14           ` 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=2e33aeab-865a-48cc-8f31-4916d4a0c604@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).