zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: linuxtechguy@gmail.com, Jim <linux.tech.guy@gmail.com>,
	devs <zsh-workers@zsh.org>
Subject: Re: Missing keyword 'tied'
Date: Tue, 4 Jan 2022 16:57:19 +0000 (GMT)	[thread overview]
Message-ID: <750958709.583242.1641315439945@mail2.virginmedia.com> (raw)
In-Reply-To: <CA+rB6GKj8G9ozRvP-bhfCi-PLMB1W+oZ1JTF+ag9CpBDBDfpVw@mail.gmail.com>

> On 04 January 2022 at 16:22 Jim <linux.tech.guy@gmail.com> wrote:
> Your patch triggered something.  The keyword 'special' for the parameter
> flag 't' is defined as "for special parameters defined by the shell".
> Should it
> also include user-defined parameters? Case in point, parameters used by
> ztie to "tie" to a gdbm file. Technically, the parameter itself is defined
> by the
> user, yet it has the 'special' keyword.  Sorry if this seems to be
> nitpicking,
> but 57 years of computer logic it's hard to break the habit.
> 
> Also when I first started using ztie I expected the parameter to include the
> key word 'tied'. Had to train myself to check parameter zgdbm_tied.

In this case the generic parameter code is getting confused by the details
of the ztie interface, so that would take some special casing to sort out ---
unless we simply document that ztie creates special parameters, which is
probably the way to go.  If the (t) flag says they're special, they're special,
no matter how they were created; it's the same flag that the shell uses everywhere
to test this.

"Tied" in the sense in the generic parameter code has a different meaning, which
doesn't apply to database ties (we should have been more careful about the language).
I don't think it's possible for the (t) code to detect the existence of a database
link without doing a lot more work than it's designed for.

pws


  reply	other threads:[~2022-01-04 16:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04 15:15 Jim
2022-01-04 15:33 ` Peter Stephenson
2022-01-04 16:22   ` Jim
2022-01-04 16:57     ` Peter Stephenson [this message]
2022-01-04 17:22       ` Jim

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=750958709.583242.1641315439945@mail2.virginmedia.com \
    --to=p.w.stephenson@ntlworld.com \
    --cc=linux.tech.guy@gmail.com \
    --cc=linuxtechguy@gmail.com \
    --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).