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 15:16:17 -0700	[thread overview]
Message-ID: <6c783297-aa25-4ff6-8233-185a281a074f@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7ZDKOP1fL7qExEfm_-G=n2dCD_vcx0+Wx-BSDJeNOcs1w@mail.gmail.com>

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



On 2024-03-10 13:08, Bart Schaefer wrote:

> Given all this uncertainty and that we're already more than 2 years
> past the 5.9 release, I'd rather get the tractable parts out there
> sooner.
I thought I'd be able to pick it up as the thread progressed, but I 
still have no idea what a namespace even is.  It sure sounds 
complicated.  I keep seeing structures because of the dots but I know 
that's not the case.  In a sentence or two, what is a namespace and why 
do we want it?  But I do remember vaguely that I once had a question 
where the future solution was going to be just that.  BTW interesting to 
learn that ksh is still in active development, I thought it was on ice, 
like bash.

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

  reply	other threads:[~2024-03-10 22:17 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 [this message]
2024-03-10 22:45         ` Lawrence Velázquez
2024-03-10 23:02           ` Ray Andrews
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=6c783297-aa25-4ff6-8233-185a281a074f@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).